Resolve mise aliases such as `lts` when reading mise.toml
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 58/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- github-actions, node.js, typescript
Research direction
Start by tracing how mise.toml values flow from getNodeVersionFromFile into isLtsAlias and version resolution. Check the existing tests for mise version files and LTS aliases, then add coverage for node = "lts"; done means it resolves as the current LTS or returns a clear error for unsupported mise aliases.
Written by the indexing model from the issue text.
Description
Description:
node-version-file: mise.toml (added in v7.1.0, #1421) reads [tools] node and passes the value through unchanged. Values that are valid for mise but are not in setup-node's version syntax then fail to resolve.
The common case is LTS:
# mise.toml
[tools]
node = "lts"
- uses: actions/[email protected]
with:
node-version-file: mise.toml
getNodeVersionFromFile returns lts. isLtsAlias only matches values that start with lts/, so lts is treated as a semver range, matches no release, and the step fails.
Proposal: when the version comes from mise.toml, translate mise's aliases to setup-node's syntax before resolving. At minimum, map lts to lts/*. Other mise-specific aliases could be handled the same way, or rejected with a clear error that names the unsupported value.
Justification:
A mise.toml is written for mise, and node = "lts" is the usual way to ask mise for the current LTS. Users who adopt the new mise.toml support expect the file they already have to work. Today the only option is to rewrite it as lts/*, which makes the file depend on setup-node's syntax instead of mise's, or to keep a separate node-version input in the workflow, which defeats the point of reading the file.
Are you willing to submit a PR?
Not at this time.
- Dominant language
- TypeScript
- Stars
- 5k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from actions/setup-node
-
`mirror-token` is sent to GitHub instead of `token` when `mirror` is setPossibly taken @v-gowridurgad claimed this 10 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
actions/setup-node#1662 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
feature request
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
actions/setup-node#1531 · 1 comment · 4 reactions ·
Maintainers usually reply within 1 day
-
`latest` & (`current` & `node`) install v27.0.0-alpha.0.0.0 not 26.13.0Possibly taken @v-gowridurgad claimed this 6 days ago. Openbug
Difficulty 3/5 1-2 days Newbie friendliness 45/100
actions/setup-node#1660 · 5 comments · 3 reactions · 1 assignee ·
Maintainers usually reply within 1 day
-
Provide `allow-prereleases` (or similar) option for Node.js 27 AlphaPossibly taken @v-priyagupta108 claimed this 7 days ago. Openfeature request
Difficulty 3/5 1-2 days Newbie friendliness 62/100
actions/setup-node#1657 · 5 comments · 4 reactions · 1 assignee ·
Maintainers usually reply within 1 day
-
Improved error message when a required os lib is missingPossibly taken @OKAN-SOFTWARE claimed this 20 days ago. Openfeature request
Difficulty 3/5 1-2 days Newbie friendliness 55/100
actions/setup-node#1651 · 1 comment ·
Maintainers usually reply within 1 day
All issues in actions/setup-node
Similar issues
-
bug impact:low Team: SecuritySolution Team:Defend Workflows v9.6.0
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
elastic/kibana#306401 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
agentes-chat/agentes-chat#927 ·
Maintainers usually reply within 1 day
-
comp/desktop P2 type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NousResearch/hermes-agent#157702 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
e2e-failure ready-to-code
Difficulty 1/5 Under an hour Newbie friendliness 72/100
redhat-developer/rhdh-plugin-export-overlays#4794 · 1 comment ·
Maintainers usually reply within 1 day