Version Packages

[daangnbot]

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/[email protected]

Patch Changes

• 0160f82: Fix intermittent incorrect transition state when transitionDuration is set to 0 by ensuring now >= eventDate in the initial aggregate call within dispatchEvent.

[cloudflare-workers-and-pages]

Deploying stackflow-demo with    Cloudflare Pages

Latest commit:	a1eaf7a
Status:	✅  Deploy successful!
Preview URL:	https://2e61d720.stackflow-demo.pages.dev
Branch Preview URL:	https://changeset-release-main.stackflow-demo.pages.dev

View logs

[coderabbitai]

📝 Walkthrough

Summary by CodeRabbit

• Bug Fixes

  • Fixed intermittent incorrect transition state in @stackflow/core when transitionDuration is set to 0.

• Documentation

  • Updated changelog for @stackflow/core version 1.3.2.

Walkthrough

This pull request releases version 1.3.2 of @stackflow/core, documenting a patch that fixes intermittent incorrect transition state when transitionDuration equals 0. The fix ensures the initial aggregate call in dispatchEvent uses now >= eventDate. Files include version updates, changelog entries, and release documentation.

Changes

Cohort / File(s)	Summary
Version Release 1.3.2 core/package.json, core/CHANGELOG.md, docs/components/ChangelogContent.mdx, .changeset/fix-transition-duration-zero-jitter.md	Version bump from 1.3.1 to 1.3.2, addition of changelog entry documenting the transition duration zero fix, removal of changeset entry, and updated release documentation.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Possibly related PRs

• Version Packages #684: Also modifies fixes within dispatchEvent; this PR ensures now >= eventDate for zero-duration transitions while the other prevents duplicate setInterval invocations in the same function.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Version Packages' accurately summarizes the main change, which is a version bump release for @stackflow/core from 1.3.1 to 1.3.2.
Description check	✅ Passed	The description is directly related to the changeset, explaining the automated release process and detailing the patch fix for the transition state issue in @stackflow/core.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch changeset-release/main

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[pkg-pr-new]

• @stackflow/demo

@stackflow/core

yarn add https://pkg.pr.new/@stackflow/[email protected]

@stackflow/compat-await-push

yarn add https://pkg.pr.new/@stackflow/[email protected]

@stackflow/link

yarn add https://pkg.pr.new/@stackflow/[email protected]

@stackflow/plugin-basic-ui

yarn add https://pkg.pr.new/@stackflow/[email protected]

@stackflow/plugin-blocker

yarn add https://pkg.pr.new/@stackflow/[email protected]

@stackflow/plugin-devtools

yarn add https://pkg.pr.new/@stackflow/[email protected]

@stackflow/plugin-google-analytics-4

yarn add https://pkg.pr.new/@stackflow/[email protected]

@stackflow/plugin-history-sync

yarn add https://pkg.pr.new/@stackflow/[email protected]

@stackflow/plugin-map-initial-activity

yarn add https://pkg.pr.new/@stackflow/[email protected]

@stackflow/plugin-preload

yarn add https://pkg.pr.new/@stackflow/[email protected]

@stackflow/plugin-renderer-basic

yarn add https://pkg.pr.new/@stackflow/[email protected]

@stackflow/plugin-renderer-web

yarn add https://pkg.pr.new/@stackflow/[email protected]

@stackflow/plugin-sentry

yarn add https://pkg.pr.new/@stackflow/[email protected]

@stackflow/plugin-stack-depth-change

yarn add https://pkg.pr.new/@stackflow/[email protected]

@stackflow/react-ui-core

yarn add https://pkg.pr.new/@stackflow/[email protected]

@stackflow/react

yarn add https://pkg.pr.new/@stackflow/[email protected]

commit: a1eaf7a

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@core/CHANGELOG.md`:
- Line 7: Update the changelog entry to remove ambiguity by explicitly stating
the fix targets the aggregate call inside dispatchEvent (not store
initialization); change the sentence to mention "ensuring now >= eventDate in
the aggregate call within dispatchEvent" and keep references to
transitionDuration, eventDate, and dispatchEvent so reviewers can locate the
relevant logic (see aggregate call inside dispatchEvent and the separate
aggregate call during store initialization).

🪄 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: d2f1a3c5-b55d-498e-9b8f-e31bfecf6034

📥 Commits

Reviewing files that changed from the base of the PR and between 0160f82 and a1eaf7a.

📒 Files selected for processing (4)

• .changeset/fix-transition-duration-zero-jitter.md
• core/CHANGELOG.md
• core/package.json
• docs/components/ChangelogContent.mdx

💤 Files with no reviewable changes (1)

• .changeset/fix-transition-duration-zero-jitter.md

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Verify where aggregate(now) guards are applied in makeCoreStore
fd -i makeCoreStore.ts --exec rg -n -C3 'aggregate\(|Math\.max\(|new Date\(\)\.getTime\(\)'

Repository: daangn/stackflow

Length of output: 790

---

Clarify wording in the release note to avoid confusion between store initialization and dispatchEvent.

The phrase "initial aggregate call within dispatchEvent" risks ambiguity. The store initialization (line 84) also calls aggregate without the guard, while dispatchEvent (lines 96-99) applies Math.max(newEvent.eventDate, new Date().getTime()) to ensure the condition. Reword to explicitly state the fix applies to the aggregate call inside dispatchEvent, not during store initialization. Example: "ensuring now >= eventDate in the aggregate call within dispatchEvent" (dropping "initial").

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@core/CHANGELOG.md` at line 7, Update the changelog entry to remove ambiguity
by explicitly stating the fix targets the aggregate call inside dispatchEvent
(not store initialization); change the sentence to mention "ensuring now >=
eventDate in the aggregate call within dispatchEvent" and keep references to
transitionDuration, eventDate, and dispatchEvent so reviewers can locate the
relevant logic (see aggregate call inside dispatchEvent and the separate
aggregate call during store initialization).

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	stackflow-docs	a1eaf7a	Commit Preview URL	Apr 03 2026, 03:09 AM