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
Since the https://github.com/owner/repo/releases/latest/download/stack.tar.gz url should always link to the latest release tag, I would expect the stack validation to work successfully and the remix project to initialize successfully.
Actual Behavior
The command fails with the following error: 🚨 The template file could not be verified. Please double check the URL and try again.
However, if you do know the latest release tag, manually include it, and try again:
I suspect this is because there's a quirk in the Github URL structure between the latest tag and a specified version (releases/latest/download vs. releases/download/version) and the Remix code isn't handling the former.
My org maintains a private Github monorepo that includes a stack tarball and it would be great to allow users to link directly to the latest release instead of having to know the exact version number.
The text was updated successfully, but these errors were encountered:
We just published version v0.0.0-nightly-eebaa56-20221013 which involves this issue. If you'd like to take it for a test run please try it out and let us know what you think!
What version of Remix are you using?
1.7.2
Steps to Reproduce
Instantiate a stack using a template from a private GitHub repo, an access token, and the "latest" release url:
Expected Behavior
Since the
https://github.com/owner/repo/releases/latest/download/stack.tar.gz
url should always link to the latest release tag, I would expect the stack validation to work successfully and the remix project to initialize successfully.Actual Behavior
The command fails with the following error:
🚨 The template file could not be verified. Please double check the URL and try again.
However, if you do know the latest release tag, manually include it, and try again:
Then it works just fine.
I suspect this is because there's a quirk in the Github URL structure between the latest tag and a specified version (
releases/latest/download
vs.releases/download/version
) and the Remix code isn't handling the former.My org maintains a private Github monorepo that includes a stack tarball and it would be great to allow users to link directly to the latest release instead of having to know the exact version number.
The text was updated successfully, but these errors were encountered: