-
Notifications
You must be signed in to change notification settings - Fork 110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Publishing docs: update steps for new release workflow #2196
Conversation
This documents the new workflow added in web-platform-dx#2191
1. For minor releases, add a `## What's New` section to the top of the release notes, before all other sections. | ||
1. For major releases, add a `## Breaking Changes` section to the top of the release notes, before all other sections. | ||
1. Click **Generate release notes**. | ||
1. In the release description, find unescaped `<` characters and make sure that HTML elements are enclosed with backticks. | ||
|
||
This regular expression can help: | ||
|
||
```regex | ||
/ (?<!`)<(.*?)> / | ||
``` | ||
|
||
1. Remove all lines from Dependabot. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm going to target these steps for automation next. 😈
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎉
|
||
1. Review the PR. | ||
|
||
1. Close and reopen the relase PR, to allow the tests to run. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This documents the new workflow added in #2191.
I don't need anyone to actually test this (I'll follow it on the next web-features release), but it'd be nice to have someone read through it.