Rewrite update-version to use the JDK_UPDATE_VERSION string from version numbers as the source of truth.#525
Draft
synecdoche wants to merge 1 commit into
Draft
Conversation
…ion-numbers as the source of truth.
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.
Description
The current
update-version.shgithub action uses whatever the latest tag is to determine the correct version string to be written intoversion.txt. Instead,JDK_UPDATE_VERSIONfromcommon/autoconf/version-numbersis used.Related issues
Motivation and context
How has this been tested?
Ran in github actions from my private fork, with both identical and different
version.txtcases.