Skip to content

Jira CLI Toolkit 2.5.1rc1

Pre-release
Pre-release

Choose a tag to compare

View all tags
@github-actions github-actions released this 08 Oct 15:42
· 22 commits to main since this release
v2.5.1rc1
9c4a393

Jira CLI Toolkit 2.5.1rc1

Commit: 9c4a393

What's new in 2.5.1

  • On PyPI: pipx install jira-cli-toolkit, then pipx upgrade jira-cli-toolkit. The package was previously named jsup; a pipx or uv installation made before 2.5.1 switches once with pipx uninstall jsup and pipx install jira-cli-toolkit (configuration and saved credentials are kept). jira update gives package-manager users the exact command.
  • Verifiable builds: release files carry GitHub attestations. Check a download with gh attestation verify FILE --repo User17745/jira-cli-toolkit.

What's new in 2.5

  • jira api calls any Jira Cloud REST path with your saved profile, so the token never appears in the command. Methods, repeated --query, headers, JSON bodies from inline text, files or stdin, raw bodies, multipart uploads, --include and --output. Requests stay on your site, redirects aren't followed, and writes are never retried.
  • --spec discovery looks an endpoint up in Atlassian's official OpenAPI documents (Jira platform, Software and Service Management) without contacting your site: permissions, scopes, parameters and body schemas. jira api spec refresh and jira api spec status manage the cache.
  • Redaction of error output now also covers the derived Basic auth value, for every command.
  • Updater: loads everything it needs to report a result before replacing the executable.

API, discovery and agent setup guide.

Upgrading a 2.1.0 standalone binary

Run jira update --yes --json. Without --json, 2.1.0 replaces itself successfully but then crashes while printing the result (zlib.error ... incorrect header check). If you saw that, the update already worked: jira --version reports the new version and the old executable is kept as jira.previous. Updates from 2.5 onward are not affected.

Migration and roadmap.

Use the manifest for platform requirements and SHA-256 checksums. Use the short jira command. Python users also retain jsup and jira-cli-toolkit compatibility commands. API tokens and local profiles are preserved during executable updates. The repository and release assets are public; downloads do not require GitHub or Jira credentials.

Prereleases are for validation and do not become latest stable. macOS binaries are not notarized; Windows binaries are not code-signed.

Assets 10
Loading