PREQ-5497: Bump mise to 2026.4.23 to fix jfrog-cli registry lookup#249
Conversation
mise-versions.jdx.dev intermittently returns empty/not-found for jfrog-cli when using mise 2026.3.17. Updating to 2026.4.23 fixes the flaky registry resolution. Bumped in all 5 files that pin the mise version: - promote/action.yml - build-yarn/action.yml - build-poetry/action.yml - build-npm/action.yml - .github/workflows/test-shell-scripts.yml
|
SummaryThis PR bumps mise from 2026.3.17 to 2026.4.23 across 5 GitHub Actions files to fix intermittent jfrog-cli installation failures. The mise 2026.4.23 release resolves an issue where Changes: Simple version string updates in 5 files (promote/action.yml, build-npm/action.yml, build-poetry/action.yml, build-yarn/action.yml, .github/workflows/test-shell-scripts.yml). Each file has one identical change on the What reviewers should knowWhat to check:
Risk level: Low. This is a straightforward version bump within the same major version. The author has confirmed the fix works. Primary risk would be if 2026.4.23 itself has undiscovered issues, but that's mitigated by the test plan (CI pass + downstream validation). Test focus: Main validation happens in CI (mise must successfully install jfrog-cli), and follow-up testing on a downstream repo (sonar-scanner-integration-tester) should confirm the promote workflow actually works end-to-end.
|
There was a problem hiding this comment.
Pull request overview
This PR updates the pinned mise version used by several composite GitHub Actions and a workflow, in order to address intermittent jfrog-cli installation failures caused by registry lookup issues.
Changes:
- Bump
misefrom2026.3.17to2026.4.23in four composite actions. - Bump
misefrom2026.3.17to2026.4.23in the ShellSpec test workflow.
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
promote/action.yml |
Updates the mise version used during the promote action setup. |
build-yarn/action.yml |
Updates the mise version used for Yarn build action setup. |
build-poetry/action.yml |
Updates the mise version used for Poetry build action setup. |
build-npm/action.yml |
Updates the mise version used for npm build action setup. |
.github/workflows/test-shell-scripts.yml |
Updates the mise version used in the shell script test workflow. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
![sonar-review-alpha[bot]](https://avatars.githubusercontent.com/in/3025063?s=60&v=4){kind=small}
There was a problem hiding this comment.
The 5 changed files are updated correctly and consistently. However, config-npm/action.yml was missed — it still pins jdx/mise-action at version: 2026.3.7 (line 93), which is even older than the version being replaced here. This means any workflow that invokes config-npm directly (including the test workflow, which runs ./config-npm before the separate mise step) will still call mise 2026.3.7 internally. If that version has the same jfrog-cli registry lookup bug, the fix is incomplete for those paths.
Summary
2026.3.17to2026.4.23across all 5 files that pin the versionjfrog-cliinstallation failures caused bymise-versions.jdx.devreturning empty/not-found responsespromote/action.yml,build-yarn/action.yml,build-poetry/action.yml,build-npm/action.yml,.github/workflows/test-shell-scripts.ymlContext
Jira: PREQ-5497
The
promoteworkflow (and potentially other workflows) fails installingjfrog-clivia mise becausemise-versions.jdx.devintermittently returns empty / "Tool not found" forjfrog-cli. The reporter confirmed that mise2026.4.23resolves the issue.Test plan
jfrog-clisuccessfully)sonar-scanner-integration-tester)