Skip to content

chore(deps): update jdx/mise-action action to v4#52

Merged
koki-develop merged 1 commit intomainfrom
renovate/jdx-mise-action-4.x
Apr 21, 2026
Merged

chore(deps): update jdx/mise-action action to v4#52
koki-develop merged 1 commit intomainfrom
renovate/jdx-mise-action-4.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Apr 18, 2026

This PR contains the following updates:

Package Type Update Change
jdx/mise-action action major v3.6.3v4.0.1

Release Notes

jdx/mise-action (jdx/mise-action)

v4.0.1: : Documentation and Internal Cleanup

Compare Source

A small maintenance release that updates the README documentation to reflect v4 and cleans up internal code. There are no functional changes to the action itself.

Changed
  • Updated all README examples to reference jdx/mise-action@v4, actions/checkout@v6, and current tool versions by @​deining in #​407 and #​408
  • Extracted getCwd() helper to deduplicate working directory resolution logic (internal refactor, no behavior change) by @​altendky in #​403
New Contributors

Full Changelog: jdx/mise-action@v4.0.0...v4.0.1

v4.0.0

Compare Source

What's Changed
New Contributors

Full Changelog: jdx/mise-action@v3...v4.0.0

v4

Compare Source


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At 12:00 AM through 04:59 AM and 10:00 PM through 11:59 PM, Monday through Friday (* 0-4,22-23 * * 1-5)
    • Only on Sunday and Saturday (* * * * 0,6)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 18, 2026

Renovate PR Review Results

⚖️ Safety Assessment: ✅ Safe

🔍 Release Content Analysis

Major Version Update (v3.6.3 → v4.0.1)

The primary change in mise-action v4 is the upgrade from Node.js 20 to Node.js 24 runtime. This is a proactive update to address GitHub's deprecation timeline:

  • v4.0.0 (Released March 13, 2026): Updated GitHub Actions runtime from Node.js 20 to Node.js 24 to align with GitHub's deprecation schedule. Node.js 20 reaches end-of-life on April 30, 2026, and GitHub will force Node.js 24 as the default runtime starting June 2, 2026.

  • v4.0.1 (Released March 22, 2026): Documentation and internal cleanup release with no functional changes:

    • Updated README examples to reference jdx/mise-action@v4 and actions/checkout@v6
    • Extracted getCwd() helper function to deduplicate working directory resolution logic (internal refactor only)

Breaking Changes:

  • Runtime environment changed from Node.js 20 to Node.js 24
  • No API changes, configuration changes, or input parameter modifications
  • All existing configuration options remain backward compatible

Security Fixes:

  • None reported in this release

New Features:

  • None - this is purely a runtime compatibility update

🎯 Impact Scope Investigation

Usage Location Analysis:

The jdx/mise-action is used exclusively in .github/workflows/ci.yml across 5 jobs:

  1. hadolint job (line 25) - Installs hadolint via mise
  2. lint job (line 38) - Installs golangci-lint via mise
  3. build job (line 51) - Installs Go toolchain via mise
  4. unit-test job (line 64) - Installs Go toolchain via mise
  5. e2e-test job (line 81) - Installs Go toolchain via mise

Current Usage Pattern:

- uses: jdx/mise-action@<commit-sha> # v4.0.1

All usages follow the default configuration (no custom parameters or inputs). The action automatically:

  • Reads mise.toml which specifies: Go 1.26.2, golangci-lint 2.11.4, lefthook 2.1.5, hadolint 2.14.0
  • Runs mise install to install these tools
  • Uses GitHub's cache for mise installations (enabled by default)

Dependency Impact:

  • No impact on other GitHub Actions (actions/checkout@v6, docker actions remain unchanged)
  • No impact on the Go toolchain, linters, or any mise-managed tools
  • No changes required to mise.toml configuration file

Runner Compatibility:

  • All jobs run on ubuntu-latest and ubuntu-24.04-arm which fully support Node.js 24
  • GitHub Actions runners already have Node.js 24 available as of April 2026
  • No changes needed to runner configurations or OS versions

Validation:
The PR diff shows clean updates across all 5 job definitions with only the commit SHA and version comment changed. No configuration blocks were added or modified.

💡 Recommended Actions

Immediate Actions:

  1. Merge this PR - The update is safe and requires no code changes
  2. No migration work required - All existing workflows will continue to function identically

Why This is Safe:

  • The action maintains complete backward compatibility with v3 configurations
  • No input parameters, cache behavior, or installation logic changed
  • Only the underlying Node.js runtime was upgraded (transparent to users)
  • All mise-managed tools (Go, golangci-lint, hadolint) are unaffected
  • GitHub's ubuntu-latest runners fully support Node.js 24

Benefits of Merging:

  • Eliminates future deprecation warnings when GitHub enforces Node.js 24 (June 2, 2026)
  • Ensures workflows remain compatible with GitHub Actions platform changes
  • Proactive compliance with GitHub's runner environment updates

Post-Merge Verification:
Monitor the next CI run to confirm all 5 jobs complete successfully. Expected behavior: identical output to previous runs with no changes to mise tool installations or test results.

🔗 Reference Links

Generated by koki-develop/claude-renovate-review

@renovate renovate Bot force-pushed the renovate/jdx-mise-action-4.x branch from b62b885 to 9e584e0 Compare April 21, 2026 21:14
@koki-develop koki-develop merged commit 56835e4 into main Apr 21, 2026
8 checks passed
@koki-develop koki-develop deleted the renovate/jdx-mise-action-4.x branch April 21, 2026 21:46
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.

1 participant