You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Port the merged Workflow release pattern to RAG. release.yml, version.yml, Changesets configuration, and workflow linting are copied unchanged. The shared scripts are build, fast check, and test:e2e; RAG's check retains its circular-dependency check, and test:e2e runs an anonymous Convex deployment smoke test that generates code. PR CI runs fast checks before the smoke test and verifies committed component-generated files.
Verified: npm ci, build, 114 tests, typecheck, lint, circular-dependency check, Changesets status from a clean commit, npm pack dry run, and a clean-checkout anonymous smoke test with unchanged generated files. Both GitHub PR workflows pass against current main. The existing untracked todo.md was left untouched. GitHub Actions already allows release PR creation.
Before the first staged release, configure npm trusted publishing for @convex-dev/rag with workflow filename release.yml (npm requires the first successful publish within two days of registration). This PR has no version bump, so merging it should not stage a package.
No actionable comments were generated in the recent review.
Walkthrough
The changes add Changesets configuration, package scripts, and release guidance. The test workflow checks package changes and generated files. A new workflow prepares release PRs, and another selects, tests, stages, and tags package releases. The workflow lint actions are also updated.
Sequence Diagram(s)
sequenceDiagram
participant ReleaseWorkflow
participant PlanJob
participant BuildJob
participant StageJob
participant Npm
participant TagJob
participant GitRepository
ReleaseWorkflow->>PlanJob: Select and validate source commit and version
PlanJob->>BuildJob: Export selected commit, package, version, and channel
BuildJob->>StageJob: Upload tested package tarball and SHA-256 digest
StageJob->>Npm: Stage verified tarball with provenance and channel
StageJob->>TagJob: Continue after staging
TagJob->>GitRepository: Create or verify version tag at source commit
Loading
Change: Feature
Merge Risk: Minimal · up to 49f50
This PR moves releases to staged CI publishing with Changesets. No merge-blocking defect was found. Before merging, configure npm trusted publishing for the release workflow as the PR description states.
Pre-merge checks: 4
Check name
Status
Explanation
Title check
The title clearly describes the main change: moving RAG releases to staged CI publishing.
Linked Issues check
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
Check skipped because no linked issues were found for this pull request.
Description check
The description explains the Changesets-based release workflow, CI changes, validation performed, and npm trusted-publishing setup. It is directly related to the changeset.
Finishing Touches
Generate unit tests (beta)
Commit to this branch
Create a new PR
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
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.
File: No configuration file from this repository applied
Commit: Unavailable
Layers: Central YAML; Path: .coderabbit.yaml
Review profile: CHILL
Plan: Advanced
Run ID: 43eedf14-301f-412d-91df-879cffb7f4db
Commits
Reviewing files that changed from the base of the PR and between 0642974 and 49f5009.
Files ignored due to path filters: 1
package-lock.json is excluded by !**/package-lock.json
Files selected for processing: 8
.changeset/README.md
.changeset/config.json
.github/workflows/lint-workflows.yml
.github/workflows/release.yml
.github/workflows/test.yml
.github/workflows/version.yml
CONTRIBUTING.md
package.json
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.
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
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.
Port the merged Workflow release pattern to RAG.
release.yml,version.yml, Changesets configuration, and workflow linting are copied unchanged. The shared scripts arebuild, fastcheck, andtest:e2e; RAG'scheckretains its circular-dependency check, andtest:e2eruns an anonymous Convex deployment smoke test that generates code. PR CI runs fast checks before the smoke test and verifies committed component-generated files.Verified:
npm ci, build, 114 tests, typecheck, lint, circular-dependency check, Changesets status from a clean commit, npm pack dry run, and a clean-checkout anonymous smoke test with unchanged generated files. Both GitHub PR workflows pass against currentmain. The existing untrackedtodo.mdwas left untouched. GitHub Actions already allows release PR creation.Before the first staged release, configure npm trusted publishing for
@convex-dev/ragwith workflow filenamerelease.yml(npm requires the first successful publish within two days of registration). This PR has no version bump, so merging it should not stage a package.