🦋 New version release - #429
Merged
Merged
Conversation
brentrager
force-pushed
the
changeset-release/main
branch
from
August 13, 2026 02:54
6a423d9 to
ecbaa14
Compare
brentrager
enabled auto-merge (squash)
August 13, 2026 02:54
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.34.2
Patch Changes
get_*/read_*/list_*= read-only-safe → auto-allowed), and the bare namecurrent_datetimefell into theUnknownbucket, soAcceptEditsasked the user before every clock read. Renamed the toolcurrent_datetime→get_current_datetimeso it is auto-allowed, with a regression test asserting the engine actually allows it. (The broader class fix — engine metadata-based tool classification and a wired "always allow" grant — is tracked in th-4c71a6 / th-cc0894.)