Skip to content

ci: TAG_NAME from release or package.json (v-${version})#12

Merged
proxymesh merged 3 commits intomainfrom
ci/publish-tag-name-fallback
Mar 21, 2026
Merged

ci: TAG_NAME from release or package.json (v-${version})#12
proxymesh merged 3 commits intomainfrom
ci/publish-tag-name-fallback

Conversation

@proxymeshai
Copy link
Collaborator

Summary

  • When github.event.release.tag_name is set (release published), use it for the version/tag check.
  • When it is empty (workflow_dispatch), set TAG_NAME to v-${package.json version} (e.g. v-0.2.0).
  • Allow matching tags: 0.2.0, v0.2.0, or v-0.2.0.

Made with Cursor

Use github.event.release.tag_name when set; otherwise set TAG_NAME to
v-${version} from package.json so workflow_dispatch matches semver.
Accept v0.2.0, 0.2.0, and v-0.2.0 in the version check.

Made-with: Cursor
setup-node with registry-url injects a dummy NODE_AUTH_TOKEN when unset,
so npm publish used that instead of trusted publishing and returned 404.
Use Node 22 + npm >=11.5.1 per npm trusted publishing requirements.

Made-with: Cursor
deno publish (used by jsr) rejects --provenance; use plain npx jsr publish
with id-token: write per JSR docs.

Made-with: Cursor
@proxymesh proxymesh merged commit a0bde06 into main Mar 21, 2026
1 check failed
@proxymesh proxymesh deleted the ci/publish-tag-name-fallback branch March 21, 2026 22:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants