-
-
Notifications
You must be signed in to change notification settings - Fork 132
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
Harmonizes naming pattern of pre-built binaries and unlocks latest permalink #1464
Conversation
|
The test fails seem to be unrelated to my changes. Their implementation contains remarks about flakyness. Maybe increasing the number of re-tries or adding a delay in between would help to reduce the ci-noise. |
removes tag names to unlock latest-permalink
changes macos and windows release assets to follow linux naming scheme: lychee-{cpu}-{platform}.{ext}
d0d0afe
to
3f00c2a
Compare
Thanks @axel-kah! The code looks fine. I didn't find a great way to test it, but we'll give it a shot with the next release. 👍 |
Sweet! Any idea when that will be (ballpark)? |
The name of the `.tar` file is repeated multiple times, verbatim. This not only violates the Don't Repeat Yourself (DRY) principle, it also makes it easier to miss an instance when the file name changes (as it did with lycheeverse/lychee#1464). Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Until version 0.15.1, the naming scheme of the release assets let them start with `lychee-<version>-`. This is no longer the case as of lycheeverse/lychee#1464, though, breaking the `lychee-action`. Since we need to allow using older versions, still, we are now stuck with a really ugly `case` construct, but this is still far better than having a broken GitHub Action. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
The name of the `.tar` file is repeated multiple times, verbatim. This not only violates the Don't Repeat Yourself (DRY) principle, it also makes it easier to miss an instance when the file name changes (as it did with lycheeverse/lychee#1464). Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Until version 0.15.1, the naming scheme of the release assets let them start with `lychee-<version>-`. This is no longer the case as of lycheeverse/lychee#1464, though, breaking the `lychee-action`. Since we need to allow using older versions, still, we are now stuck with a really ugly `case` construct, but this is still far better than having a broken GitHub Action. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Until version 0.15.1, the naming scheme of the release assets let them start with `lychee-<version>-`. This is no longer the case as of lycheeverse/lychee#1464, though, breaking the `lychee-action`. Since we need to allow using older versions, still, we are now stuck with a really ugly `case` construct, but this is still far better than having a broken GitHub Action. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
We got some issues with the change. Follow lycheeverse/lychee-action#232 and lycheeverse/lychee-action#234 for updates. |
Work around new naming scheme Until version 0.15.1, the naming scheme of the release assets let them start with `lychee-<version>-`. This is no longer the case as of lycheeverse/lychee#1464, though, breaking the `lychee-action`. Since we need to allow using older versions, still, we are now stuck with a really ugly `case` construct, but this is still far better than having a broken GitHub Action. The name of the `.tar` file is repeated multiple times, verbatim. This not only violates the Don't Repeat Yourself (DRY) principle, it also makes it easier to miss an instance when the file name changes (as it did with lycheeverse/lychee#1464). DRY up the lengthy `.tar` file name. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
This closes #1463