mise upgrade for granted resolves 0.39.0, but the Common Fate release URL returns 404
#934
garysassano
started this conversation in
General
Replies: 1 comment 2 replies
|
New releases of Granted are being published at releases.granted.dev. See the release infrastructure changes section here: https://github.com/fwdcloudsec/granted/releases/tag/v0.39.0. Sorry for any pain this has caused. We don’t maintain the mise or aqua packages - could you please raise an issue or make a pull request on those projects to request an update? If you can link back any relevant issues or PRs to this discussion that would be great, in case other Granted users hit the same issue. |
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi, I ran into an issue upgrading
grantedthroughmise, and it looks like there may be a mismatch between the published GitHub release assets and thereleases.commonfate.ioURL thatmise/aquais trying to download.Environment
mise --version:2026.3.17 linux-x64 (2026-03-27)x86_64LinuxWhat happens
Running:
fails with:
What I verified
The exact URL
misetries to download returns404:Response:
For comparison, the previous release artifact is available:
Response:
At the same time, the GitHub
v0.39.0release page does appear to contain the Linux tarball asset:granted_0.39.0_linux_x86_64.tar.gzSo this looks like one of:
releases.commonfate.iohas not synced the asset yet,v0.39.0,mise/aquametadata is pointing at the wrong distribution URL template.Question
Is
v0.39.0expected to be installable fromreleases.commonfate.ioyet?If yes, could someone check why this specific asset URL returns
404even though the asset appears on the GitHub release?If no, what is the supported installation source for
mise/aquausers forv0.39.0?Temporary workaround
Pinning to
0.38.0still works, since the corresponding release URL returns200.All reactions