Skip to content

chore: move main to ui 0.52.0 / core 0.25.12 (unpublished) so the package smoke passes - #1743

Merged
backnotprop merged 1 commit into
mainfrom
chore/ui-core-next-versions
Oct 7, 2026
Merged

backnotprop merged 1 commit into
mainfrom
chore/ui-core-next-versions

Conversation

@backnotprop

Copy link
Copy Markdown
Owner

ui 0.51.0 and core 0.25.11 were published to npm from 66c7a55. Main's ui has since started importing @plannotator/core/server-session (#1729), which the published core 0.25.11 does not export, so packages/ui smoke:package now fails on every PR (seen on #1741).

This bumps core to 0.25.12 and ui to 0.52.0 (ui pins core 0.25.12 exactly). Neither is published; the smoke then reads the source manifest instead of the registry. These become the next cut (0.52.0 adds the QuestionBlock decision toggle for Workspaces plus the unreleased HANDOFF entries).

Verified: bun run --cwd packages/ui smoke:package passes ("Verified @plannotator/ui@0.52.0 packs ... installs externally with @plannotator/core@0.25.12").

….12 (unpublished)

ui 0.51.0 / core 0.25.11 were published from 66c7a55. Main's ui already imports
@plannotator/core/server-session, which the published core 0.25.11 lacks, so the
ui package smoke failed on every PR. Bumping both (core pinned exactly) marks them
as the next, unpublished cut; the smoke then checks against the source manifest.
@backnotprop
backnotprop merged commit 128af7e into main Oct 7, 2026
25 checks passed
@backnotprop
backnotprop deleted the chore/ui-core-next-versions branch October 7, 2026 04:38
backnotprop added a commit that referenced this pull request Oct 21, 2026
…a cleared Custom name

The UI imports @plannotator/core/agent-switch, which the published core
0.25.13 lacks, so the package smoke failed. Core moves to 0.25.14 and the
UI pins it, as in #1743.

Choosing Custom with an empty name now removes the old custom-name cookie,
and config.json's bare "custom" is never paired with a leftover name, so
an old custom agent is not switched to again.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant