The automated script generated this PR, which updates the check-release.sh script.
Explaination
check-release.yml used to parse the GITHUB_REF with tr -d 'refs/tags/v'. But, tr deletes characters and not a specific string.
Which results in a wrong parsing of tags containings the characters present in refs/tags/v.
Example:
refs/tags/v0.1.0-strapi-v3.1 becomes 0.1.0-pi-v3.1
To avoid this issue, the command is changed to a more robust parsing method: cut -d '/' -f 3 | sed -r 's/^v//'
cut -d '/' -f 3 splits our string based on the / and takes the 3th element.
refs/tags/v0.1.0-strapi-v3.1 => ["refs", "tags", "v0.1.0-strapi-v3.1"]
sed -r 's/^v//' removes the prepending v.
v0.1.0-strapi-v3.1 => 0.1.0-strapi-v3.1
meili-bors[bot]
commented
1 year ago
This PR is auto-generated.
The automated script generated this PR, which updates the check-release.sh script.
Explaination
check-release.ymlused to parse theGITHUB_REFwithtr -d 'refs/tags/v'. But,trdeletes characters and not a specific string. Which results in a wrong parsing of tags containings the characters present inrefs/tags/v. Example:refs/tags/v0.1.0-strapi-v3.1becomes0.1.0-pi-v3.1To avoid this issue, the command is changed to a more robust parsing method:
cut -d '/' -f 3 | sed -r 's/^v//'cut -d '/' -f 3splits our string based on the/and takes the 3th element.refs/tags/v0.1.0-strapi-v3.1=>["refs", "tags", "v0.1.0-strapi-v3.1"]sed -r 's/^v//'removes the prependingv.v0.1.0-strapi-v3.1=>0.1.0-strapi-v3.1