- name
SKILL.md
スキルファイルは公開元のリポジトリに置かれたままです。
コピーしたコマンドをターミナルに貼り付けてください。この SKILL.md がそのエージェントにインストールされます。
npx skills add mariadb-operator/mariadb-operator --skill mariadb-operator-release-notes -a cursor -yコピーしたコマンドをターミナルに貼り付けてください。この SKILL.md がそのエージェントにインストールされます。
npx skills add mariadb-operator/mariadb-operator --skill mariadb-operator-release-notes -a claude-code -yコピーしたコマンドをターミナルに貼り付けてください。この SKILL.md がそのエージェントにインストールされます。
npx skills add mariadb-operator/mariadb-operator --skill mariadb-operator-release-notes -a codex -yコピーしたコマンドをターミナルに貼り付けてください。この SKILL.md がそのエージェントにインストールされます。
npx skills add mariadb-operator/mariadb-operator --skill mariadb-operator-release-notes -a grok -yコピーしたメッセージを Grok Bot のチャットで送信してください。Bot がこの SKILL.md を GitHub から取得し、すべての Bot が共有するスキルに追加します。
Install this skill: https://github.com/mariadb-operator/mariadb-operator/tree/HEAD/.agents/skills/mariadb-operator-release-notes公開元より
Produce the two release documentation artifacts for a new version and deliver them as a PR against the release branch:
docs/releases/RELEASE_<version>_HEADER.md.gotmpl — the release notes headerdocs/releases/UPGRADE_<version>.md — the upgrade guide.github/workflows/release.yml runs goreleaser on the release tag. It looks for
docs/releases/RELEASE_${VERSION}_HEADER.md.gotmpl (falling back to the generic
RELEASE_HEADER.md.gotmpl) and prepends its rendered content to the auto-generated "What's Changed"
changelog. Consequences:
26.10.0 → RELEASE_26.10.0_HEADER.md.gotmpl.{{ .ProjectName }} for the project name, never hardcode it..github/workflows/release.yml before relying on it.All GitHub calls in the Step sections below use the project-scoped GitHub MCP tools
(mcp__github-mariadb-operator__*). If that server isn't connected, fall back in order: gh CLI with the
project token (GH_TOKEN="$GITHUB_MARIADB_OPERATOR_TOKEN" gh ..., not the ambient gh auth session), then the
generic mcp__github__* tools, then plain gh auth.
Preferred input: the release PR. The user provides the release PR (titled Release <version>, head branch
release-<version>, base main). Its body is the ordering and scope authority: it lists every PR in the
release, typically grouped by where it merged ("merged into main", "merged into this branch").
Fetch it with the GitHub MCP server:
mcp__github-mariadb-operator__pull_request_read(method="get", owner="mariadb-operator", repo="mariadb-operator", pullNumber=<release-pr>) → title, body, headRefName, baseRefNameParse the body into the list of PR links included in the release. By the time release notes are written, every listed PR is expected to be merged — re-check the release PR body for the current state rather than trusting a status that was recorded earlier in the conversation.
Fallback: no release PR provided. Ask the user for the new version to release (e.g. 26.10.0). Then infer
the change set from git history:
git fetch --tags origin main release-<version>
LAST_TAG=$(git describe --tags --abbrev=0 release-<version> 2>/dev/null || git describe --tags --abbrev=0 origin/main)
git log --oneline ${LAST_TAG}..origin/release-<version> # what changed
git log --merges --pretty='%h %s' ${LAST_TAG}..origin/release-<version> # merge commits → PRs
Map merge commits back to PR numbers (commit subjects and the pull/ refs in commit bodies), and confirm the
release-<version> branch exists on the remote before proceeding. If the history is ambiguous (squashed
merges, rebases), say so and list the commits you could not attribute to a PR.
For every PR in the release, fetch:
mcp__github-mariadb-operator__pull_request_read(method="get", owner="mariadb-operator", repo="mariadb-operator", pullNumber=<n>) → title, body, author, stateClassify each: feature (new capability, new spec field), bugfix, improvement (perf, tooling, CI), docs, or toolchain (dependency/tool bumps).
Record the author (user.login) and whether head.repo is a fork: a PR authored from a fork by someone
who is not a maintainer is a community contribution and gets credited in the notes (Step 2). Also read the body
for co-authors the PR itself credits — they get credited too.
Then determine the data-plane impact, which decides the upgrade guide content:
git diff --stat ${LAST_TAG}..origin/release-<version> -- \
cmd/init cmd/agent pkg/controller/replication/config.go pkg/galera/config \
pkg/environment pkg/builder/container_builder.go pkg/command
Any change here (agent/init behavior, rendered config, env vars, backup/restore CLIs, default images) means the
data-plane must be updated to the new version. Also check whether the release bumps
the default MariaDB image (RELATED_IMAGE_MARIADB_VERSION in the Makefile) — that belongs in the notes.
Map the PRs into logical groups sorted by relevance (biggest user-facing features first). Typical section lineup for this project — use only the ones that have content:
read_only)Every item is one bullet naming the concrete change, why it matters, and a PR link:
- Fixed X that could Y ([#1234](https://github.com/mariadb-operator/mariadb-operator/pull/1234)).
Stop at the change: one or two sentences, no forensics.
Group by what the reader experiences, not by which PR shipped it: one PR can contribute bullets to two sections (e.g. a Galera fix plus a generic backup-args fix), and a section must not collect items that don't belong to its topic.
Credit community contributions inline, following the convention of previous headers:
Kudos to @handle for driving this feature end to end!([#1234](...), thanks @handle!).user.login.Write docs/releases/RELEASE_<version>_HEADER.md.gotmpl, following the most recent version's header as the
template (read docs/releases/RELEASE_<previous>_HEADER.md.gotmpl first). Structure:
**`{{ .ProjectName }}` [<zero-padded short version>](https://github.com/mariadb-operator/mariadb-operator/releases/tag/<version>) is here!** 🦭
<enthusiastic open-source intro; highlight any milestones the user provides, e.g. star count, Docker pulls —
never invent numbers>
<community thank-you paragraph, pointing at the inline credits in the sections below>
If you're upgrading from previous versions, __do not miss the [UPGRADE GUIDE](https://github.com/mariadb-operator/mariadb-operator/blob/main/docs/releases/UPGRADE_<version>.md)__ for a smooth transition.
## <feature section>
...
## Bugfixes
...
## Improvements
...
---
## Community
<same adopters/stars paragraph as previous releases>
## Enterprise
<same Enterprise Operator paragraph as previous releases>
Formatting rules (these are the review corrections — apply them up front):
26.10 for 26.10.0), the
releases/tag/ link is not. Keep the two forms consistent with the previous release's header.https://github.com/mariadb-operator/mariadb-operator/blob/main/docs/<doc>.md).
The header is rendered on the GitHub releases page, where relative links such as ./replication.md resolve
against the release URL and 404. Anchors (#section) must exist in the target doc — grep its headings.api/v1alpha1/ on the release branch
before writing them — wrong field names in release notes ship to every reader.Write docs/releases/UPGRADE_<version>.md, copying the previous guide's structure:
# <zero-padded short version> update guide
This guide illustrates, step by step, how to update to `<version>` from previous versions. This guide only
applies if you are updating from a version prior to `<zero-padded>x`, otherwise you may upgrade directly
(see [Helm](../helm.md#updates))
> [!TIP] (OCI-based installation — same block as previous guides)
> [!CAUTION] (mariadb-operator-crds in-place upgrade — same block as previous guides)
- The [data-plane](../data_plane.md) must be updated ... `updateStrategy.autoUpdateDataPlane=true` diff block
- Upgrade `mariadb-operator-crds` then `mariadb-operator` helm chart to `<version>` (bash blocks)
- Consider reverting `updateStrategy.autoUpdateDataPlane` back to `false` (diff block)
> [!NOTE] per release-specific behavior change users must know about but need not act on —
a changed default (e.g. the default mariadb image), or reconciled server state that differs after the
update. Use > [!CAUTION] only for actual migration hazards (breaking change, deprecated mechanism).--version 26.10.0).# filenames match the tag exactly (release.yml lookup)
ls docs/releases/RELEASE_<version>_HEADER.md.gotmpl docs/releases/UPGRADE_<version>.md
# template variables and links are sane
grep -n "{{ .ProjectName }}" docs/releases/RELEASE_<version>_HEADER.md.gotmpl
grep -n "UPGRADE_<version>.md" docs/releases/RELEASE_<version>_HEADER.md.gotmpl
# no relative doc links leaked into the header (must be empty)
grep -n '](\.\?\./' docs/releases/RELEASE_<version>_HEADER.md.gotmpl
# every PR of the release is cited exactly where expected
grep -o 'pull/[0-9]*' docs/releases/RELEASE_<version>_HEADER.md.gotmpl | sort -u
Compare that last list against the release PR's list: every PR must appear, and nothing else may. Then re-read
both files end to end: every version string in the right form for its context, every @handle matching the PR
author, every field name matching api/v1alpha1/, and the upgrade guide applicable to users of the previous
release.
Branch feature-release-notes-<version> from release-<version>.
Commit both files: "Add release notes and upgrade guide for ".
Push the branch (git push origin feature-release-notes-<version>), then open the PR targeting
release-<version> with the GitHub MCP server:
mcp__github-mariadb-operator__create_pull_request(owner="mariadb-operator", repo="mariadb-operator", title="Add release notes and upgrade guide for <version>", head="feature-release-notes-<version>", base="release-<version>", body=...)Wait for human review before merging — never self-merge release docs.
release-26.6.1). The "update to <version> from a version prior to
<major.minor>.x" line must match the actual minor series of the release being documented.>
---name: mariadb-operator-release-notesdescription: >---# .agents/skills/mariadb-operator-release-notes/SKILL.mdよくある質問
公開元から .agents/skills/mariadb-operator-release-notes/SKILL.md をダウンロードするか、パスをコピーしてリポジトリを開いてください。PlugMCP はスキルを掲載するだけで、ファイルはホストしていません。
公開元は https://github.com/mariadb-operator/mariadb-operator で管理しています。
Claude、Cursor、Codex、Grok Build は、公開元のリポジトリから追加した SKILL.md を読み込めます。Grok Bot は、チャットでスキルの GitHub フォルダーのリンクを送るとインストールします。