Skip to content

chore: prepare v0.9.2 release#868

Merged
danielmeppiel merged 3 commits intomainfrom
release/v0.9.2
Apr 23, 2026
Merged

chore: prepare v0.9.2 release#868
danielmeppiel merged 3 commits intomainfrom
release/v0.9.2

Conversation

@danielmeppiel
Copy link
Copy Markdown
Collaborator

v0.9.2 release

Bumps pyproject.toml 0.9.1 -> 0.9.2 and finalizes CHANGELOG.md with one-line summaries for every PR merged since 0.9.1.

Highlights

Added

Changed

Fixed

Verification

  • pyproject.toml version bumped to 0.9.2
  • CHANGELOG.md [Unreleased] cleared, new [0.9.2] - 2026-04-23 section populated
  • All 14 PRs merged between 0.9.1 prep (chore: prepare v0.9.1 release #838) and this PR are accounted for (or already documented under 0.9.1)

Post-merge

Tag + GitHub release per existing release workflow.

Bumps version to 0.9.2 and finalizes CHANGELOG with one-line summaries
for each PR merged since 0.9.1.

Highlights:
- ADO AAD bearer-token auth (#856)
- Governance Guide + enterprise docs IA refactor (#851, #858)
- Merge Gate orchestrator + single-authority aggregation (#865, #867)
- Landing + first-package docs rewrite (#855, #866)
- gh-aw imports migration (#864)
- Custom-port surfacing fix (#804)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot AI review requested due to automatic review settings April 23, 2026 09:11
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Prepares the v0.9.2 release by bumping the package version and rolling the accumulated Unreleased changelog entries into a dated 0.9.2 section, consistent with Keep a Changelog + SemVer.

Changes:

  • Bump apm-cli version from 0.9.1 to 0.9.2 in pyproject.toml.
  • Finalize CHANGELOG.md by clearing [Unreleased] and adding ## [0.9.2] - 2026-04-23 with categorized one-line PR summaries.
Show a summary per file
File Description
pyproject.toml Updates the project version to 0.9.2.
CHANGELOG.md Moves Unreleased entries into a new 0.9.2 release section with Added/Changed/Fixed grouping.

Copilot's findings

  • Files reviewed: 2/2 changed files
  • Comments generated: 0

danielmeppiel and others added 2 commits April 23, 2026 11:30
The dual-trigger pattern (pull_request + pull_request_target with
concurrency cancel-in-progress) shipped in #865 was over-engineered.
It produced TWO 'gate' check-runs per SHA -- one SUCCESS, one
CANCELLED -- and branch protection's status-check rollup treats
CANCELLED as failure, so PRs were silently BLOCKED unless an admin
overrode (which masked the bug on #867).

GitHub Actions has no primitive for 'either of these events
succeeded'. World-class OSS projects (kubernetes, rust, deno, next.js)
accept this and use a single trigger. The cost: a dropped 'pull_request'
webhook (rare; observed once on PR #856) requires manual recovery.

Recovery paths now documented at top of file:
  - push empty commit
  - gh workflow run merge-gate.yml -f pr_number=NNN
  - close + reopen PR

Replaces the dual-trigger + bootstrap-fetch dance with a clean
two-job flow: resolve-sha (handles workflow_dispatch input or PR head)
then gate (sparse checkout + run script). Same script, same exit
codes, same EXPECTED_CHECKS env.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The two-job split (resolve-sha + gate) created two visible check-runs.
Inlining the SHA resolution as a step within the gate job leaves only
one check-run -- 'Merge Gate / gate' -- on the PR.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@danielmeppiel danielmeppiel merged commit ba1f8e0 into main Apr 23, 2026
10 of 11 checks passed
@danielmeppiel danielmeppiel deleted the release/v0.9.2 branch April 23, 2026 09:56
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.

2 participants