Repository navigation
ci: publish release candidates under latest - #2300
Merged
Merged
Conversation
|
Contributor
|
No actionable comments were generated in the recent review.
 |
| Layer / File(s) | Summary |
|---|---|
Publishing policy and tests CONTRIBUTING.md, scripts/publish-packages.mjs, scripts/publish-packages.test.mjs |
The publishing script assigns latest to every version. The tests expect latest for candidate publications and check failures by candidate version. Contributor guidance documents how to move an existing version to latest without republishing it. |
Release oracle alignment scripts/publish-history-oracle.property.test.js, scripts/publish-http-oracle.property.test.js, scripts/release-history-oracle.js, docs/contributing/oracle-coverage.md |
Release oracle expectations now use latest for candidate versions. The coverage notes distinguish historical rc-only evidence from the current policy and describe the scope of the oracles. |
Priority:
Estimated code review effort: 2 (Simple) | ~10 minutes
Change: Feature
Merge Risk: 
85e26
-
No actionable merge-blocking risk is established for this release-tag policy change.
Pre-merge checks: 
-
Check name Status Explanation Title check The title clearly and concisely identifies the main change: publishing release candidates under the latest tag. Docstring Coverage Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat… 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 follows the required template and fills every section. It states the change: future RC uploads move from the rctag tolatest, and stable packages keep theirlatestpublishing. T…Full details: Docstring Coverage
-
Explanation
Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 1 functions across 5 files. (2 skipped: 2 unsupported.)
Full details: Description check
-
Explanation
The description follows the required template and fills every section. It states the change: future RC uploads move from the
rctag tolatest, and stable packages keep theirlatestpublishing. The Oracle Coverage section names the coverage-map owners, the law under test, the reach, the validation run, and the limits. The author reports changed-file lint, formatting, and whitespace checks as passed, and states that no local tests or builds were run at the maintainer's instruction. The unchecked local-test box is explained. The Release Impact section marks the change as docs/CI/dev-only and explains that no existing version is retagged. The description is detailed and specific. Two items are not fully resolved: the Oracle Coverage section does not give RED/GREEN evidence for a bug fix, but this is not a bug fix, so that requirement does not apply. The description also lists open deferrals without resolving them, which the template allows.
-
Finishing Touches
-
📝 Generate docstrings
-
- Commit to this branch
- Create a new PR
🧪 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.
Comment @coderabbitai help to get the list of available commands.
More templates
@tanstack/angular-db
@tanstack/browser-db-sqlite-persistence
@tanstack/capacitor-db-sqlite-persistence
@tanstack/cloudflare-durable-objects-db-sqlite-persistence
@tanstack/convex-db-collection
@tanstack/db
@tanstack/db-ivm
@tanstack/db-sqlite-persistence-core
@tanstack/electric-db-collection
@tanstack/electron-db-sqlite-persistence
@tanstack/expo-db-sqlite-persistence
@tanstack/node-db-sqlite-persistence
@tanstack/offline-transactions
@tanstack/powersync-db-collection
@tanstack/preact-db
@tanstack/query-db-collection
@tanstack/react-db
@tanstack/react-native-db-sqlite-persistence
@tanstack/react-router-with-db
@tanstack/rxdb-db-collection
@tanstack/solid-db
@tanstack/svelte-db
@tanstack/tauri-db-sqlite-persistence
@tanstack/trailbase-db-collection
@tanstack/vue-db
commit: |
Contributor
|
Size Change: 0 B Total Size: 238 kB ℹ️ View Unchanged
|
1 of 2 tasks
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
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.
🎯 Changes
RC uploads currently use the
rctag, so unqualified installs continue to select the old stable line. Publish future candidate versions underlatest, as the maintainer explicitly directed on 2026-10-29. Query Collection and Offline Transactions retain their stable versions andlatestpublishing.Update the independent release model, command/HTTP oracle contract prose and wrong-tag calibration, supplemental release tests, and contributor policy together. Keep every history, observation, declared reach, and run budget. This changes the accepted tag policy; historical
rc-only campaign records remain preserved.Existing versions are still skipped by exact version. This PR does not promote already-published versions: use
npm dist-tag add <package>@1.0.0-rc.1 latestfor the 20 staged RC packages. That operation preserves their existingrcaliases. Future uploads uselatest; automatic movement of anrcalias is outside this change. PR #2299 has merged and main is integrated here. It restores Release test jobs and public publication eligibility for Convex Collection, Preact DB, and React Router with DB at 1.0.0-rc.1. Initial publication and trusted-publisher permissions for those three packages still require verification.🔬 Oracle Coverage
Coverage-map entry: RC release histories and replay observations, owned by
scripts/release-history-oracle.js, with command and HTTP receivers inscripts/publish-history-oracle.property.test.jsandscripts/publish-http-oracle.property.test.js. The RC npm tag policy, 2026-10-29 entry records the authority and execution limits.latest, independent of registry tag history; authority is the maintainer decision recorded in CONTRIBUTING.md.rcalias movement are not established by these owners. Full readiness is not assessed; known Ordered live query publishes new rows during a failed marker replay #2294, Multi-tab Electric: a deleted row returns after a peer reset and deploys #2281, Ordered loader retains earlier requests after a newer authoritative read succeeds #2296, and source-health oracle: reach check fails at random in CI #2287 deferrals remain.✅ Checklist
pnpm test.The maintainer explicitly prohibited further local tests and builds. CI supplies execution evidence; this checkbox remains unchecked.
🚀 Release Impact
The release tooling changes the tag for future uploads. It does not upload or retag any existing version by itself.
Summary by CodeRabbit
latesttag. Existing versions aren’t republished to change tags; use npm’s tag command to promote a version, preserving any existingrcalias.