chore(release): bump versions and update changelogs - #255
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
August 17, 2026 09:15
1c404e8 to
9627cbf
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 17, 2026 12:42
9627cbf to
e101998
Compare
designcode
approved these changes
Aug 18, 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.9.0
Minor Changes
#256
91ee258Thanks @designcode! - Addtigris snapshots deleteto remove snapshots from a bucketSnapshots could be taken and listed, but never deleted from the CLI — the only
way to drop one was to call the SDK's
deleteBucketSnapshotdirectly. The newcommand closes that gap:
Find versions with
tigris snapshots list.--yes(or--force) skips theprompt. Like the other destructive commands, it refuses to run without
--yeswhen stdin is not a TTY.one bad version in a list does not hide the outcome of the others. Exits
non-zero if any deletion failed.
--format jsonemits{ action, bucket, versions, errors }, matching theshape
buckets deletealready returns.Deletion is permanent. Forks already created from a snapshot are unaffected.
Patch Changes
#246
7702103Thanks @designcode! - Fix object counts reported bycp,mv, andrmFolder markers (the zero-byte
folder/keys that make an empty prefix show upas a folder) were being counted as objects, so
mv -ron a folder of 10 filesasked "Are you sure you want to move 11 object(s)?" and then reported "Moved 10
object(s)".
lshides those markers, so the counts now do too — theconfirmation prompt and the final tally are derived from the same rule and
always agree.
mvandrmno longer count the folder's own marker, or the markers of anynested subfolders, as objects. The markers are still moved and deleted as
before; they're just not counted or printed.
handled, so an empty folder counts as
1rather than reading as a no-op, andclearing three sibling empty folders reports
3rather than1.cpremote-to-remote no longer counts nested folder markers, and a run whoseobject copies all failed now reports
0instead ofNo objects to copy.The
countfield in--format jsonoutput for these commands follows the samerule and may be lower than before for folders that contain markers.
Wildcards also no longer operate on the folder they match inside. A wildcard
names files within a folder, not the folder itself, so:
mv 'folder/*.zip'with nothing matching now reportsNo objects to moveinstead of
Moved 1 object(s). It previously moved the source folder'smarker to the destination, which removed
folder/itself.cp 'folder/*'no longer creates a folder marker at the destination.rm 'folder/*'empties the folder without deleting it, matching howrm dir/*behaves in a shell. Userm -r folderto remove the folder too.tigris@3.9.0
Patch Changes
7702103,91ee258]:Note
Low Risk
Release metadata only—no runtime code changes in this diff; risk is limited to incorrect version or changelog text at publish time.
Overview
Prepares the 3.9.0 npm release for
@tigrisdata/cliand the unscopedtigrisalias by bumping both packages from 3.8.0 to 3.9.0, folding the pending Changesets intoCHANGELOG.md, and deleting the consumed changeset files.The new changelog entries document what ships in this version (already merged elsewhere):
tigris snapshots delete(minor) with confirmation/--yes, batch comma-separated versions, per-version errors, and JSON output aligned withbuckets delete; and fixes tocp/mv/rmcounts and wildcard behavior (patch) so folder markers matchls, prompts agree with final tallies, and patterns likefolder/*no longer move or delete the folder marker itself.Reviewed by Cursor Bugbot for commit e101998. Bugbot is set up for automated code reviews on this repo. Configure here.