Skip to content

Prepare 0.3.0 release - #13

Merged
maotora merged 2 commits into
mainfrom
chore/release-0.3.0
May 23, 2026
Merged

maotora merged 2 commits into
mainfrom
chore/release-0.3.0

Conversation

@maotora

@maotora maotora commented May 23, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Bump reveal-ui to 0.3.0 with a new CHANGELOG.md.
  • Refresh root and docs-site dependencies (Biome 2.4.15, Jest 30.4.x, Motion 12.40.0, React 19.2.6, Next.js 15.5.18, tailwind-merge 3.6.0).
  • Align the motion peer dependency to ^12.40.0.
  • Harden npm publishing for GitHub OIDC trusted publishing (npm whoami preflight, job-level id-token permission).
  • Add npm publish --dry-run to CI so tarball issues are caught before tagging.

Test plan

  • npm run ci passes locally
  • CI workflow passes on this PR
  • After merge: tag v0.3.0 on main and confirm Publish workflow succeeds via OIDC
  • Verify npm view reveal-ui version reports 0.3.0
  • Confirm GitHub Pages deploy still succeeds on main

Release notes

After this PR merges:

  1. Merge to main
  2. Create and push tag: git tag v0.3.0 && git push origin v0.3.0
  3. Watch the Publish workflow — OIDC npm whoami should pass before publish runs

Made with Cursor

maotora and others added 2 commits May 23, 2026 19:40
…ing.

Refresh toolchain and runtime deps, align the motion peer range, add changelog and CI publish dry-run, and verify npm OIDC auth before release publishes.

Co-authored-by: Cursor <cursoragent@cursor.com>
`npm publish --dry-run` was re-running prepublishOnly and breaking the smoke consumer tarball step.

Co-authored-by: Cursor <cursoragent@cursor.com>
@maotora
maotora merged commit 86ea4b0 into main May 23, 2026
4 checks passed
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.

1 participant