Skip to content

Conversation

sjungling
Copy link
Member

Reverts complex manual publishing workflow back to a simpler approach where
semantic-release handles all version management and publishing from dist/.

Key changes:

  • Reset package.json version to 0.0.0-development
  • Configure semantic-release to publish from dist/ directory (pkgRoot: dist)
  • Remove manual npm version/publish steps from workflow
  • Keep hybrid auth: registry-url for trusted publishing + NODE_AUTH_TOKEN fallback
  • Remove package.json from git assets (semantic-release shouldn't commit root version)

This matches the successful v4.0.0 approach while maintaining trusted publishing
support for enhanced security and provenance generation.

Reverts complex manual publishing workflow back to a simpler approach where
semantic-release handles all version management and publishing from dist/.

Key changes:
- Reset package.json version to 0.0.0-development
- Configure semantic-release to publish from dist/ directory (pkgRoot: dist)
- Remove manual npm version/publish steps from workflow
- Keep hybrid auth: registry-url for trusted publishing + NODE_AUTH_TOKEN fallback
- Remove package.json from git assets (semantic-release shouldn't commit root version)

This matches the successful v4.0.0 approach while maintaining trusted publishing
support for enhanced security and provenance generation.
@sjungling sjungling marked this pull request as ready for review September 24, 2025 16:58
@sjungling sjungling merged commit 6b87f80 into main Sep 24, 2025
3 checks passed
@sjungling sjungling deleted the chore/trusted-pub-v2 branch September 24, 2025 17:07
github-actions bot pushed a commit that referenced this pull request Sep 24, 2025
## [4.1.3](v4.1.2...v4.1.3) (2025-09-24)

### Bug Fixes

* simplify npm publishing by reverting to semantic-release approach ([#6](#6)) ([6b87f80](6b87f80))
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.

3 participants