SMOODEV-3412: Add the changeset #577 needed to release - #578
Merged
Merged
Conversation
#577 merged without one, so `changeset version` had nothing to bump — no version, no `version:sync` onto the crates, no crates.io publish, and therefore nothing for smooai to consume. The flag was on main and unreachable. `minor`: a new public builder on `AppState`, additive and off by default. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
🦋 Changeset detectedLatest commit: b4802de The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
brentrager
added a commit
that referenced
this pull request
Oct 1, 2026
…oot (#579) My changeset named `@smooai/smooth-operator-js`, which is the PRIVATE root package.json — not a package changesets manages. `changeset version` then threw "Found changeset require-owned-conversations for package @smooai/smooth-operator-js which is not in the workspace" and the release failed, which means my fix has been breaking the release on every push to main since #578 landed, not just failing to publish itself. The published one is `@smooai/smooth-operator` (typescript/package.json, the only non-private member); `version:sync` stamps its version onto the crates, which is the number smooai needs. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Problem
#577 merged without a changeset, so the release workflow has nothing to bump. No version, no
version:syncstamping the crates, no crates.io publish — and therefore nothing forsmooaito consume.with_require_owned_conversationsis onmainand unreachable from the consumer that needs it.Confirmed:
.changeset/onmainholds onlyREADME.mdandconfig.json.Solution
Adds the changeset.
minor— a new public builder onAppState, additive and off by default.Sequencing (unchanged, and it matters)
The flag fails closed by design: it is checked before the scope match, so a
UserScope::Deniedprincipal — one whose token carries noemailclaim — reaches nothing at all.smooai#5206— theemailclaim on the minted operator token. Already merged.smooai-smooth-operator-serverinsmooai.copilot-ws.Enabling the flag before step 1 had deployed would have refused every conversation read rather than leaking through — the right direction, but it would have broken the drawer.
🤖 Generated with Claude Code