Skip to content

chore(release): v0.3.0#198

Merged
arnaudlh merged 2 commits into
mainfrom
release/0.3.0
Jun 19, 2026
Merged

chore(release): v0.3.0#198
arnaudlh merged 2 commits into
mainfrom
release/0.3.0

Conversation

@arnaudlh

Copy link
Copy Markdown
Member

Release 0.3.0

Bumps Git-Ape from 0.2.0 → 0.3.0 and synchronizes the changelog and generated docs.

Version bumps

  • plugin.json0.3.0
  • .github/plugin/marketplace.jsonmetadata.version and the git-ape plugin entry → 0.3.0 (the ape-context entry stays at 1.0.0)

These satisfy the release invariant enforced by git-ape-release.yml (plugin.json, marketplace metadata.version, and the git-ape entry must all equal the tag version).

Changelog

Adds a curated ## [0.3.0] section to CHANGELOG.md covering everything merged to main since v0.2.0: the 4-track workshop program + agentic updater, the azure-policy-advisor skill and eval suite, onboarding/deploy hardening, and dependency bumps.

Docs regeneration

node scripts/generate-docs.js output is committed. Beyond the version-reference pages (marketplace.md, plugin-json.md), this also syncs workflow docs that had drifted on main after PR #180 merged (workshop workflow pages, overview.md, and gh-aw lock-file version refs) — the advisory Git-Ape: Docs Check will be green.

Release flow

After this merges to main, tag v0.3.0 (or run the Git-Ape: Plugin Release workflow with version 0.3.0) to publish the GitHub release, VSIX, and marketplace update.

A follow-up PR will add git-cliff-based changelog automation so future CHANGELOG.md sections are generated from conventional commits instead of hand-curated.

arnaudlh added 2 commits June 19, 2026 11:22
- bump version references in plugin-json and marketplace pages
- sync workshop workflow pages and gh-aw lock docs merged via #180
@arnaudlh arnaudlh requested a review from sendtoshailesh June 19, 2026 03:27
@arnaudlh arnaudlh self-assigned this Jun 19, 2026

@sendtoshailesh sendtoshailesh left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Review: clean release — mergeable, no required changes ✅

Verified this end-to-end as a release PR (version consistency, changelog accuracy, no stray code, docs sync).

✅ Version bumps — correct & complete

  • plugin.json, marketplace metadata.version, and the git-ape plugin entry all = 0.3.0; ape-context correctly stays 1.0.0. Satisfies the git-ape-release.yml invariant (check-version-drift is green).

✅ Changelog — exactly complete & accurate

  • 27 non-merge commits since v0.2.0 → 27 changelog entries. Every referenced SHA resolves in history; nothing omitted, nothing fabricated. Sensible categorization (Features / Fixes / Refactor / Docs / Chores / Deps).

✅ No stray code

  • Diff touches only plugin.json, .github/plugin/marketplace.json, CHANGELOG.md, and generated website/docs/** — no source/logic in the release PR.

✅ Docs fully in sync

  • A fresh node scripts/generate-docs.js yields zero residual drift. Bonus: this PR also clears the workshop/lock-doc drift that #180 left on main, so the advisory Docs Check goes green.

✅ No version stragglers — the only remaining 0.2.0 hits are third-party transitive deps in website/package-lock.json, not the plugin version.

All CI green; mergeable (the BLOCKED state is just the pending required approval).

Optional / non-blocking: the Other Changes bucket (2 entries — 0784bb0 drift-detector onboarding, 4aa2a71 script-lint gate) holds real Feature/CI work that landed with non-conventional commit titles (no feat:/ci: prefix), so it fell through to "Other." Accurate as-is, and the planned git-cliff automation would categorize these properly going forward. Purely cosmetic.

Verdict: textbook release PR — version-consistent, changelog-complete, docs-clean, no stray code. Ready to approve, merge, and tag v0.3.0. 👍

@arnaudlh arnaudlh merged commit ab5bd54 into main Jun 19, 2026
7 checks passed
@arnaudlh arnaudlh deleted the release/0.3.0 branch June 19, 2026 06:48
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