Open
Conversation
This script updates the FAQ's "Should I upgrade?" section to mention a new security-relevant Git for Windows version. It is intended to be called as part of the embargoed release process automation, analogous to how bump-version.js updates hugo.yml with the latest version metadata. The script takes a display version (e.g. "2.53.0(3)") as argument, updates the "older than" threshold, and prepends the version to the comma-separated list of security-fix releases. It is idempotent: if the version is already listed, it exits cleanly without changes. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
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
1 participant
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.
Every time a security release of Git for Windows is published, the FAQ's "Should I upgrade?" section needs to be updated to recommend upgrading to (at least) the latest security-fix version. This is easy to forget amidst the many steps of an embargoed release, as demonstrated this past Tuesday when the FAQ update was only remembered a day later.
This script automates that step. It takes a display version (e.g.
2.53.0(3)) as argument, updates the "older than" threshold, and prepends the version to the comma-separated list of security-fix releases. It is idempotent: if the version is already listed, it exits cleanly without changes.Analogous to how
bump-version.jsupdateshugo.ymlwith the latest version metadata, this script is intended to be called as part of the embargoed release process automation so that the FAQ update is never forgotten again.