🦋 New version release#108
Merged
Merged
Conversation
brentrager
force-pushed
the
changeset-release/main
branch
from
c229a3c to
d0fb41f
Compare
brentrager
added a commit
that referenced
this pull request
Jun 25, 2026
…5d79) The local-flavor seams merged to smooth-operator main (#108), so point smooth-operator-server + smooth-operator-svc at ../smooth-operator (canonical main checkout) instead of the temporary smooth-local-flavor worktree, which is now removed. Same two-repo path pattern as the engine dep. Daemon builds + 97 tests pass + live smoke green against main (v1.7.0). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016wBikCFJyoowRokiWK5rX1
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish 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
@smooai/smooth@0.15.2
Patch Changes
check_releasekeyedshould_releaseoffgit log -1, but the changesets action leaves HEAD on its own🦋 New version releasecommit on thechangeset-release/mainside-branch — so the gate matched in the version-PR run too, firing build/release/update-homebrew-tap against a half-merged tree and 404'ing the tap job on a not-yet-published asset (a spurious red failure every release). Now keyed offgithub.event.head_commit.message(the commit actually pushed to main), with anorigin/main-tip fallback forworkflow_dispatch. README: brew install stays the headline method, with a verify step. (pearl th-891ccb)