Skip to content

CLDR-14212 Update GitHub actions to @vx vs @vx.y.z#813

Merged
srl295 merged 1 commit into
unicode-org:masterfrom
srl295:fixjava14212
Oct 30, 2020
Merged

CLDR-14212 Update GitHub actions to @vx vs @vx.y.z#813
srl295 merged 1 commit into
unicode-org:masterfrom
srl295:fixjava14212

Conversation

@srl295

@srl295 srl295 commented Oct 23, 2020

Copy link
Copy Markdown
Member

CLDR-14212

@srl295 srl295 requested review from btangmu and echeran October 23, 2020 18:11
@srl295 srl295 changed the title CLDR-14212: Update GitHub actions to @vx vs @vx.y.z CLDR-14212 Update GitHub actions to @vx vs @vx.y.z Oct 23, 2020
- Background: https://github.community/t/version-numbering-for-actions/16307/4
- Specific issue: actions/setup-java#104 (comment)
actions/setup-java@v1.4.2 was creating warning messages about set-env,
needed to switch to v1.4.3.  Instead, all actions now use @v1 or @v2, which points to a
branch.
@jira-pull-request-webhook

Copy link
Copy Markdown

Hooray! The files in the branch are the same across the force-push. 😃

~ Your Friendly Jira-GitHub PR Checker Bot

@srl295 srl295 self-assigned this Oct 23, 2020
@srl295

srl295 commented Oct 23, 2020

Copy link
Copy Markdown
Member Author

This is the cause of the 'warnings' in the setup-java phases.

@echeran echeran left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM. Thanks for the links to the specific details on how GH Actions versioning is supposed to work. It makes sense that the onus is on the action maintainer to keep the latest major version alias pointed to the latest release, since each version is really defined just as the name of a git ref (branch/tag) in the action's git repo.

@srl295 srl295 requested review from hagbard, macchiati, pedberg-icu and sffc and removed request for sffc October 26, 2020 16:51
@srl295 srl295 merged commit 5b3d380 into unicode-org:master Oct 30, 2020
@srl295 srl295 deleted the fixjava14212 branch October 30, 2020 21:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants