fix(mise): minimum age does not cause pinned versions to fail#575
Merged
Conversation
Generated-by: aiautocommit
Generated-by: aiautocommit
* Automate upgrading the dependencies for the Python example project during the mise-upgrade task. * Ensure the repository remains current with the latest versions during the automated maintenance flow. Generated-by: aiautocommit
Generated-by: aiautocommit
- Remove the hardcoded MISE_MINIMUM_RELEASE_AGE environment variable to allow configuration via system defaults or user settings. Generated-by: aiautocommit
- Update the node version expectation to accept any valid version string when configured as "latest". - This avoids brittle test failures caused by the actual "latest" version changing over time. Generated-by: aiautocommit
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
Railpack sets a default
minimum_release_ageof 14 days in generated container mise configs to avoid very new tool releases (missing binaries, GPG verification gaps, etc.). Host-side version resolution during build plan generation did not apply the same filter, so builds could fail whenmise.tomlrequestslatestbutmise.lockpins a release newer than that window.Fixes #571
Description
Host
GetLatestVersionnow resolves fuzzy constraints withMISE_MINIMUM_RELEASE_AGE=14dfirst, then falls back to unfiltered resolution when nothing matches (e.g. a lockfile pins a version inside the age window). A globalMISE_MINIMUM_RELEASE_AGEon every host mise invocation was removed so only this resolution path applies the filter.Adds
examples/python-uv-latest-lockedto exerciselatesttools with a shortminimum_release_ageand a lockfile that pins edge releases. Themise-upgradetask upgrades that example's dependencies as part of routine maintenance.Also includes GitHub Actions version bump tooling and a snapshot refresh for
pnpm-corepack-runtime-usage.Test
examples/python-uv-latest-lockedasserts resolved Python/uv versions at build timepython-uv-latest-lockedlatest