Skip to content
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

Merged
merged 1 commit into from
Nov 8, 2024

Conversation

ddbeck
Copy link
Collaborator

@ddbeck ddbeck commented Nov 8, 2024

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.

@ddbeck ddbeck requested a review from Elchi3 November 8, 2024 10:42
@github-actions github-actions bot added the documentation Improvements or additions to documentation label Nov 8, 2024
Comment on lines +41 to +52
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.
Copy link
Collaborator Author

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. 😈

Copy link
Collaborator

@Elchi3 Elchi3 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎉

@Elchi3 Elchi3 merged commit bb2ad89 into web-platform-dx:main Nov 8, 2024
4 checks passed
@ddbeck ddbeck deleted the update-publishing-docs branch November 8, 2024 13:48

1. Review the PR.

1. Close and reopen the relase PR, to allow the tests to run.
Copy link
Contributor

@szepeviktor szepeviktor Nov 8, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ddbeck A new typo here: "relase"
#1825

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants