Repository navigation
chore: move main to ui 0.52.0 / core 0.25.12 (unpublished) so the package smoke passes - #1743
Merged
Merged
Conversation
….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
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.
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
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.
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, sopackages/uismoke:packagenow 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:packagepasses ("Verified @plannotator/ui@0.52.0 packs ... installs externally with @plannotator/core@0.25.12").