Repository navigation
feat: Automate release note publish dates - #347
Merged
Merged
Conversation
Collaborator
Author
|
I've tested this locally in and builds are passing with nothing breaking, so merging for now. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description:
Moves release dates into the release note headings (
## 157 - 2026-09-29), which our existing plugins show under each heading. Titles and URLs stay the same (e.g.,Firefox 157,/release-notes/version/firefox-157/)Additions:
Other:
_Upcoming, not yet released._under the heading. The workflow removes that line.Motivation:
Changing "Upcoming" to "Released" was a manual edit on every release day. Dated headings also give each release a single machine-readable date, which the plugin already supported but we weren't using.
Related issues and pull requests:
Relates to #297