Skip to content

Trust generated mise config before running mise env/install - #2414

Open
eon-pulumi-agent[bot] wants to merge 2 commits into
masterfrom
fix-2413-mise-trust-postupgrade
Open

Trust generated mise config before running mise env/install#2414
eon-pulumi-agent[bot] wants to merge 2 commits into
masterfrom
fix-2413-mise-trust-postupgrade

Conversation

@eon-pulumi-agent

@eon-pulumi-agent eon-pulumi-agent Bot commented Jul 22, 2026

Copy link
Copy Markdown

What changed

Renovate can run make renovate before mise trusts the generated .config/mise.toml. This stops SDK and schema files from being regenerated after dependency updates.

This PR makes the generated renovate target trust the mise config before running the provider’s Renovate script. Other Makefile targets are unchanged.

Fixes #2413.

Alternative / possible follow-up

We could instead configure the Renovate runner to trust mise configs globally using MISE_TRUSTED_CONFIG_PATHS or MISE_YES=1. That would cover all uses of mise in Renovate, but it would grant broader trust and require a change outside this repository.

Reviewer feedback on whether the scoped fix in this PR or a central Renovate configuration is preferable would be welcome.

Testing

  • cd provider-ci && make all

@pose pose left a comment

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.

@corymhall I would like to this discuss this since it's related to: https://github.com/pulumi/home/issues/4462#issuecomment-4934728789

@corymhall
corymhall removed their request for review July 23, 2026 12:30
corymhall and others added 2 commits July 24, 2026 14:07
Renovate's postUpgradeTasks runner (and any other environment that
hasn't pre-trusted the repo) causes 'mise env'/'mise install' to abort
with 'Config files ... are not trusted', which in turn aborts
'make renovate' -> 'make generate_sdks' before any artifacts are
regenerated. The PR then lands with the dependency bumped but stale
generated SDK/schema output.

Run 'mise trust --yes -q' ahead of 'mise env -q' and 'mise install -q'
in the generated Makefile's mise_env / .make/mise_install targets so
mise commands work regardless of whether the runner has pre-trusted
the generated .config/mise.toml. This is the first suggested fix from
issue #2413.

Fixes #2413
Trusting the generated .config/mise.toml in the shared mise_env/
.make/mise_install targets affects every provider and every make
invocation, not just Renovate. Since the mise config staleness
problem only manifests in Renovate's postUpgradeTasks runner, move
the 'mise trust --yes -q' call into the generated 'renovate' Makefile
target instead (only rendered when .Config.RenovateCmd is set), right
before it invokes the provider's renovate command. Trust is persisted
by mise, so this covers the recursive 'make generate_sdks' invocation
that renovate.sh performs.

This reduces the diff footprint to only the providers that opt into
RenovateCmd (currently just the eks test provider) plus the two
template files.
@pose
pose force-pushed the fix-2413-mise-trust-postupgrade branch from f2d413a to 2dc6727 Compare July 24, 2026 13:07
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.

Renovate postUpgradeTasks fail on untrusted mise config, leaving generated artifacts stale

2 participants