chore(release): bump versions and update changelogs

[github-actions]

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.7.0

Minor Changes

• #230 931178a Thanks @designcode! - tigris init no longer offers to install a CLI you already have, and the CLI is
  now reachable unscoped as npx tigris.

  • The wizard installs the CLI only when tigris isn't on PATH; when it is, the
    "Defaults" hint drops the CLI - Global step and the existing install is
    brought up to date instead. Updating delegates to tigris update, which
    matches how the CLI was installed (npm / Homebrew / standalone binary). If
    that fails and leaves a CLI too old to serve the agent handoff (predating
    init --agent in 3.5.0), the handoff falls back to npx.
  • Run through a package runner (npx tigris init, pnpm dlx), init no longer
    counts the runner's own throwaway copy as an installed CLI — that copy is gone
    the moment the runner exits, so it installs a real one instead.
  • tigris init --agent now opens with a single CLI step chosen from what init
    detected — install when tigris is missing, update when it's present —
    instead of printing both behind if tigris isn't on $PATH conditions for the
    agent to evaluate.
  • New tigris package: an unscoped alias that hands straight over to
    @tigrisdata/cli, so npx tigris init works without the scope. Every
    command, flag and exit code behaves identically.

• #233 8c25b57 Thanks @designcode! - tigris buckets migrate keeps more data in flight by default, and the budget is
  now tunable per run.

  • The in-flight byte budget — the total size of migrations scheduled
    server-side but not yet confirmed — rises from 10 GB to 50 GB. A run made up
    of multi-gigabyte objects can now keep several of them in flight at once
    instead of serializing files that individually exceeded the old budget.
  • New --max-in-flight-gb overrides that budget, accepting 1 to 100 (default
    50). Out-of-range and non-numeric values are rejected up front — before
    discovery lists the bucket — rather than silently clamped, so the flag always
    means what it says. The separate 1,000-object in-flight cap is unchanged.

tigris@3.7.0

Minor Changes

• #230 931178a Thanks @designcode! - tigris init no longer offers to install a CLI you already have, and the CLI is
  now reachable unscoped as npx tigris.

  • The wizard installs the CLI only when tigris isn't on PATH; when it is, the
    "Defaults" hint drops the CLI - Global step and the existing install is
    brought up to date instead. Updating delegates to tigris update, which
    matches how the CLI was installed (npm / Homebrew / standalone binary). If
    that fails and leaves a CLI too old to serve the agent handoff (predating
    init --agent in 3.5.0), the handoff falls back to npx.
  • Run through a package runner (npx tigris init, pnpm dlx), init no longer
    counts the runner's own throwaway copy as an installed CLI — that copy is gone
    the moment the runner exits, so it installs a real one instead.
  • tigris init --agent now opens with a single CLI step chosen from what init
    detected — install when tigris is missing, update when it's present —
    instead of printing both behind if tigris isn't on $PATH conditions for the
    agent to evaluate.
  • New tigris package: an unscoped alias that hands straight over to
    @tigrisdata/cli, so npx tigris init works without the scope. Every
    command, flag and exit code behaves identically.

• #233 8c25b57 Thanks @designcode! - tigris buckets migrate keeps more data in flight by default, and the budget is
  now tunable per run.

  • The in-flight byte budget — the total size of migrations scheduled
    server-side but not yet confirmed — rises from 10 GB to 50 GB. A run made up
    of multi-gigabyte objects can now keep several of them in flight at once
    instead of serializing files that individually exceeded the old budget.
  • New --max-in-flight-gb overrides that budget, accepting 1 to 100 (default
    50). Out-of-range and non-numeric values are rejected up front — before
    discovery lists the bucket — rather than silently clamped, so the flag always
    means what it says. The separate 1,000-object in-flight cap is unchanged.

Patch Changes

• Updated dependencies [931178a, 8c25b57]:
  • @tigrisdata/cli@3.7.0

---

Note

Low Risk
Release housekeeping only (versions, changelogs, changeset cleanup); no runtime code changes in this PR.

Overview
This is a Changesets release PR: it bumps @tigrisdata/cli and the unscoped tigris alias from 3.6.1 → 3.7.0, rolls their pending changeset notes into CHANGELOG.md, and deletes the consumed .changeset/*.md files. There is no application source change in the diff—only version metadata and release notes.

The 3.7.0 entries document two already-merged minor features: smarter tigris init / npx tigris alias behavior ([#230]), and higher default plus --max-in-flight-gb tuning for tigris buckets migrate ([#233]).

^{Reviewed by Cursor Bugbot for commit a567861. Bugbot is set up for automated code reviews on this repo. Configure here.}