ci: integrate release-please for automated releases#33
Merged
jeff-atriumn merged 2 commits intomainfrom Feb 26, 2026
Merged
Conversation
- Add Contributor Covenant CODE_OF_CONDUCT.md - Add CHANGELOG.md (Keep a Changelog format) - Add homepage and bugs fields to package.json, include LICENSE in npm package - Add GitHub issue templates (bug report, feature request) and PR template - Expand Getting Started with Claude Desktop, VS Code, Windsurf instructions - Add FAQ docs page covering data freshness, accuracy, troubleshooting Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Adds release-please GitHub Action to automate versioning, changelog generation, and GitHub Releases on push to main. Removes the manual GitHub Release step from release.yml to avoid conflicts. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
jeff-atriumn
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Change Summary
Integrates Google's release-please to automate versioning, changelog generation, and GitHub Releases. This replaces the manual process of bumping
package.jsonand pushingv*tags.What changed:
release-please.ymlworkflow — runs on push tomain, creates/updates a release PRrelease-please-config.json— node release type, cleanvX.Y.Ztags, conservative pre-1.0 bumping.release-please-manifest.json— tracks current version (0.1.1)Create GitHub Releasestep fromrelease.yml(release-please handles this now)contents: write→contents: readon the publish jobCHANGELOG.mdto match release-please's format (removed[Unreleased]section and footer reference links)New release flow:
mainrelease.yml→ typecheck, test, npm publishRisk & Impact Assessment
Risk Level: low
mainpushrelease.ymlnpm publish pipeline is unchanged (still triggers onv*tags)Test Plan
release.ymlstill has correct structure after removing the GitHub Release stepManual Verification Steps
mainrelease.ymlstill triggers correctly on tag push🤖 Generated with Claude Code