Repository navigation
ci: update TanStack config pins for Changesets v3 - #397
benjavicente wants to merge 1 commit into
Conversation
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
|
View your CI Pipeline Execution ↗ for commit 1c7703e
☁️ Nx Cloud last updated this comment at |
@tanstack/angular-store
@tanstack/lit-store
@tanstack/octane-store
@tanstack/preact-store
@tanstack/react-store
@tanstack/solid-store
@tanstack/store
@tanstack/svelte-store
@tanstack/vue-store
commit: |
🎯 Changes
The repository uses Changesets v3, but the older TanStack/config action pin still installs
@changesets/get-release-plan ^4.0.16for version previews. Update the config action pins to466151b2d479656b38942cd84a0a3dce29d48de3, which uses@changesets/get-release-plan ^5.0.0and aligns the preview tooling with Changesets v3.This picks up TanStack/config#422, following the same pin update as TanStack/form#2437. Setup and release-comment references are kept on the same config revision.
This overlaps with the automated pin update in #396.
Confirmed reproduction: Store's prerelease Version Preview installed Changesets CLI 3.0.3 and used config pin
7bbdf58, then failed withENOENTopening.changeset/pre/changes.md. A second prerelease run failed opening.changeset/pre/changes.json. These match the prerelease-directory incompatibility fixed in TanStack/config#422.This PR updates
main. The correspondingalphafix is #398, where the reproduced failure occurs.Validation: reviewed the pin-only diff and checked that the workflow YAML parses with no structural changes. Package test suites were not run for this CI-only change; workflow execution is left to PR CI.
Prepared with the Codex agent at the author's request.
✅ Checklist
pnpm test:pr, or these tests do not apply to this pull request.🚀 Release Impact
Summary by CodeRabbit