habsi/elasticsearch-js
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Ensure npm publish succeeds when publishing non-latest versions (#2754)

Browse Source
This commit is contained in:
Josh Mock
2025-04-16 11:02:28 -05:00
committed by GitHub
parent 1650e3d264
commit d726942ad1
1 changed files with 12 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
.github/workflows/npm-publish.yml vendored
View File

@ -27,9 +27,20 @@ jobs:
run: | run: |
version=$(jq -r .version package.json) version=$(jq -r .version package.json)
tag_meta=$(echo "$version" | cut -s -d '-' -f2) tag_meta=$(echo "$version" | cut -s -d '-' -f2)
# if no meta info on the version (e.g. a '-alpha.1' prefix), publish as a stable release
if [[ -z "$tag_meta" ]]; then if [[ -z "$tag_meta" ]]; then
# get latest version on npm
latest=$(npm view @elastic/elasticsearch --json | jq -r '.["dist-tags"].latest')
# if $version is higher than the most recently published version, publish as-is
if [[ $(yes | npx semver "$version" "$latest" | tail -n1) == "$version" ]]; then
npm publish --provenance --access public npm publish --provenance --access public
else else
# otherwise, publish with "previous" tag
npm publish --provenance --access public --tag "previous"
fi
else
# publish as a non-stable release using the meta name (e.g. 'alpha') as the tag
tag=$(echo "$tag_meta" | cut -d '.' -f1) tag=$(echo "$tag_meta" | cut -d '.' -f1)
npm publish --provenance --access public --tag "$tag" npm publish --provenance --access public --tag "$tag"
fi fi