You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
default minimum release age will solve a lot of annoying problems: enabling node GPG verification, lack of pre-compiled binaries for recently released py versions, better security posture in general. We want to enable this by default but allow users to easily override it in their applications.
need to allow the user to customize minimum_release_age setting within their application
this needs to be respected when running latest to resolve a version within the host mise logic
this is hard to test since we would need to (a) customize the min age value passed to the host mise which is isolated from the config of the application and (b) hard to test with static data since the latest values are always changing + aging.
this only causes a failure if the latest value is contained in a lockfile. If latest or another unpinned version is specified, the logic works just fine.
if an exact version is specified, that should bypass all date filtering logic
all resolution runs through a mise latest call right now. latest does not short-circuit when an exact date is provided
minimum_release_agesetting within their applicationlatestto resolve a version within the host mise logiclatestor another unpinned version is specified, the logic works just fine.latestcall right now.latestdoes not short-circuit when an exact date is provided