Skip to content

release: feat/ai-sre → main (incident list --channel-id)#44

Merged
ysyneu merged 3 commits into
mainfrom
feat/ai-sre
Jun 15, 2026
Merged

release: feat/ai-sre → main (incident list --channel-id)#44
ysyneu merged 3 commits into
mainfrom
feat/ai-sre

Conversation

@ysyneu

@ysyneu ysyneu commented Jun 15, 2026

Copy link
Copy Markdown
Contributor

Promote the merged audit fix #43 to main for the v1.3.11 release.

  • incident list: rename --channel--channel-id for consistency with sibling channel commands (channel info/escalate-rule-list use --channel-id). Flag removed, not aliased.

feat/ai-sre is exactly main + #43 (CI green). Authorized by Boss for this main-trunk repo.

ysyneu added 3 commits June 15, 2026 11:47
`incident list` only accepted --channel, but every sibling channel command
(channel info --channel-id, channel escalate-rule-list --channel-id, ...)
uses --channel-id. An ai-sre agent that transferred the flag name across
commands ran `incident list --channel-id <id>` and got "unknown flag",
wasting a turn.

Make --channel-id the canonical flag (matching the siblings) and keep
--channel as a deprecated alias bound to the same variable so existing
callers keep working. Add tests asserting both flags forward to
/incident/list as channel_ids.
`incident list` used --channel while every sibling channel command uses
--channel-id (channel info --channel-id, channel escalate-rule-list
--channel-id, ...). Rename the flag to --channel-id for consistency.
--channel is removed (not aliased); only --channel-id exists.
…incident-list-channel-id

fix(incident): rename --channel to --channel-id on incident list
@ysyneu ysyneu merged commit e7d4dae into main Jun 15, 2026
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant