Automate generating techniques changelog #4515
Open
Conversation
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
✅ Deploy Preview for wcag2 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
iadawn
approved these changes
Aug 14, 2025
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.
This adds:
It turns out that in our manual maintenance of the changelog, we had missed roughly half of the entries that belong in it. This makes the changelog rather long, warranting its own page.
The script added in this PR properly recognizes obsolete techniques, as well as techniques that only pertain to 2.2 success criteria, so the 2.1 and 2.2 changelogs are now distinct. (The PR preview will only show the changelog for 2.2, as the changelog exists at the same path in each version. Here's roughly what it'll look like for 2.1, bearing in mind that one of the stylesheets doesn't load in this standalone preview.)
Because the script reads git history, it will need to be run after PRs that add or remove techniques are merged. I'll discuss with Kevin whether we want to make this part of the monthly publication process.
I also noticed we were incorrectly linking to the old default branch name, so I've updated that in
techniques/index.htmlandunderstanding/about.html.@netlify /techniques/changelog