chore(release): 1.0.0-rc.3 — the integration ecosystem#318
Merged
Conversation
Lockstep bump of all 30 publishable packages 1.0.0-rc.2 → 1.0.0-rc.3. Caret sibling peer ranges (^1.0.0-rc.1 / ^1.0.0-rc.2) already admit rc.3, so only the version fields move (per docs/RELEASING.md — peer ranges widen only on a major bump). CHANGELOG: promote [Unreleased] to [1.0.0-rc.3] and document the first wave of @stitchapi/* ecosystem adapters (server frameworks, client/UI bindings, data-fetching libs, state stores, auth, observability, AI). check:release ✓ (lockstep, peer coherence, access, dist-tag→rc, changelog, LICENSE+README) · prettier ✓ Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
What
Lockstep version bump
1.0.0-rc.2→1.0.0-rc.3across all 30 publishable packages, plus the CHANGELOG entry documenting the first wave of@stitchapi/*ecosystem adapters.Why
rc.3is the first release to ship the integration ecosystem — 21 new adapter packages added sincerc.2(server frameworks, client/UI bindings, data-fetching libs, state stores, auth, observability, AI). They were merged without a grouped CHANGELOG entry; this release gives them one.Changes
1.0.0-rc.3in all 30 publishablepackages/*/package.json. Caret sibling peer ranges (^1.0.0-rc.1/^1.0.0-rc.2) already admitrc.3, so perdocs/RELEASING.mdthey stay put (peer ranges widen only on a major bump).[Unreleased]→[1.0.0-rc.3] — 2026-06-21, added the "the integration ecosystem" section, refreshed compare links.Verification
pnpm check:release --changelog --tag rc✓ — lockstep (30 @ rc.3), peer coherence (39 ranges admit rc.3), scoped access, dist-tag →rc, CHANGELOG entry present, LICENSE+README in all 30prettier --check✓OIDC trusted publishing cannot publish a brand-new package name. These 21 packages have never been on npm, so their first publish must be a manual interactive-2FA bootstrap (
npm login→pnpm -r publish --tag rc), after which a Trusted Publisher is attached on npmjs.com and they ridenpm-publish.ymllikestitchapi/nest/redis. Seedocs/RELEASING.md→ Bootstrapping a new package's first publish. The GitHub-release-triggered workflow alone will not deploy them.🤖 Generated with Claude Code