chore(release): bump versions and update changelogs - #269
Closed
github-actions[bot] wants to merge 0 commit into
Closed
chore(release): bump versions and update changelogs#269github-actions[bot] wants to merge 0 commit into
github-actions[bot] wants to merge 0 commit into
Conversation
designcode
force-pushed
the
changeset-release/main
branch
from
August 24, 2026 07:08
9778c5c to
29aa3df
Compare
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm 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
@tigrisdata/cli@3.9.1
Patch Changes
#259
45e8661Thanks @designcode! - Fixtigris initfailing the whole skills step over one unsupported editor, andthe install banner appearing twice
Two things went wrong in a single
npx tigris@latest initrun:initpasses every selected editor to theupstream
skillsinstaller in one call, and that tool validates all of its-anames before doing any work — so one name it doesn't know fails the stepfor every editor. A user with Zed selected got
Invalid agents: zedand no skills at all, in any editor. Two changes: theinstaller is now pinned to
skills@latest, since npx otherwise reuses acached release that predates the newer agent names; and when the installer
does reject an editor,
initwarns about that editor and installs for therest instead of giving up.
straight to
/dev/tty, so it escaped the captured stdio of thenpm install -gthatinitandtigris updaterun and was painted over the wizard's ownprompts. Children the CLI spawns to install or update itself now set
TIGRIS_NO_BANNER, which postinstall honours — the banner still greets afirst-time install.
tigris@3.9.1
Patch Changes
45e8661]:Note
Low Risk
Release-only version and changelog updates; no runtime or security-sensitive code changes. Merging will publish to npm.
Overview
Automated Changesets release PR: bumps
@tigrisdata/cliand thetigrisalias to 3.9.1 and updates their changelogs.The patch notes the
tigris initskills-install fix (skip unsupported editors instead of failing the whole step, pinskills@latest) and suppressing the postinstall banner during self-install/update viaTIGRIS_NO_BANNER. No application logic is changed in this PR itself.Reviewed by Cursor Bugbot for commit 29aa3df. Bugbot is set up for automated code reviews on this repo. Configure here.