Skip to content

Conversation

@crisap94
Copy link
Member

@crisap94 crisap94 commented Jan 7, 2026

Test PR to verify automated deployment workflow.

This PR bumps the version to 0.2.8 to test that:

  • Workflow triggers automatically on merge to main
  • Version is extracted correctly
  • NPM tag is detected as 'latest'
  • Package publishes to npm with OIDC
  • GitHub release is created automatically

Summary by CodeRabbit

  • Chores
    • Version bumped to 0.2.8

✏️ Tip: You can customize this high-level summary in your review settings.

@coderabbitai
Copy link

coderabbitai bot commented Jan 7, 2026

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

The package version is updated from 0.2.8 to 0.2.8 in package.json. No changes to dependencies, scripts, exports, or codebase logic. This is a routine version increment.

Changes

Cohort / File(s) Summary
Version Bump
package.json
Version field incremented from 0.2.7 to 0.2.8 for release tagging and deployment.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

Poem

🐰✨
A digit danced, from seven to eight,
Version bumped at a perfect rate,
Release tags flow, deployment's near,
Rabbit's work complete this year! 🚀


📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 30cc960 and 6388651.

📒 Files selected for processing (1)
  • package.json

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions
Copy link

github-actions bot commented Jan 7, 2026

🔍 PR Quality Check Summary

Check Status
Code Quality & Tests ✅ success
Security Audit ✅ success

📋 Checks Performed:

  • ✅ TypeScript compilation
  • ✅ ESLint code quality
  • ✅ Prettier code formatting
  • ✅ Unit tests with coverage (80%+ required)
  • ✅ Build verification
  • ✅ Security audit

🎉 All checks passed! This PR is ready for review.

@crisap94 crisap94 merged commit f16a0b5 into main Jan 7, 2026
3 of 4 checks passed
@crisap94 crisap94 deleted the test/version-bump-0.2.8 branch January 7, 2026 17:05
crisap94 added a commit that referenced this pull request Jan 7, 2026
After 4 failed attempts with OIDC trusted publishing (#20, #21, #22, #23),
we're switching to the more reliable traditional npm token authentication.

Changes:
- Add registry-url back to setup-node
- Add NODE_AUTH_TOKEN env using NPM_TOKEN secret
- Bump version to 0.2.12
- Keep --provenance flag for supply chain security

Required setup:
1. Create npm automation token at https://www.npmjs.com/settings/[username]/tokens/create
2. Add as GitHub secret: NPM_TOKEN

Benefits:
✅ Battle-tested and reliable
✅ Still supports provenance attestation
✅ No OIDC configuration issues

Trade-offs:
⚠️ Requires manual token management
⚠️ Token needs rotation
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