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

Node * and Node lts/* CI jobs are duplicates #51943

Closed
ddzz opened this issue Dec 18, 2022 · 3 comments · Fixed by #51965
Closed

Node * and Node lts/* CI jobs are duplicates #51943

ddzz opened this issue Dec 18, 2022 · 3 comments · Fixed by #51965
Assignees
Labels
Infrastructure Issue relates to TypeScript team infrastructure Needs Investigation This issue needs a team member to investigate its status.

Comments

@ddzz
Copy link
Contributor

ddzz commented Dec 18, 2022

Bug Report

In the GitHub Actions CI matrix, the Node versions * and lts/* both resolve to the same version (currently 18.12.1), making these two jobs duplicates.

🔎 Search Terms

CI, continuous integration, Node version

🕗 Version & Regression Information

N/A

⏯ Playground Link

https://github.com/microsoft/TypeScript/actions/runs/3721283259/jobs/6311330943#step:3:9

https://github.com/microsoft/TypeScript/actions/runs/3721283259/jobs/6311330986#step:3:10

💻 Code

https://github.com/microsoft/TypeScript/blob/main/.github/workflows/ci.yml#L21-L22

🙁 Actual behavior

The Node version in the two CI jobs are the same, making them duplicates.

🙂 Expected behavior

The Node version "*" in the matrix should be changed to "19.x" so that tests run using the latest Node version.

@andrewbranch andrewbranch added Infrastructure Issue relates to TypeScript team infrastructure Needs Investigation This issue needs a team member to investigate its status. labels Dec 19, 2022
@jakebailey
Copy link
Member

This has to be a bug in setup-node, as their docs say that if check-latest is enabled, it will pull the latest dist from https://nodejs.org/dist/index.json which says 19.3.0.

Honestly, I'm not super convinced that we should keep using these special version specs. This issue is one problem, but now we're technically supposed to be testing 14/16/18/19 but our workflow doesn't actually hit 14 anymore, which is a problem.

@jakebailey
Copy link
Member

Ah, so "*" means "whatever is newest on the runner", versus "current" or "latest" which explicitly pull the newest. I can change us to doing that, but I am a little unhappy with the fact that we don't quite get the versions right already.

@fatcerberus
Copy link

It kind of makes sense though - I would generally interpret * in this context to mean either "try all versions" or else "use whatever, I don't care"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Infrastructure Issue relates to TypeScript team infrastructure Needs Investigation This issue needs a team member to investigate its status.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants