Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

release-prep

Sterne0

Forks0

Aktualisiert15. Juli 2026 um 15:15

Prepare beta-line or stable release PRs for terraform-provider-ona by selecting the next provider version, updating version/STABLE_VERSION, version/BETA_VERSION, and CHANGELOG.md as appropriate, validating release metadata, and describing the publish step.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

gitpod-io

gitpod-io/terraform-provider-ona

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

name	release-prep
description	Prepare beta-line or stable release PRs for terraform-provider-ona by selecting the next provider version, updating version/STABLE_VERSION, version/BETA_VERSION, and CHANGELOG.md as appropriate, validating release metadata, and describing the publish step.

Release Prep

Use this skill when asked to prepare, review, or reason about an Ona Terraform provider release PR.

Release Model

version/STABLE_VERSION is the reviewed stable release intent and contains exact bare SemVer, for example 0.2.0.
version/BETA_VERSION is the reviewed beta release line and contains a bare beta line without the numeric suffix, for example 0.3.0-beta.
GitHub release tags add the leading v, for example v0.2.0 or v0.3.0-beta.7.
terraform-registry-manifest.json version is the Registry manifest schema version, not the provider version.
Pushes to main run CI and automatically publish the next beta tag from version/BETA_VERSION.
Stable publishing is a manual Build main workflow run from main with release_channel=stable after the stable release-prep PR merges.
Local publishing is not supported; the publish scripts are invoked by GitHub Actions on main.

Workflow

Inspect existing tags and releases. Use the highest SemVer tag as the lower bound; use the most recent published tag as the diff base for changelog review when those differ.
For a beta-line PR, update only version/BETA_VERSION to the intended beta line, for example 0.3.0-beta.
For a stable release-prep PR, update version/STABLE_VERSION to exact bare SemVer and update the first CHANGELOG.md heading to the same version.
Run both release metadata checks:
- scripts/validate-release-version.sh --channel stable
- scripts/validate-release-version.sh --channel beta
For a release-prep PR, keep the PR focused on release metadata unless the user asked for release automation changes too.
After a beta-line PR merges, the next push to main publishes the next computed v...-beta.N tag.
After a stable release-prep PR merges, run the Build main workflow manually from main with release_channel=stable.
After a stable release is published, prepare the next beta-line PR before the next beta publish attempt if the current beta line is no longer greater than the latest stable tag.

Guardrails

Do not publish stable releases on every merge to main.
Do not publish from release-prep branches or local workstations.
Do not release a version lower than an existing SemVer tag, even if that lower version has a larger run number.
Do not put the leading v in version/STABLE_VERSION or version/BETA_VERSION.
Do not put the numeric beta suffix in version/BETA_VERSION; tags carry the auto-incrementing .N suffix.
Do not treat prereleases as automatically selected by Terraform version ranges; users should pin beta versions explicitly.

Mehr aus diesem Repository

gleiches Repository

manage-ona-with-terraform

gitpod-io/terraform-provider-ona

Safely create, edit, review, import, plan, and troubleshoot Terraform configurations using the gitpod-io/ona provider and ona_* resources. Use for Ona provider setup, resources, data sources, ephemeral resources, Terraform Query, imports, state safety, and provider diagnostics. Do not use for developing the provider's Go implementation.

2026-07-170

terraform-provider-development

gitpod-io/terraform-provider-ona

Build, extend, review, test, or debug the Ona Terraform provider in Go with the Terraform Plugin Framework. Use for provider resources, data sources, ephemeral resources, schema/model changes, import behavior, state drift, generated docs/examples, local Terraform dev loops, acceptance tests, or questions like adding a resource, fixing a perpetual diff, or keeping tokens out of state.

2026-07-160

go-tests

gitpod-io/terraform-provider-ona

Go test patterns for this Terraform provider using table-driven tests, the Expectation pattern, and cmp.Diff. MUST be consulted before writing Go test code, including tests added as part of a larger feature implementation. Use when writing, adding, or fixing Go tests; working with _test.go files; implementing Go behavior that needs test coverage; adding unit tests; testing Terraform provider mapping/model/diagnostic behavior; adding acceptance tests with Terraform Plugin Testing; or verifying Go code with tests. Triggers on "Go test", "write tests", "add tests", "test coverage", "unit test", "_test.go", "verify with tests", "test the implementation", "add test cases", "table-driven test", "cmp.Diff", or any Go implementation task that includes a testing step.

2026-07-140

create-pr

gitpod-io/terraform-provider-ona

Create a pull request for changes in terraform-provider-ona. Use when asked to create a PR, open a PR, submit changes, land changes, prepare a branch, commit changes, write a PR description, or summarize verification.

2026-07-100

review

gitpod-io/terraform-provider-ona

Review code changes in this Terraform provider repository. Use when asked to review, self-review, check a diff, review a PR, or assess changes to Go provider code, Terraform docs, examples, generation, release scripts, or CI for terraform-provider-ona.

2026-07-100

technical-writing

gitpod-io/terraform-provider-ona

Write, edit, or review Terraform provider documentation and examples for terraform-provider-ona. Use for README updates, generated provider docs, examples, release docs, local dev-loop docs, import workflows, and developer-facing prose.

2026-07-100

name	release-prep
description	Prepare beta-line or stable release PRs for terraform-provider-ona by selecting the next provider version, updating version/STABLE_VERSION, version/BETA_VERSION, and CHANGELOG.md as appropriate, validating release metadata, and describing the publish step.

Release Prep

Use this skill when asked to prepare, review, or reason about an Ona Terraform provider release PR.

Release Model

version/STABLE_VERSION is the reviewed stable release intent and contains exact bare SemVer, for example 0.2.0.
version/BETA_VERSION is the reviewed beta release line and contains a bare beta line without the numeric suffix, for example 0.3.0-beta.
GitHub release tags add the leading v, for example v0.2.0 or v0.3.0-beta.7.
terraform-registry-manifest.json version is the Registry manifest schema version, not the provider version.
Pushes to main run CI and automatically publish the next beta tag from version/BETA_VERSION.
Stable publishing is a manual Build main workflow run from main with release_channel=stable after the stable release-prep PR merges.
Local publishing is not supported; the publish scripts are invoked by GitHub Actions on main.

Workflow

Inspect existing tags and releases. Use the highest SemVer tag as the lower bound; use the most recent published tag as the diff base for changelog review when those differ.
For a beta-line PR, update only version/BETA_VERSION to the intended beta line, for example 0.3.0-beta.
For a stable release-prep PR, update version/STABLE_VERSION to exact bare SemVer and update the first CHANGELOG.md heading to the same version.
Run both release metadata checks:
- scripts/validate-release-version.sh --channel stable
- scripts/validate-release-version.sh --channel beta
For a release-prep PR, keep the PR focused on release metadata unless the user asked for release automation changes too.
After a beta-line PR merges, the next push to main publishes the next computed v...-beta.N tag.
After a stable release-prep PR merges, run the Build main workflow manually from main with release_channel=stable.
After a stable release is published, prepare the next beta-line PR before the next beta publish attempt if the current beta line is no longer greater than the latest stable tag.

Guardrails

Do not publish stable releases on every merge to main.
Do not publish from release-prep branches or local workstations.
Do not release a version lower than an existing SemVer tag, even if that lower version has a larger run number.
Do not put the leading v in version/STABLE_VERSION or version/BETA_VERSION.
Do not put the numeric beta suffix in version/BETA_VERSION; tags carry the auto-incrementing .N suffix.
Do not treat prereleases as automatically selected by Terraform version ranges; users should pin beta versions explicitly.