Skip to content

chore(deps): update jdx/mise-action action to v3.6.3#23

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/jdx-mise-action-3.x
Open

chore(deps): update jdx/mise-action action to v3.6.3#23
renovate[bot] wants to merge 1 commit intomainfrom
renovate/jdx-mise-action-3.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Mar 10, 2026

This PR contains the following updates:

Package Type Update Change
jdx/mise-action action patch v3.6.1v3.6.3

Release Notes

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

v3.6.3

Compare Source

What's Changed

New Contributors

Full Changelog: jdx/mise-action@v3.6.2...v3.6.3

v3.6.2

Compare Source

What's Changed

New Contributors

Full Changelog: jdx/mise-action@v3.6.1...v3.6.2


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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

Renovate PR Review Results

⚖️ Safety Assessment: ✅ Safe

🔍 Release Content Analysis

v3.6.2 (intermediate release):

  • Cache key fix: Moved file_hash to end of cache key template to prevent unintended prefix matching between different workflows
  • Cache invalidation: Bumped cache key prefix from mise-v0 to mise-v1 to invalidate potentially corrupted caches
  • Impact: Improves cache reliability and prevents workflows from restoring incorrect cached dependencies
  • Dependencies: Routine maintenance updates to prettier, @types/node, @types/handlebars, and GitHub action digests

v3.6.3 (target release):

  • Critical bug fix: Pass cwd (current working directory) to all exec calls in exportMiseEnv() function
  • Root cause: The function was ignoring the working_directory input parameter and always running in the GitHub Actions workspace root
  • Impact: In mise 2026.2.0+, this bug caused CI hangs when lockfiles weren't present, as mise would attempt network resolution in the wrong directory and hit errors in environments with private registries

Breaking changes: None
Security fixes: None explicitly mentioned, but the v3.6.3 fix prevents potential CI hangs

🎯 Impact Scope Investigation

Usage locations in this repository:

  • .github/workflows/ci.yml (5 occurrences across all jobs)
    • hadolint job (line 25)
    • lint job (line 38)
    • build job (line 51)
    • unit-test job (line 64)
    • e2e-test job (line 81)

Current usage pattern:

- uses: jdx/mise-action@5228313ee0372e111a38da051671ca30fc5a96db # v3.6.3

Configuration analysis:

  • No custom working_directory or install_dir parameters are specified in any workflow
  • All mise-action invocations use default configuration (runs in workspace root)
  • mise.toml is located at repository root, defining Go 1.26.1 and Aqua tools (golangci-lint, lefthook, hadolint)

Dependency impact:

  • The changes are internal to mise-action's execution logic
  • No API changes or configuration schema modifications
  • The fix ensures correct behavior when running in default mode (workspace root)
  • Cache key changes in v3.6.2 will trigger cache regeneration on first run, but this is transparent

Risk assessment:

  • v3.6.2 cache changes: May cause initial cache miss on first workflow run, then normal operation resumes. This is expected and beneficial (removes potentially corrupted caches)
  • v3.6.3 cwd fix: Since this project doesn't use custom working directories, the fix addresses edge cases that don't apply here, but improves overall robustness

💡 Recommended Actions

Immediate actions:

  1. Merge the PR - This is a safe patch update with bug fixes and no breaking changes
  2. Monitor first workflow run - The cache key prefix change (v0 → v1) will cause a cache miss, expect slightly longer execution time on first run only

No migration work required:

  • No code changes needed in this repository
  • No configuration updates required
  • No workflow modifications necessary
  • Default usage pattern is compatible and benefits from the fixes

Expected behavior after merge:

  • First CI run will rebuild cache due to cache key prefix change (one-time impact)
  • Subsequent runs will use new cache structure normally
  • More robust environment variable resolution in all jobs
  • Elimination of potential CI hang scenarios

🔗 Reference Links

Generated by koki-develop/claude-renovate-review

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.

0 participants