Version Packages#725
Conversation
Deploying stackflow-demo with
|
| Latest commit: |
f0db947
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://094a1e36.stackflow-demo.pages.dev |
| Branch Preview URL: | https://changeset-release-main.stackflow-demo.pages.dev |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
stackflow-docs | f0db947 | Commit Preview URL | Jul 11 2026, 02:55 PM |
📝 WalkthroughSummary by CodeRabbit
WalkthroughThe release updates Stackflow core to 3.0.0, documents snapshot-related API changes and ChangesCore release documentation
History-sync release
Dependent package alignment
Estimated code review effort: 2 (Simple) | ~15 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
@stackflow/core
@stackflow/link
@stackflow/plugin-basic-ui
@stackflow/plugin-blocker
@stackflow/plugin-devtools
@stackflow/plugin-google-analytics-4
@stackflow/plugin-history-sync
@stackflow/plugin-lifecycle
@stackflow/plugin-renderer-basic
@stackflow/plugin-renderer-web
@stackflow/plugin-sentry
@stackflow/plugin-stack-depth-change
@stackflow/react-ui-core
@stackflow/react
commit: |
612e3c0 to
f0db947
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@extensions/plugin-lifecycle/package.json`:
- Line 3: Update the .changeset entries driving this release to use minor or
major severity for extensions/plugin-lifecycle/package.json (line 3;
peerDependency line 64), extensions/plugin-renderer-basic/package.json (line 3;
peerDependency line 44), extensions/plugin-renderer-web/package.json (line 3;
peerDependency line 44), and extensions/plugin-sentry/package.json (line 3;
peerDependency line 35), then rerun the changesets bot to regenerate the
corresponding version bumps. The peerDependency declarations at those referenced
lines require no direct change. Re-level the 1.1.7 entry in
extensions/plugin-stack-depth-change/CHANGELOG.md (lines 3-9) to minor or major
if its peerDependency also changed to ^3.0.0.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: fa4ea82f-ee1d-45c0-952b-3ed9d953883e
⛔ Files ignored due to path filters (1)
yarn.lockis excluded by!**/yarn.lock,!**/*.lock
📒 Files selected for processing (34)
.changeset/tidy-bats-context.mdcore/CHANGELOG.mdcore/package.jsondemo/CHANGELOG.mddemo/package.jsondocs/CHANGELOG.mddocs/components/ChangelogContent.mdxdocs/package.jsonextensions/link/CHANGELOG.mdextensions/link/package.jsonextensions/plugin-basic-ui/CHANGELOG.mdextensions/plugin-basic-ui/package.jsonextensions/plugin-blocker/CHANGELOG.mdextensions/plugin-blocker/package.jsonextensions/plugin-devtools/CHANGELOG.mdextensions/plugin-devtools/package.jsonextensions/plugin-google-analytics-4/CHANGELOG.mdextensions/plugin-google-analytics-4/package.jsonextensions/plugin-history-sync/CHANGELOG.mdextensions/plugin-history-sync/package.jsonextensions/plugin-lifecycle/CHANGELOG.mdextensions/plugin-lifecycle/package.jsonextensions/plugin-renderer-basic/CHANGELOG.mdextensions/plugin-renderer-basic/package.jsonextensions/plugin-renderer-web/CHANGELOG.mdextensions/plugin-renderer-web/package.jsonextensions/plugin-sentry/CHANGELOG.mdextensions/plugin-sentry/package.jsonextensions/plugin-stack-depth-change/CHANGELOG.mdextensions/plugin-stack-depth-change/package.jsonextensions/react-ui-core/CHANGELOG.mdextensions/react-ui-core/package.jsonintegrations/react/CHANGELOG.mdintegrations/react/package.json
💤 Files with no reviewable changes (1)
- .changeset/tidy-bats-context.md
✅ Files skipped from review due to trivial changes (16)
- extensions/plugin-devtools/CHANGELOG.md
- extensions/plugin-renderer-basic/CHANGELOG.md
- extensions/react-ui-core/CHANGELOG.md
- extensions/plugin-sentry/CHANGELOG.md
- core/package.json
- core/CHANGELOG.md
- extensions/link/CHANGELOG.md
- extensions/plugin-basic-ui/CHANGELOG.md
- extensions/plugin-blocker/CHANGELOG.md
- extensions/plugin-lifecycle/CHANGELOG.md
- integrations/react/CHANGELOG.md
- extensions/plugin-google-analytics-4/CHANGELOG.md
- demo/CHANGELOG.md
- docs/components/ChangelogContent.mdx
- extensions/plugin-renderer-web/CHANGELOG.md
- extensions/plugin-history-sync/CHANGELOG.md
| { | ||
| "name": "@stackflow/plugin-lifecycle", | ||
| "version": "0.1.1", | ||
| "version": "0.1.2", |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win
All plugin packages receive patch bumps despite a major peerDependency range change on @stackflow/core. The shared root cause is that the changesets driving this release assigned patch-level version bumps to packages whose @stackflow/core peerDependency moved from ^2.0.0 to ^3.0.0. A peerDependency range that drops support for a previously-supported major version is a breaking change for consumers — installing these plugins alongside @stackflow/core@2.x will produce peer dependency errors. Per semver, these packages should receive at least a minor (ideally major) version bump.
extensions/plugin-lifecycle/package.json#L3-L3: bump 0.1.2 to at least 0.2.0 (or 1.0.0) to reflect the breaking peerDependency change at L64.extensions/plugin-lifecycle/package.json#L64-L64: peerDependency^3.0.0is correct; the package version at L3 needs to reflect this breaking change.extensions/plugin-renderer-basic/package.json#L3-L3: bump 1.1.15 to at least 1.2.0 (or 2.0.0) to reflect the breaking peerDependency change at L44.extensions/plugin-renderer-basic/package.json#L44-L44: peerDependency^3.0.0is correct; the package version at L3 needs to reflect this breaking change.extensions/plugin-renderer-web/package.json#L3-L3: bump 1.1.15 to at least 1.2.0 (or 2.0.0) to reflect the breaking peerDependency change at L44.extensions/plugin-renderer-web/package.json#L44-L44: peerDependency^3.0.0is correct; the package version at L3 needs to reflect this breaking change.extensions/plugin-sentry/package.json#L3-L3: bump 0.1.2 to at least 0.2.0 (or 1.0.0) to reflect the breaking peerDependency change at L35.extensions/plugin-sentry/package.json#L35-L35: peerDependency^3.0.0is correct; the package version at L3 needs to reflect this breaking change.extensions/plugin-stack-depth-change/CHANGELOG.md#L3-L9: the 1.1.7 patch entry should be re-leveled to at least minor/major if the package's peerDependency range also changed to^3.0.0.
To fix: update the changeset files (in .changeset/) that generated this release to use minor or major severity for these packages, then re-run the changesets bot to regenerate this PR with correct version bumps.
📍 Affects 5 files
extensions/plugin-lifecycle/package.json#L3-L3(this comment)extensions/plugin-lifecycle/package.json#L64-L64extensions/plugin-renderer-basic/package.json#L3-L3extensions/plugin-renderer-basic/package.json#L44-L44extensions/plugin-renderer-web/package.json#L3-L3extensions/plugin-renderer-web/package.json#L44-L44extensions/plugin-sentry/package.json#L3-L3extensions/plugin-sentry/package.json#L35-L35extensions/plugin-stack-depth-change/CHANGELOG.md#L3-L9
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@extensions/plugin-lifecycle/package.json` at line 3, Update the .changeset
entries driving this release to use minor or major severity for
extensions/plugin-lifecycle/package.json (line 3; peerDependency line 64),
extensions/plugin-renderer-basic/package.json (line 3; peerDependency line 44),
extensions/plugin-renderer-web/package.json (line 3; peerDependency line 44),
and extensions/plugin-sentry/package.json (line 3; peerDependency line 35), then
rerun the changesets bot to regenerate the corresponding version bumps. The
peerDependency declarations at those referenced lines require no direct change.
Re-level the 1.1.7 entry in extensions/plugin-stack-depth-change/CHANGELOG.md
(lines 3-9) to minor or major if its peerDependency also changed to ^3.0.0.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@stackflow/core@3.0.0
Major Changes
f0fc1fb: Distinguish how a stack is initialized — created fresh (
create) or restored from a snapshot (load) — and add the surface a snapshot round-trip needs:StackSnapshot,actions.captureSnapshot(), theprovideSnapshot/onLoadErrorplugin hooks, andinitInfoononInit. Runtime behavior is unchanged when no snapshot is provided; the breaks are type-level only — theStackflowPluginHook→StackflowPluginInitHookrename, plus new required members onStackflowActionsand on theonInit/overrideInitialEventshook signatures — hence the major.Added
StackSnapshot(with theSnapshotEvent/NavigationEventunions) — a plain-data record of the events a stack recorded at runtime — plusSnapshotLoadError.actions.captureSnapshot()to export that record, and theprovideSnapshot/onLoadErrorplugin hooks to supply a snapshot at creation time and route a failed load.initInfo: { kind: "create" | "load" }ononInit;overrideInitialEventsnow runs on the load path too and receives the sameinitInfo.Changed
StackflowPluginHooktype toStackflowPluginInitHook.StackflowActionsnow requirescaptureSnapshot, theonInit/overrideInitialEventshook arguments now requireinitInfo, andoverrideInitialEvents' parameter widens from(PushedEvent | StepPushedEvent)[]toSnapshotEvent[]— hand-written mocks and wrap-and-forward plugins must adopt these.validateEventsnow also rejects aReplacedthat names an unregistered activity (does not fire in config-first usage).@stackflow/plugin-history-sync@1.12.0
Minor Changes
initialContextto routedefaultHistorycallbacks so the initial stack can depend on request-specific context.Patch Changes
@stackflow/link@2.0.1
Patch Changes
@stackflow/plugin-basic-ui@1.18.3
Patch Changes
@stackflow/plugin-blocker@0.1.2
Patch Changes
@stackflow/plugin-devtools@0.1.13
Patch Changes
@stackflow/plugin-google-analytics-4@1.1.17
Patch Changes
@stackflow/plugin-lifecycle@0.1.2
Patch Changes
@stackflow/plugin-renderer-basic@1.1.15
Patch Changes
@stackflow/plugin-renderer-web@1.1.15
Patch Changes
@stackflow/plugin-sentry@0.1.2
Patch Changes
@stackflow/plugin-stack-depth-change@1.1.7
Patch Changes
@stackflow/react-ui-core@1.3.6
Patch Changes
@stackflow/react@2.1.2
Patch Changes
@stackflow/demo@1.4.2
Patch Changes
@stackflow/docs@2.1.2
Patch Changes