# Changelog

All notable changes to this project are documented in this file.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [Unreleased]

## [1.1.12] - 2026-07-02

### Fixed

- **`npm ci` lockfile drift fixed.** The per-platform `optionalDependencies` subentries in `package-lock.json` (`node_modules/@fateforge/jira-cli-*`) were missing their `version`, so once those platform packages were published, `npm ci` failed its consistency check (`lock file's <pkg>@ does not satisfy <pkg>@<version>`). The version bump (`scripts/version-files.js`) now syncs the lockfile platform subentries too, and `check-version.js` guards them, so the drift can't silently recur.

## [1.1.11] - 2026-06-29

### Fixed

- `update` Sigstore signature verification now bounds the TUF trust-root refresh with a timeout and binds it to the command context. A hung or slow Sigstore TUF registry can no longer stall the `verify_signature` stage indefinitely, and a SIGINT during the refresh is honored instead of being swallowed until the fetch returns (CLI-SPEC §14).
- `update` now classifies a TUF trust-root **refresh** failure (network/timeout) as a retryable network condition instead of the non-retryable `E_INTEGRITY` reserved for a genuine signature/identity/checksum mismatch. Fetching trust metadata is a network step, not a forged-release verdict.
- `update` notice cache reads are now version-aware: a cached `update_available` notice is suppressed once the running binary is already at or past the cached latest version. Business commands no longer keep advertising an update to a version that is already installed for up to the 24h cache TTL (for example, right after a successful update).

## [1.1.10] - 2026-06-25

### Added

- Contract single-source: `internal/contract/contract_gen.go` is now generated from `contract/contract.json` (vendored from ai-native-cli-spec@v1.4) via `scripts/gen-contract.js`. `internal/output` imports the generated package so `SchemaVersion`, `ExitCodeForErrorCode`, and `RetryableForErrorCode` cannot drift from the fleet contract.
- Conformance test `internal/output/contract_conformance_test.go` asserts every emitted error code is in the canonical contract with the exact exit + retryable, and that success/error envelopes carry only the canonical top-level and meta keys.
- CI guard `scripts/check-spec.js` added to the `npm-audit` job (after `check-version.js`) to fail the build if the vendored contract drifts from ai-native-cli-spec.

### Changed

- `.agent` is now synced from ai-native-cli-spec@v1.4 (SPEC_VERSION pinned).
- `update` on a package-manager-managed install (npm or Go) now **drives** the package manager — it runs `npm install -g @fateforge/jira-cli@<ver>` (or `go install`) on the user's behalf, then syncs the Skill, and reports `status: "updated"`. Previously it printed the command and exited with code 2. `--dry-run` remains read-only (previews the command, runs nothing). A PM failure returns `E_IO`, `binary_replaced: false`, with the command for manual recovery.
- `exitForUpdateCode` now delegates to `output.ExitCodeForErrorCode` (sourced from the contract) instead of a hand-coded switch, eliminating a class of exit-code drift.

## [1.1.9] - 2026-06-25

### Fixed

- `update` now uses `--target-version` as the canonical flag to select a specific release; `--version` is kept as a hidden, deprecated alias so the target-release selector is no longer confused with the root command's `--version` (which prints the tool version).
- A failure to download the Sigstore signature bundle during `verify_signature` (5xx, connection reset, DNS, rate-limit) is now classified on the retryable network taxonomy (`E_SERVER`/`E_NETWORK`/`E_RATE_LIMITED`/`E_TIMEOUT`) with a SIGINT/SIGTERM check (`E_INTERRUPTED`, exit 130), instead of being collapsed into non-retryable `E_INTEGRITY`. Only a fetched-but-invalid signature (or a deliberately missing bundle) remains `E_INTEGRITY`. Discover/download HTTP failures are likewise mapped by status through the single `ErrorCodeFromStatus` taxonomy, so a 404 on a requested `--target-version` tag surfaces as `E_NOT_FOUND` (exit 3) rather than a generic network error.
- `update --dry-run` is now evaluated before the package-manager (npm) gate, so the read-only preview is always reachable on a package-managed install instead of being short-circuited into the "use your package manager" error.

## [1.1.8] - 2026-06-22

### Added

- The cached update-available notice is now attached to every command's `meta.notices` (read-only from the local cache, no network call), so an agent sees an available update from any command output. The field is omitted when the cache has nothing to report; the fresh/active view stays under `context`/`doctor`/`update --check` `data.notices`.
- Update notices are now severity-graded: `warning` when the embedded CHANGELOG delta since the running version contains a `security` entry or the latest crosses a major version, otherwise `info` (`critical` is reserved). The severity is computed at check time and stored in the cache, so the cached `meta.notices` carries the right level.

## [1.1.7] - 2026-06-21

### Changed

- `update` is now a single self-update command with no confirm-token gate: a bare `jira-cli update` resolves the latest (or `--version`) release, verifies its integrity, replaces the binary, and syncs the Skill in one call. The previous `--dry-run` → `--confirm <token>` write gate has been removed from `update` only (data-write commands are unchanged). `--check` and `--dry-run` remain optional read-only flags, and `update --dry-run` no longer issues a `confirm_token` or `expires_at`. `update` is idempotent: already-latest returns a no-op success.

### Added

- Staged update failure/interruption envelope: every `update` failure now carries `stage` (`discover|download|verify_signature|verify_checksum|replace|skill_sync`), `current_version`, `binary_replaced`, and `skill_sync_status` in `error.details`, so an agent can always reason about the post-failure state.
- New error codes `E_IO` (exit 1, non-retryable) and `E_INTERRUPTED` (exit 130, retryable). SIGINT/SIGTERM during `update` is trapped: the temp dir is cleaned and a terminal `E_INTERRUPTED` envelope is still emitted on stdout, never a bare killed process.

### Fixed

- `update` replace-stage local failures (permission, disk full, file locked, partial write) are now classified as `E_FORBIDDEN`/`E_IO` instead of `E_NETWORK`, so an agent does not retry a problem that needs an environment fix.
- A post-swap Skill-sync failure is now reported as partial success (`ok:false`, `binary_replaced:true`, retryable, with `skill_sync_command`) instead of a hard `E_NETWORK`, so the agent knows it is already on the new binary and only needs to finish the Skill sync.

## [1.1.6] - 2026-06-16

### Fixed

- npm `optionalDependencies` platform-package pins now match the package version. The previous release bumped the top-level version but left the pins at the prior version, so `npm install` resolved a stale platform binary (the new wrapper with the old binary). The publish workflow now rewrites `optionalDependencies` from the package version before `npm publish`, so the pins can no longer drift from the single source of truth.

## [1.1.5] - 2026-06-16

### Changed

- `update` now verifies the release Sigstore signature on `checksums.txt` **in-process** (embedded `sigstore-go`, bootstrapped from the embedded TUF trust root) instead of shelling out to an external `cosign`. Verification is mandatory and fail-closed: a missing signature bundle, a signature that does not verify against this repo's tagged release-workflow identity, or a checksum mismatch all refuse the update — there is no skip path. Releases are now signed with `cosign sign-blob --new-bundle-format`.

### Security

- Release-integrity failures (missing/invalid signature or checksum mismatch) now return the non-retryable `E_INTEGRITY` error code (exit 1) instead of a retryable network code, so an agent treats a possible supply-chain issue as a hard stop rather than retrying.

## [1.1.4] - 2026-06-15

### Added

- Batch issue commands, each one agent-facing command with one confirm token and one aggregated `items[]`/`summary` result (per-item `{target, ok, error{code,retryable}}`, no whole-batch rollback): `issue bulk-create --file` (native `/issue/bulk`), `issue backlog-move` (native `/backlog/issue`, symmetric inverse of `sprint move`), `issue bulk-assign`, `issue bulk-edit` (client-side loop over per-issue field writes), and `issue rank` (native `/issue/rank`). All accept plural `--issues` (comma-separated or repeatable) and/or `--jql` selection, support `--continue-on-error` (default `true`), and auto-chunk to the Jira ≤50 cap so a large batch never 400s upstream. New `batch_result` / `batch_create_result` output schemas and runnable dry-run→confirm examples in `reference`.

### Changed

- npm scope migration `@fatecannotbealtered-` → `@fateforge` (the hyphenless org name was taken on npm, so the package and its platform binaries moved to the `@fateforge` scope). The npm package is now `@fateforge/jira-cli` and the optional platform packages are `@fateforge/jira-cli-<os>-<arch>`. The GitHub org, Go module path, and the `npx skills add` Skill source are unchanged.

### Fixed

- `sprint move` now auto-chunks issue keys at the agile ≤50 per-request cap instead of POSTing the whole list in one call (a >50 move previously 400'd silently upstream). The chunk size lives in one shared helper (`api.ChunkKeys` + `api.AgileMoveCap`) reused by `sprint move`, `issue backlog-move`, `issue bulk-create`, and `issue rank` so the cap cannot drift between commands sharing an endpoint.

## [1.1.3] - 2026-06-14

### Added

- `issue link list <key>` -- first-class issue-link listing; `sprint report <sprintId>` -- sprint velocity/completion (committed vs completed counts + story points).
- `reference` now exposes a real per-command `output_schema` + `examples[]`, guarded against regression.

### Changed

- Confirm tokens are now single-use: replaying a confirmed write's token returns `E_CONFLICT` (safe-retry).

## [1.1.2] - 2026-06-14

### Added

- `search` now exposes pagination honestly: single-page output includes `isLast` and (when not last) `nextStartAt`, a new `--start-at` flag pages forward, and `--all` output sets `truncated: true` (with `cap`) when the 10k ceiling is hit. `issue bulk-transition --jql` now refuses to run when the JQL matches more than the cap, instead of silently skipping issues.

### Changed

- **Behavior change (agents must adopt):** the `write-dangerous` tier is now actually enforced. `issue delete`, `issue bulk-transition`, `sprint close`, and `filter delete` require `--dangerous` in BOTH the `--dry-run` and `--confirm` steps; without it they return exit `5` / `E_CONFIRMATION_REQUIRED`. Previously the tier was advertised in `reference`/SKILL but not enforced in code (the self-description over-promised). The dangerous set is now the single source of truth shared by the runtime gate and `permission_tier`. Self-update is reclassified from `write-dangerous` to `write` (it is confirm-token gated and does not mutate Jira data).

### Fixed

- HTTP `409` now maps to `E_CONFLICT` (exit `6`) instead of collapsing into `E_VALIDATION`, so genuine Jira edit/transition conflicts are distinguishable.

## [1.1.1] - 2026-06-14

### Added

- Recorded live smoke against a real licensed Jira Data Center instance (`docs/LIVE-SMOKE-EVIDENCE.md`, 2026-06-14: auth, reads, error taxonomy, and the write confirm-chain including a real comment add/delete with cleanup); `release_readiness` is now `stable` with `live_smoke_status: verified`.
- FCC enumeration guard (`TestFCC_EveryLeafCommandHasTest`): enumerates every leaf command from live `reference` output and asserts each has a command-level test; skips while `fcc_status` is honestly declared non-verified, so the claim cannot be flipped without coverage.
- Command-level tests for `changelog` (`--json` and `--since`).
- Added runtime `changelog [--since]` output derived from `CHANGELOG.md`, plus an embedded changelog source for built binaries.
- Added repository standard files for the AI-native tool skeleton: `AGENTS.md`, `NOTICE.md`, `CODE_OF_CONDUCT.md`, `docs/COMPATIBILITY.md`, `docs/E2E.md`, and `docs/OPEN_SOURCE_CHECKLIST.md`.
- Added bundled Skill version negotiation via `metadata.requires.min_version` and a `doctor` version check.

### Changed

- Synced the `.agent/` spec copies from the ai-native-cli-spec template: stdout failure envelope (§4), HMAC confirm-token requirement (§7), signature_status/signature_verified fields (§14), Skill frontmatter `version` rule.
- Unified the golangci-lint v2 toolchain: Makefile installs from the `/v2` module path and CI uses `golangci-lint-action@v8` to match the v2 config format.
- `update` result fields are now snake_case (`current_version`, `latest_version`, `requested_version`, `update_available`, `check_only`, `dry_run`, `install_method`, `manager_command`, `checksum_verified`); after an install, `current_version` reports the newly installed version alongside `previous_version`.
- Expanded `jira-cli reference` with tool/version metadata, security tier, command type, permission tier, blast radius, output schema, exit codes, and error codes.
- JSON IDs for flattened boards and sprints are now strings, and Jira timestamps returned in flattened issue/comment/worklog/attachment output are normalized to ISO 8601 UTC where possible.
- JSON write confirmation tokens now bind command context, configured host, token fingerprint, and available resource state to reduce stale or cross-context confirmation risk.
- Self-update now syncs the whole Agent Skill directory through `npx skills add fatecannotbealtered/jira-cli -y -g` and reports `skill_sync_status`.
- README, README_zh, CONTRIBUTING, `.agent/` specs, and the bundled Skill now describe stdout JSON envelopes, `doctor` checks, dry-run/confirm writes, runtime changelog refresh, encrypted config, Skill sync, and `_untrusted` fields.
- The E2E PowerShell scripts unwrap JSON envelopes and exercise write commands through `--dry-run` then `--confirm` in JSON mode.

### Fixed

- `issue create` / `issue edit` sent the `--description` as Cloud ADF (a `{type:"doc",…}` object), but jira-cli targets Jira Data Center / Server REST API v2, which takes a **plain string** — a real DC instance rejected it with `description: must be a string`. Now passed through as a plain string, with a regression test. Found by live smoke (mock tests had asserted the ADF shape).
- `TestIssueCommands_NotConfigured` now isolates HOME so a developer's real `~/.jira-cli/config.json` cannot leak into the test and turn it into a network call.
- JSON failure envelopes now include `meta.duration_ms`.
- Agent error codes now use the CLI spec names `E_AUTH` and `E_CONFIRMATION_REQUIRED`.
- Audit log timestamps are written in UTC and audit entries include the configured Jira host while redacting sensitive arguments.

### Security

- API token now lives in the OS keyring (Windows Credential Manager / macOS Keychain / Linux Secret Service); `config.json` keeps zero secrets, only a `token_storage` marker. Machine-bound file encryption remains as the fallback when no keyring service exists, and `context.data.credentials.storage` reports the active backend. Logout clears the keyring entry.
- Synced `.agent/` SEC-SPEC from the template: credential-at-rest is now the keyring three-part pattern (password discarded after login / secrets in the OS keyring / zero-secret config), file encryption demoted to a visible fallback, env vars as the recommended secret channel, and an honest note on Windows `0600` semantics.
- Confirm tokens are now signed with a machine-local HMAC key (`confirm.secret`, created on first use with 0600 permissions) so they cannot be fabricated without running `--dry-run` on the same machine.
- Saved config tokens are written as AES-256-GCM encrypted `token_enc` values; legacy plaintext config remains readable for migration.
- Release checksums are signed with Sigstore/Cosign, and install/update paths report signature verification status separately from checksum verification.
- npm install checksum verification now fails closed, with `package-lock.json` committed and npm audit added to CI/release checks.
- Default JSON output tags Jira-controlled issue summaries/descriptions, comments, worklog comments, and attachment filenames with `_untrusted` where returned.


## [1.1.0] - 2026-06-06

### Added

- **Agent JSON envelope** — default JSON success and failure responses now share a stable envelope: `ok`, `schema_version`, `data`/`error`, and `meta.duration_ms`.
- **Confirm-token write flow** — JSON write commands now support the non-interactive `--dry-run` → `--confirm <token>` flow. Dry-run responses include a change preview, `confirm_token`, and `expires_at`; execution validates that the token still matches the operation.
- **Self-description commands** — added `context`, and expanded `reference` and `doctor` output for agent discovery and environment checks.
- **Structured error taxonomy** — error envelopes now include stable `E_*` codes and `retryable` hints for automated retry decisions.

### Changed

- **JSON is the agent contract** — stdout now contains exactly one JSON document for normal command responses; human-readable output requires `--format text`.
- **Error JSON moved to stdout** — machine-readable failures now use the same stdout channel and envelope shape as successes. Progress, prompts, warnings, and text-mode errors remain on stderr.
- **Exit code semantics** — exit codes now follow the agent contract: `2` bad args, `3` not found, `4` auth/permission, `5` confirmation required, `6` conflict, `7` retryable transient failure, `8` timeout.
- **Interactive login is text-only** — default JSON mode requires `jira-cli login --host <url> --token <pat>`; interactive login requires `--format text`.
- **`doctor` output** — JSON output now reports a `checks` list with `check`, `status`, `message`, and `fix` fields instead of the old `authValid` shape.

### Fixed

- **JSON write safety** — confirmed JSON writes no longer fall through to stdin prompts after token validation.
- **Stable confirmation hashing** — write-command confirm tokens include the full operation details and stable slice handling in tests.

## [1.0.6] - 2026-06-05

### Added

- **Built-in `update` command** — standalone binaries can check GitHub Releases, verify `checksums.txt`, and replace the current executable. Package-manager installs are detected and guided back to the package manager unless `--force` is used.
- **Global output format control** — `--format json|text|raw` now controls CLI output across commands. JSON is the default for agent-friendly parsing, `text` keeps human-readable tables and prompts, and `raw` is explicitly supported only by commands that can return raw output.

### Changed

- **Agent-friendly defaults** — commands now emit stable JSON by default, while `--json` remains a compatibility alias for `--format json`.
- **Reference output** — `jira-cli reference` now defaults to structured JSON; use `jira-cli --format text reference` for the Markdown command reference.
- **Output flag rules** — `--compact` and `--fields` are JSON-only, `--quiet` no longer suppresses JSON/raw result bodies, and unsupported `raw` output returns an argument error instead of silently downgrading.

### Fixed

- **Structured argument errors** — Cobra argument validation errors now return machine-readable JSON by default instead of plain text.
- **Clean JSON stdout** — interactive prompts and cancellation/error paths no longer pollute JSON success output.

## [1.0.5] - 2026-06-02

### Added

- **`issue attachments` download** — the command can now fetch attachment content, not just list metadata. `--out <dir>` downloads all attachments into a directory; add `--id <attachmentId>` to download a single one (exit code 4 if not found). With `--json` it prints `{id, filename, path, mimeType}` per saved file. Downloads stream to disk (handles large files like screen recordings) and validate the content URL points at the configured Jira host. The `attachments --json` listing now also includes the `content` download URL.

## [1.0.4] - 2026-05-31

### Fixed

- **`issue get` description** — `description` is now included in the default flat output and selectable via `--fields description` (previously only reachable through `--raw`). Bulk outputs (`issue list`, `search`, `filter run`, `sprint issues`) stay lean and omit `description` by default to preserve token efficiency. Handles both Data Center (plain string) and Cloud/v3 (ADF) descriptions.

## [1.0.3] - 2026-05-26

### Fixed

- **Semantic exit codes** — validation, auth, and config failures now return non-zero exit codes (via `SilentErr`); `doctor` and `login` work correctly in CI scripts.
- **Audit logging on failed writes** — write commands are logged even when the operation fails.
- **`FilterSprintFields`** — camelCase sprint fields (`startDate`, `endDate`) filter correctly with `--fields`.
- **Config file corruption detection** — invalid JSON in `~/.jira-cli/config.json` returns a clear parse error.
- **`issue edit --description`** — plain text is converted to ADF, matching `issue create`.
- **Agile API pagination** — sprint/board list, backlog, epics, and epic issues fetch all pages instead of truncating at ~50 items.
- **`ListWorklogs` pagination** — worklogs beyond the first page are included.
- **`search --order-by`** — skips appending `ORDER BY` when JQL already contains one.
- **`issue delete --dry-run`** — no longer prompts for confirmation before previewing.
- **`issue bulk-transition`** — `skipped` and `failed` counts are reported separately in JSON output.
- **E2E script** — sprint move (K7) runs before issue cleanup; `JIRA_E2E_CLEANUP=0` is honored.

### Added

- **`cmd.Run()` / `Main()`** — testable CLI entry point with correct exit code propagation.
- **Comprehensive unit tests** — 100% statement coverage across all packages; httptest-based command integration tests.
- **`internal/api/agile_page.go`** — shared pagination helper for Jira Agile API endpoints.

### Changed

- **Minimum Go version** — `go.mod` updated to Go 1.24 (uses `testing.T.Chdir` in tests).

### Documentation

- Clarify `search --fields` (Jira fetch) vs `issue get/list --fields` (output trimming).
- Document `issue delete --dry-run` skips confirmation; remove misleading `sprint close --force` wording.
- Add `epic list` / `epic issues` to README; document `filter run --raw/--fields`.
- Document stdout (success JSON) vs stderr (error JSON); `doctor` exit code and `authValid` checks.
- Note npm install requires `curl`; add `issue list` vs `search` JSON/jq examples.

## [1.0.2] - 2026-05-14

### Fixed

- **Retry loop now respects context cancellation** — long-running API calls with rate limiting or server errors can now be interrupted by the caller.
- **Upload retry loop now respects context cancellation** — file uploads honor context cancellation during retries.
- **Token sanitization improved** — audit logging now handles `--token=value` format for all case variations (e.g., `--TOKEN=`, `--Token=`).
- **Config file corruption detection** — invalid JSON in `~/.jira-cli/config.json` now returns an error instead of silently continuing with empty values.
- **Timing attack prevention** — confirmation prompts use constant-time comparison to prevent timing-based information leakage.

### Security

- **Audit logging uses constant-time comparison** to prevent timing attacks on confirmation inputs.
- **Sensitive flags aligned with JDC-only PAT authentication** — audit sanitization targets only `--token` and `-t` since this CLI uses PAT only, no password support.

## [1.0.1] - 2026-05-06

### Fixed

- **Audit log `sanitizeArgs` now handles `--token=value` format** — previously `--token=secret` would be logged in plaintext.
- **`SearchAll` capped at 10,000 issues** to prevent unbounded memory usage on large result sets.
- **`sprint active` supports multiple active sprints** — previously only the first was returned.
- **`issue clone` extracts project key from source issue** instead of scanning the issue key string for `-`.
- **Removed empty `internal/api/compat.go`** file.

### Added

- **`filter run` supports `--raw` and `--fields`** flags, consistent with `search` and `issue list`.
- **`board backlog` and `board epics` support `--limit`** flag (default 50, max 200).
- **`issue watch`/`unwatch`/`vote`/`unvote` produce JSON output** with `--json` flag.
- **`parseTimeSpent` supports `d` (days) and `w` (weeks)`** units — `1d` = 8h, `1w` = 5d (Jira defaults).
- **`make test` now runs `gofmt` and `go vet`** before unit tests.
- **Release workflow extracts version-specific notes** from CHANGELOG.md for GitHub Release body.

## [1.0.0] - 2026-05-03

Initial release of jira-cli for Jira Data Center.

### Features

- **Jira Data Center only**: Bearer PAT authentication, DC `name`-based user references, `/rest/api/2/` exclusively.
- **Complete coverage**: issues, sprints, boards, epics, projects, users, filters — CRUD + advanced operations.
- **AI Agent friendly**:
  - `--json` outputs token-efficient flat format by default; `--raw` returns full Jira API response.
  - `--fields key,summary,status` to output only specified fields.
  - `--quiet` suppresses all non-JSON stdout (clean pipe output).
  - `--dry-run` on all write commands — previews without executing.
  - `--force` skips interactive confirmation prompts.
  - Machine-readable error codes (`errorCode`) and actionable hints (`hint`) in JSON error responses.
  - Semantic exit codes: 0=OK, 2=bad args, 3=auth, 4=not found, 5=forbidden, 6=rate limited, 7=network.
  - `reference` command: structured markdown listing of all commands and flags for AI self-discovery.
- **Smart retry**: automatic exponential backoff on 429 rate limits and 5xx errors.
- **Beautiful output**: colored tables with CJK character width support.
- **Custom fields**: set custom fields during create and edit via `--field "Name=Value"`.
- **Environment variables**: `JIRA_HOST` and `JIRA_TOKEN` override config file for CI/Agent use.
- **npm distribution**: `npm install -g @fateforge/jira-cli` with bundled AI Agent Skill.
- **Cross-platform**: Linux, macOS, Windows (x64 + arm64) via GoReleaser.
- **E2E test scripts**: Comprehensive PowerShell E2E script (`scripts/e2e-full.ps1`) covering all 55+ commands against a real Jira DC instance, with CSV report output and read-only mode.
- **Audit logging**: Automatic JSONL audit trail for all write commands (`~/.jira-cli/audit/`), with monthly file rotation and configurable retention (default 3 months). Disable with `JIRA_NO_AUDIT=1`.

### Documentation

- Bilingual README (English + Chinese) with CI/Report Card/License/npm badges.
- SKILL.md with JSON output schemas, error codes, exit codes, and complete flag reference.
- GitHub PR template for contributors.

[Unreleased]: https://github.com/fatecannotbealtered/jira-cli/compare/v1.1.0...HEAD
[1.1.0]: https://github.com/fatecannotbealtered/jira-cli/compare/v1.0.6...v1.1.0
[1.0.6]: https://github.com/fatecannotbealtered/jira-cli/compare/v1.0.5...v1.0.6
[1.0.5]: https://github.com/fatecannotbealtered/jira-cli/compare/v1.0.4...v1.0.5
[1.0.4]: https://github.com/fatecannotbealtered/jira-cli/compare/v1.0.3...v1.0.4
[1.0.3]: https://github.com/fatecannotbealtered/jira-cli/compare/v1.0.2...v1.0.3
[1.0.2]: https://github.com/fatecannotbealtered/jira-cli/compare/v1.0.1...v1.0.2
[1.0.1]: https://github.com/fatecannotbealtered/jira-cli/compare/v1.0.0...v1.0.1
[1.0.0]: https://github.com/fatecannotbealtered/jira-cli/releases/tag/v1.0.0