Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change latest node ver to '*' #3831

Merged
merged 3 commits into from
Oct 24, 2023
Merged

Change latest node ver to '*' #3831

merged 3 commits into from
Oct 24, 2023

Conversation

dbkr
Copy link
Member

@dbkr dbkr commented Oct 24, 2023

This uses the latest cached version rather than fetching the latest released version so we don't reply on (and hammer) node's download servers for the very latest version before the actions runners get updated. We'll still stay current, just not quite so aggressively current.

Checklist

  • Tests written for new code (and old code if feasible)
  • Linter and other CI checks pass
  • Sign-off given on the changes (see CONTRIBUTING.md)

This change is marked as an internal change (Task), so will not be included in the changelog.

This uses the latest cached version rather than fetching the latest released version so we don't reply on (and hammer) node's download servers for the very latest version before the actions runners get updated. We'll still stay current, just not quite so aggressively current.
@dbkr dbkr requested a review from a team as a code owner October 24, 2023 14:19
@dbkr dbkr requested a review from MidhunSureshR October 24, 2023 14:19
@dbkr dbkr added the T-Task Tasks for the team like planning label Oct 24, 2023
@t3chguy
Copy link
Member

t3chguy commented Oct 24, 2023

@dbkr could you improve the naming too?

image

@t3chguy
Copy link
Member

t3chguy commented Oct 24, 2023

Also given we also have to download 18 anyway (and 20 this month when it enters LTS) is this even going to make any difference?

@dbkr
Copy link
Member Author

dbkr commented Oct 24, 2023

I don't think we can make it the actual version as I'm assuming you can't use the output of a step in the name of a job. Might be able to fix it to 'latest avail' or something?

@t3chguy
Copy link
Member

t3chguy commented Oct 24, 2023

Sure something like default or even latest is better than * - plus latest means no need to change branch protections

@dbkr
Copy link
Member Author

dbkr commented Oct 24, 2023

We already have node 18 available though on the runner image as it is at the moment (https://github.com/actions/runner-images/blob/main/images/linux/Ubuntu2204-Readme.md#nodejs). Hopefully these will be the same, generally speaking.

@dbkr dbkr added this pull request to the merge queue Oct 24, 2023
Merged via the queue into develop with commit f941fd8 Oct 24, 2023
19 checks passed
@dbkr dbkr deleted the change-latest-node-ver branch October 24, 2023 15:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-Task Tasks for the team like planning
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants