Release gitlab-simulation v0.3.0

Andrew Dunnrequested to merge
release/v0.3.0 into main

What

Cuts v0.3.0. The [Unreleased] section is dated as 0.3.0, an empty [Unreleased] stays above it, and the plugin version moves to 0.3.0, so the manifest, the notes and the tag agree after the merge.

Conventions applied

  • Dating [Unreleased], not regenerating it. The v0.2.0 release commit dated the existing section and kept an empty [Unreleased] above it (commit 0adbb92). The section already held the skill merge, the just lab / just contrib / just publish regroup (ADR-0005), the one gate set and the AI disclosure rule.
  • Entries for what the section lacked. Five commits since v0.2.0 carry a Changelog: trailer and had no entry: the herdr VM-up notification, the suggestion batch through upstream-post, the spine cut, running recipes from any directory, and the pinned vendor-sync tools. Each is one lead sentence plus two supporting sentences, under the category its trailer names (CHANGELOG.md header, CONTRIBUTING.md "Commit messages").
  • Categories in Keep a Changelog order. The section had two ### Fixed blocks; they are now one, after Deprecated (CHANGELOG.md header, which adopts Keep a Changelog).
  • Installer limits named once, in the "Recipes run from any directory" entry: type the recipe path unquoted, and a skill path with spaces does not match the permission pattern.
  • A stale sentence corrected. The "Old recipe names are gone" entry told installers to run the skill from its own directory; the any-directory fix made that untrue.
  • Version in every carrier. .claude-plugin/plugin.json is the only file carrying 0.2.0 (the one other hit is a vendored skill's own version, which CONTRIBUTING.md forbids editing). CONTRIBUTING.md "Tags": the plugin version tracks the tag.
  • Commit trailers. Signed-off-by: and AI-Assisted: yes per CONTRIBUTING.md; no tool-naming trailer, which just ci enforces.
  • Tag after merge. CONTRIBUTING.md "Tags": annotated, vMAJOR.MINOR.PATCH. The tag annotation is the changelog section under the heading gitlab-simulation v0.3.0, as v0.2.0's was. The tag pipeline's create-release job publishes it as the GitLab Release (.gitlab-ci.yml).
  • Merge commit. The project merges with a merge commit and squashing is off (CONTRIBUTING.md "Merge requests"); the tag goes on the merge commit.

Diagram

None. A release moves no path, adds no flow and changes no recipe, so there is nothing to draw.

Testing

just ci passes locally, including commit-trailers, the vale gate, sims-check and word-budget.

Merge request reports