Skip to content

feat: Prepare v1.17.0 release notes for feature map commands #638

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
StatPan merged 1 commit into from
May 24, 2026
Merged

feat: Prepare v1.17.0 release notes for feature map commands #638

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,17 @@ Gira uses SemVer tags. User-facing features normally increment the minor version

## Unreleased

## v1.17.0 - 2026-05-24

- Added optional issue-backed feature map commands with the short `gira feat`
alias so operators and agents can list feature records, check feature map
health, and inspect whether a work issue is linked to a capability.
- Added the feature map convention docs for GitHub issue-backed capability
records, keeping GitHub Projects as visibility views and GitHub issues as the
canonical source of truth.
- Added stable JSON contracts for `feature-map-list/v1`,
`feature-map-check/v1`, and `feature-map-for/v1`.
Comment on lines +11 to +18
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot May 24, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The release notes for v1.17.0 appear to be incomplete. Based on the command registry in internal/gira/command_registry.go, several other features are also marked as introduced or stabilized in v1.17.0, including the goal command suite and the ticket handoff command. These should be included in the changelog to provide a comprehensive overview of the release.

Suggested change
- Added optional issue-backed feature map commands with the short `gira feat`
alias so operators and agents can list feature records, check feature map
health, and inspect whether a work issue is linked to a capability.
- Added the feature map convention docs for GitHub issue-backed capability
records, keeping GitHub Projects as visibility views and GitHub issues as the
canonical source of truth.
- Added stable JSON contracts for `feature-map-list/v1`,
`feature-map-check/v1`, and `feature-map-for/v1`.
- Added optional issue-backed feature map commands with the short `gira feat`\n alias so operators and agents can list feature records, check feature map\n health, and inspect whether a work issue is linked to a capability.\n- Added the feature map convention docs for GitHub issue-backed capability\n records, keeping GitHub Projects as visibility views and GitHub issues as the\n canonical source of truth.\n- Added stable JSON contracts for `feature-map-list/v1`,\n `feature-map-check/v1`, and `feature-map-for/v1`.\n- Added the goal-level operating model commands (`goal status`, `goal plan`,\n `goal next`, and `goal finish`) with stable JSON contracts for managing\n complex work graphs.\n- Added `gira ticket handoff` with the `worker-handoff/v1` JSON contract to\n compile worker-neutral handoff packets for stateless agents.


## v1.16.0 - 2026-05-19

- Added milestone lifecycle commands for creating, listing, assigning, planning,
Expand Down
6 changes: 3 additions & 3 deletions docs-site/command-reference.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ Usage:
gira feature check [--repo OWNER/REPO] [--limit N] [--json]
```

Since: `v1.18.0`
Since: `v1.17.0`

Flags:

Expand Down Expand Up @@ -40,7 +40,7 @@ Usage:
gira feature for ISSUE [--repo OWNER/REPO] [--limit N] [--json]
```

Since: `v1.18.0`
Since: `v1.17.0`

Flags:

Expand Down Expand Up @@ -69,7 +69,7 @@ Usage:
gira feature list [--repo OWNER/REPO] [--limit N] [--json]
```

Since: `v1.18.0`
Since: `v1.17.0`

Flags:

Expand Down
6 changes: 3 additions & 3 deletions internal/gira/command_registry.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -128,7 +128,7 @@ func CoreCommandSpecs() []CommandSpec {
Path: []string{"feature", "list"},
Summary: "List optional issue-backed feature or capability records.",
Usage: "gira feature list [--repo OWNER/REPO] [--limit N] [--json]",
Since: "v1.18.0",
Since: "v1.17.0",
Flags: []FlagSpec{
{Name: "--repo", Summary: "Target GitHub repo in OWNER/REPO format."},
{Name: "--limit", Summary: "Max issues to inspect. Default: 1000."},
Expand All @@ -144,7 +144,7 @@ func CoreCommandSpecs() []CommandSpec {
Path: []string{"feature", "check"},
Summary: "Validate optional feature map records and work links without mutating GitHub.",
Usage: "gira feature check [--repo OWNER/REPO] [--limit N] [--json]",
Since: "v1.18.0",
Since: "v1.17.0",
Flags: []FlagSpec{
{Name: "--repo", Summary: "Target GitHub repo in OWNER/REPO format."},
{Name: "--limit", Summary: "Max issues to inspect. Default: 1000."},
Expand All @@ -160,7 +160,7 @@ func CoreCommandSpecs() []CommandSpec {
Path: []string{"feature", "for"},
Summary: "Show which feature or capability a work issue is linked to.",
Usage: "gira feature for ISSUE [--repo OWNER/REPO] [--limit N] [--json]",
Since: "v1.18.0",
Since: "v1.17.0",
Flags: []FlagSpec{
{Name: "--repo", Summary: "Target GitHub repo in OWNER/REPO format."},
{Name: "--issue", Summary: "Work issue number. Can also be numeric positional."},
Expand Down