Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Specifying lycheeVersion as "nightly" broken #232

Closed
osslate opened this issue Jun 20, 2024 · 6 comments
Closed

Specifying lycheeVersion as "nightly" broken #232

osslate opened this issue Jun 20, 2024 · 6 comments

Comments

@osslate
Copy link

osslate commented Jun 20, 2024

As the GitHub Action prepends "v" to the lycheeVersion (so it becomes vnightly instead of nightly) when grabbing the binary from GitHub, trying to use the nightly version with this GitHub Action is broken.

@mre
Copy link
Member

mre commented Jun 20, 2024

Oh well.

Wonder how we can fix it.

@osslate
Copy link
Author

osslate commented Jun 21, 2024

To avoid breaking compatibility with people already using the Action, a solution might be introducing a useNightly option that overrides lycheeVersion.

@mre
Copy link
Member

mre commented Jun 21, 2024

We could introduce a breaking change with a new version but yeah, it's not ideal. Alternatively, we could check if version is nightly and avoid prepending the v.

@dscho
Copy link
Contributor

dscho commented Aug 12, 2024

Seems that this is broken even on master now, because the nightly artifact changed name from lychee-nightly-x86_64-unknown-linux-gnu.tar.gz to lychee-x86_64-unknown-linux-gnu.tar.gz (note the removed infix nightly-).

@dscho
Copy link
Contributor

dscho commented Aug 12, 2024

Seems that this is broken even on master now

The reason seems to be lycheeverse/lychee#1464, which renamed the release assets. Note: This will be a major problem once the next lychee version is released, because then not only the nightly version will be broken.

I opened #234 to fix that.

mre added a commit that referenced this issue Aug 20, 2024
This is a consequence of #232. It adds a few additional tests for special lychee versions to avoid breaking changes in the future.
mre added a commit that referenced this issue Aug 20, 2024
This is a consequence of #232. It adds a few additional tests for special lychee versions to avoid breaking changes in the future.
@mre
Copy link
Member

mre commented Aug 20, 2024

@dscho fixed it. @osslate, please try again. 😊
If it doesn't work as expected, please reopen.

@mre mre closed this as completed Aug 20, 2024
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

No branches or pull requests

3 participants