Skip to content

Remove mise version pinning from CI#214

Closed
zeitlinger wants to merge 2 commits intomainfrom
remove-mise-version-pinning
Closed

Remove mise version pinning from CI#214
zeitlinger wants to merge 2 commits intomainfrom
remove-mise-version-pinning

Conversation

@zeitlinger
Copy link
Copy Markdown
Member

Summary

  • Remove version and sha256 pinning from jdx/mise-action in workflows — mise is stable enough to use latest
  • Remove the custom renovate manager and package rule for mise version updates (no longer needed)

mise is stable enough that pinning a specific version is unnecessary.
This also simplifies the renovate config by removing the custom manager.
Signed-off-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com>
Signed-off-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com>
@zeitlinger zeitlinger enabled auto-merge (squash) February 20, 2026 12:50
Comment on lines -16 to -18
with:
version: v2026.2.11
sha256: 3e1baedb9284124b770d2d561a04a98c343d05967c83deb8b35c7c941f8d9c9a
Copy link
Copy Markdown
Member

@martincostello martincostello Feb 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This isn't about stability - it's about reproducibility and determinism.

Pinning means that the version doesn't silently change from under us and cause problems building the repo in the future, and it also mitigates about supply-chain attacks (e.g. a bad new version gets pushed which becomes the latest until it's noticed and taken down).

Essentially the exact same reason we pin GitHub Actions by their Git SHA.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's a good question

  • gh actions usually package some sort of code - and you want to have that pinned
  • mise uses mise.toml for the actual "payload"
  • the only thing that mise pins protect against
    • logic in installing packages
    • deprecated features being removed

to sum it up

  • I added this step when mise was less mature IMO
  • and propose to remove it now
  • either way, I think we should have it consistent across repos - but that's very easy to do either way using AI

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we should remove it, because we want the version to be deterministic.

mise is the subject of the pinning, and without pinning it the action will fetch a non-deterministic version here.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK, I'll revert for all repos then.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what do you think about adding the renovate rules for that in flint - since flint also uses mise?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't it already covered by the "_VERSION in GitHub Actions" preset?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah I see, it's a custom rule that works without you needing to add the comment usual comment (like this).

I was talking about the standard preset that keeps things updated if you have the comment, but that wouldn't work anyway because it's version: not _VERSION:.

In that case, yeah we can add that to flint.

@zeitlinger
Copy link
Copy Markdown
Member Author

Closing this — keeping the pinning per Martin's review. Instead, I'll move the renovate custom manager for mise to flint so all maintained repos get automatic version+sha256 update support, and add pinning to the repos that don't have it yet.

@zeitlinger zeitlinger closed this Feb 20, 2026
auto-merge was automatically disabled February 20, 2026 17:53

Pull request was closed

@zeitlinger zeitlinger deleted the remove-mise-version-pinning branch February 20, 2026 17:56
@zeitlinger
Copy link
Copy Markdown
Member Author

Here are the PRs to centralize mise renovate rules in flint and roll out version+sha256 pinning to all maintained repos:

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.

2 participants