Repository navigation
chore(release): bump versions and update changelogs - #355
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
October 5, 2026 16:49
a030840 to
9070dfb
Compare
designcode
force-pushed
the
changeset-release/main
branch
from
October 6, 2026 10:23
9070dfb to
486d452
Compare
designcode
approved these changes
Oct 6, 2026
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
October 6, 2026 10:31
486d452 to
df778ee
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
October 6, 2026 14:42
df778ee to
3ba3c7d
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.15.0
Minor Changes
#344
2cffc3bThanks @designcode! -tigris access-keys deletetakes a comma-separated list of IDs, likebuckets delete: one confirmation for the batch that names every key, each key deleted in turn, failures reported per key without stopping the rest, and a non-zero exit if any failed.#344
2cffc3bThanks @designcode! -tigris orgs delete [id]deletes an organization you own, after a confirmation (--yesskips it). With no ID it lets you pick one from a list; organization names are not unique, so they are not accepted. The organization must be empty first; the gateway's reason is shown otherwise (IAM gateway errors now surface their message instead of the HTTP status text, for every IAM command). Your last organization cannot be deleted, and Fly.io organizations are not offered. If the deleted organization was the active one, the first remaining organization becomes active and is named, so the next command just works; JSON output always reportsactiveOrganization.#356
ef397c4Thanks @designcode! -tigris usageshows the active organization's usage and charges for the current month, or any month with--month YYYY-MM. Line items with zero usage are hidden unless--allis given;--format jsonreturns the full invoice. Requires OAuth login.Patch Changes
2cffc3bThanks @designcode! - Requests the CLI makes through the Tigris HTTP client (bucket listing and stats, copy/move, bucket settings) are retried on transient failures — 3 attempts with backoff and full jitter on 408/429/5xx and network errors — instead of failing on the first blip. Requests that go through the AWS SDK's S3 client keep its own retry policy, as before.2cffc3b,ef397c4]:@tigrisdata/iam@2.7.0
Minor Changes
#344
2cffc3bThanks @designcode! -deleteOrganization(organizationId)deletes an organization you own, throughDELETE /tigris-iam/namespacesscoped to that organization. The gateway accepts it only from an OAuth session, only for Tigris-native organizations, only from the owner, and only once the organization is empty (no buckets, access keys, policies, teams, or other members); its shares and invitations are removed with it. Gateway errors are returned as is, and so are transport failures — as{ error }, never a throw;removeAccessKeynow does the same.Errors from the IAM gateway now carry its reason (
{ status: "error", message }) instead of the HTTP status text, so a refused request says why rather thanBad Request.#356
ef397c4Thanks @designcode! -getUsage({ month })fetches the organization's usage and charges for a billing month from the management API — the data behind the console's Usage page: every charge with its quantity, billed quantity, tiers and amount, plus subtotal, credits, total, plan and invoice state. Defaults to the current month; needs a session token.tigris@3.15.0
Patch Changes
2cffc3b,2cffc3b,2cffc3b,ef397c4]:Note
Low Risk
No application code in the diff—only version bumps, changelogs, and removal of consumed changeset files.
Overview
Release PR that finalizes the Changesets bump: removes consumed
.changeset/*.mdfiles, raises@tigrisdata/clito 3.15.0,@tigrisdata/iamto 2.7.0, and thetigrisalias to 3.15.0, with matching CHANGELOG entries.What ships in this release (already merged via #344 / #356): batch
tigris access-keys delete,tigris orgs deletewith IAM gateway error messages surfaced in the CLI,tigris usagefor billing months, IAMdeleteOrganization/getUsage,removeAccessKeyreturning{ error }instead of throwing, and CLI HTTP client retries (3× backoff/jitter on transient failures for Tigris HTTP paths).Reviewed by Cursor Bugbot for commit 3ba3c7d. Bugbot is set up for automated code reviews on this repo. Configure here.