Skip to content

Commit

Permalink
Bump version to 0.16.x, respect new tag names
Browse files Browse the repository at this point in the history
With 0.16.x, we started to release the lychee CLI binary separately from
the lychee library. As a consequence, the crates get prefixed differently
on GitHub releases:

- CLI binary: `lychee-v0.16.0`
- Library: `lychee-lib-v0.16.0`

We need to account for that when downloading the binary, as shown in this commit.
  • Loading branch information
mre committed Oct 7, 2024
1 parent e7546ad commit 88ffbfe
Showing 1 changed file with 6 additions and 2 deletions.
8 changes: 6 additions & 2 deletions action.yml
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ inputs:
required: false
lycheeVersion:
description: "Use custom version of lychee link checker"
default: v0.15.0
default: v0.16.1
required: false
output:
description: "Summary output file path"
Expand Down Expand Up @@ -60,8 +60,12 @@ runs:
# This determines the correct filename based on the version string.
if [[ '${{ inputs.lycheeVersion }}' =~ ^v0\.0|^v0\.1[0-5]\. ]]; then
echo "filename=lychee-${{ inputs.lycheeVersion }}-x86_64-unknown-linux-gnu.tar.gz" >> $GITHUB_OUTPUT
echo "tag=${{ inputs.lycheeVersion }}" >> $GITHUB_OUTPUT
else
echo "filename=lychee-x86_64-unknown-linux-gnu.tar.gz" >> $GITHUB_OUTPUT
# Each crate in the workspace has its own tag, so we need to specify the tag for the binary
# The binary is released under the 'lychee' tag, the library under 'lychee-lib'
echo "tag=lychee-${{ inputs.lycheeVersion }}" >> $GITHUB_OUTPUT
fi
shell: bash

Expand All @@ -75,7 +79,7 @@ runs:

- name: Download lychee
run: |
curl -sfLO "https://github.com/lycheeverse/lychee/releases/download/${{ inputs.lycheeVersion }}/${{ steps.lychee-filename.outputs.filename }}"
curl -sfLO "https://github.com/lycheeverse/lychee/releases/download/${{ steps.lychee-filename.outputs.tag }}/${{ steps.lychee-filename.outputs.filename }}"
shell: bash

- name: Extract lychee
Expand Down

0 comments on commit 88ffbfe

Please sign in to comment.