Repository navigation
chore(release): bump versions and update changelogs - #359
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
October 8, 2026 07:53
24f9c75 to
582fe0a
Compare
designcode
approved these changes
Oct 8, 2026
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.16.0
Minor Changes
198eaadThanks @designcode! -tigris buckets purgepermanently destroys one or more soft-deleted buckets (comma-separated), after a confirmation that names them;--yesskips it. Each bucket is purged in turn, failures are reported per bucket without stopping the rest, and the exit code is non-zero if any failed. Purged buckets can no longer be restored.Patch Changes
198eaad]:@tigrisdata/storage@3.23.0
Minor Changes
198eaadThanks @designcode! -purgeBucket(name)permanently destroys a soft-deleted bucket before its retention period expires — the counterpart ofrestoreBucket. The bucket must already be soft-deleted (the gateway rejects a live one) and can no longer be restored afterwards; list the candidates withlistBuckets({ deleted: true }).@tigrisdata/agent-shell@0.7.2
Patch Changes
f5808a6Thanks @claude! - Update the README to the currentforksyntax:fork [<source-bucket>] --name <fork-name> [--snapshot <version>]creates a fork andfork [<source-bucket>] --listlists forks. The removedforkscommand andcreateForksListCommandexport are no longer documented.198eaad]:tigris@3.16.0
Patch Changes
198eaad]:Note
Low Risk
No runtime code in the diff—only version bumps and changelogs—though the published CLI/storage release adds irreversible bucket purge operations.
Overview
This is a Changesets release PR: it bumps package versions, rolls changelog entries forward, and removes the consumed
.changesetfiles so npm can publish on merge.@tigrisdata/storage@3.23.0 documents
purgeBucket(name)— permanent destruction of an already soft-deleted bucket (gateway rejects live buckets; uselistBuckets({ deleted: true })to find candidates).@tigrisdata/cli@3.16.0 ships
tigris buckets purgeon top of that SDK API: comma-separated names, confirmation (or--yes), per-bucket errors without aborting the batch, non-zero exit if any fail.@tigrisdata/agent-shell@0.7.2 is a patch bump for README
forksyntax docs and a dependency pin to@tigrisdata/storage@3.23.0. Thetigrisalias moves to 3.16.0 via@tigrisdata/cli.Reviewed by Cursor Bugbot for commit 582fe0a. Bugbot is set up for automated code reviews on this repo. Configure here.