Jira CLI Toolkit 2.5.2

Jira CLI Toolkit 2.5.2

Commit: 58c5aa7

What's new in 2.5.2

• Homebrew: brew install user17745/tap/jira-cli-toolkit on macOS (Apple Silicon and Intel) and Linux x86_64, upgraded with brew upgrade jira-cli-toolkit. jira update recognizes a Homebrew installation and points to brew upgrade instead of replacing its files.
• PyPI page: the README's images and links now work on PyPI.

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.

Jira CLI Toolkit 2.5.1

Jira CLI Toolkit 2.5.1

Commit: cfd05fa

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.

Jira CLI Toolkit 2.5.1rc1

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.

Jira CLI Toolkit 2.5.0

Jira CLI Toolkit 2.5.0

Commit: 2a8861f

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.

Jira CLI Toolkit 2.5.0rc2

Jira CLI Toolkit 2.5.0rc2

Commit: 9e8a764

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.

Jira CLI Toolkit 2.5.0rc1

Jira CLI Toolkit 2.5.0rc1

Commit: 158b951

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.

Jira CLI Toolkit 2.1.0

Jira CLI Toolkit 2.1.0

Commit: 0675d21

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.

Jira CLI Toolkit 2.0.0

Jira CLI Toolkit 2.0.0

Commit: cdb0c0f

Migration and roadmap.

Use the manifest for platform requirements and SHA-256 checksums. Python users retain both jsup and jira-cli-toolkit commands. API tokens and local profiles are preserved during executable updates. The repository is private; downloads require repository read access.

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

Validation complete: all eight published assets match the manifest and checksums; latest stable resolves to v2.0.0. Actual RC-to-stable standalone and pipx upgrades passed, with configuration preserved and both CLI entry points working.

Completed v2 acceptance evidence. Planned v2.5 authenticated API flow; API commands are not part of v2.0.0.

Jira CLI Toolkit 2.0.0rc1

Jira CLI Toolkit 2.0.0rc1

Validated source commit: d064060.

This candidate adds project-neutral commands, guided API-token login and profiles, field/workflow discovery, issue maintenance, templates, shell completion, script output, and explicit updates. Both jsup and jira-cli-toolkit remain available throughout v2.x.

Validation passed: 128 regression tests; Linux/macOS/Windows compatibility jobs; four native builds; wheel/sdist installed smoke checks; original 0.2.0 pipx/uv/Python bootstrap; and live BUG issue operations. The tag pipeline published the complete eight-asset set. Downloaded assets match the manifest sizes/checksums. An earlier standalone CI binary updated to this published candidate, retained its previous executable and byte-identical config, and passed a no-op recheck. The candidate does not become latest stable.

Tag pipeline · Acceptance evidence · Migration guide

Use manifest.json for platform requirements and SHA-256 hashes. The repository is private; downloads require repository-read GitHub authentication. Jira tokens are not used for GitHub. Version 0.2.0 needs a one-time package-manager bootstrap before an update command is available. Select this candidate explicitly with update --version 2.0.0rc1 --prerelease.

Live auth/migration passed with explicit POSIX file storage. Successful interactive native-store access remains a manual gate before stable promotion; scripted macOS calls fail clearly when OS approval is needed, and Linux wallets are interactive only. API tokens cannot refresh automatically. macOS binaries are not notarized; Windows binaries are not code-signed. Optional GitHub attestations are disabled until private-repository eligibility is confirmed; updater hashes provide integrity checks, with publisher trust through authenticated GitHub HTTPS.