ci(lotus): publish prereleases under the lotus dist-tag
CI / Build embedded bundle (push) Successful in 1m55s
CI / Publish to Gitea npm registry (push) Failing after 52s

Run #1861 built fine but `npm publish` refused: "You must specify a tag
using --tag when publishing a prerelease version" (npm 11 rule). Add
`--tag lotus`; cinny pins exact versions so the dist-tag is only a
namespace.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PPmy3tPq869XDW4njjVaKA
This commit is contained in:
Lotus CI
2026-09-12 14:36:05 -04:00
co-authored by Claude Opus 5
parent d203e7a33e
commit c0a2103822
+5 -1
View File
@@ -177,8 +177,12 @@ jobs:
TAG="${GITHUB_REF_NAME#v}" # v0.20.1-lotus.1 -> 0.20.1-lotus.1 TAG="${GITHUB_REF_NAME#v}" # v0.20.1-lotus.1 -> 0.20.1-lotus.1
npm version "$TAG" --no-git-tag-version --allow-same-version npm version "$TAG" --no-git-tag-version --allow-same-version
# `--tag lotus`: npm >= 11 refuses to publish a prerelease (x.y.z-lotus.N)
# without an explicit dist-tag (run #1861). cinny pins exact versions, so
# the dist-tag is only a namespace — it keeps `latest` pointing at the
# last upstream-parity publish.
- name: Publish - name: Publish
working-directory: embedded/web working-directory: embedded/web
env: env:
NODE_AUTH_TOKEN: ${{ secrets.GITEA_NPM_TOKEN }} NODE_AUTH_TOKEN: ${{ secrets.GITEA_NPM_TOKEN }}
run: npm publish --access public run: npm publish --access public --tag lotus