Skip to content

chore(release): bump versions and update changelogs - #255

Merged
designcode merged 1 commit into
mainfrom
changeset-release/main
Aug 18, 2026
Merged

chore(release): bump versions and update changelogs#255
designcode merged 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

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 91ee258 Thanks @designcode! - Add tigris snapshots delete to remove snapshots from a bucket

    Snapshots could be taken and listed, but never deleted from the CLI — the only
    way to drop one was to call the SDK's deleteBucketSnapshot directly. The new
    command closes that gap:

    tigris snapshots delete my-bucket 1765889000501544464 --yes
    tigris snapshots delete my-bucket 1765889000501544464,1765889000501544465 --yes
    • Takes the bucket name and one or more snapshot versions, comma-separated.
      Find versions with tigris snapshots list.
    • Prompts for confirmation before deleting; --yes (or --force) skips the
      prompt. Like the other destructive commands, it refuses to run without
      --yes when stdin is not a TTY.
    • Deletes each version in turn and reports per-version success or failure, so
      one bad version in a list does not hide the outcome of the others. Exits
      non-zero if any deletion failed.
    • --format json emits { action, bucket, versions, errors }, matching the
      shape buckets delete already returns.

    Deletion is permanent. Forks already created from a snapshot are unaffected.

Patch Changes

  • #246 7702103 Thanks @designcode! - Fix object counts reported by cp, mv, and rm

    Folder markers (the zero-byte folder/ keys that make an empty prefix show up
    as a folder) were being counted as objects, so mv -r on a folder of 10 files
    asked "Are you sure you want to move 11 object(s)?" and then reported "Moved 10
    object(s)". ls hides those markers, so the counts now do too — the
    confirmation prompt and the final tally are derived from the same rule and
    always agree.

    • mv and rm no longer count the folder's own marker, or the markers of any
      nested subfolders, as objects. The markers are still moved and deleted as
      before; they're just not counted or printed.
    • An operation whose scope is nothing but markers reports the folders it
      handled, so an empty folder counts as 1 rather than reading as a no-op, and
      clearing three sibling empty folders reports 3 rather than 1.
    • cp remote-to-remote no longer counts nested folder markers, and a run whose
      object copies all failed now reports 0 instead of No objects to copy.

    The count field in --format json output for these commands follows the same
    rule 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 reports No objects to move
      instead of Moved 1 object(s). It previously moved the source folder's
      marker 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 how
      rm dir/* behaves in a shell. Use rm -r folder to remove the folder too.

tigris@3.9.0

Patch Changes


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/cli and the unscoped tigris alias by bumping both packages from 3.8.0 to 3.9.0, folding the pending Changesets into CHANGELOG.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 with buckets delete; and fixes to cp / mv / rm counts and wildcard behavior (patch) so folder markers match ls, prompts agree with final tallies, and patterns like folder/* 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.

@github-actions
github-actions Bot force-pushed the changeset-release/main branch 2 times, most recently from 1c404e8 to 9627cbf Compare August 17, 2026 09:15
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 9627cbf to e101998 Compare August 17, 2026 12:42
@designcode
designcode merged commit 80eb1c0 into main Aug 18, 2026
2 checks passed
@designcode
designcode deleted the changeset-release/main branch August 18, 2026 07:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant