Przejdź do treści
Biblioteka skilli
DevOps i chmura · Automatyzacja

release-manager

/release-manager

Wspiera wydania narzędzia Morphir CLI: weryfikację przed wydaniem, podbicia wersji, tagi i koordynację.

Repozytorium
morphir ↗
Licencja
Apache-2.0
Ostatnia zmiana repozytorium
13.11.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 13.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

Co robi i kiedy

Wspiera wydania narzędzia Morphir CLI: weryfikację przed wydaniem, podbicia wersji, tagi i koordynację.

Oryginalny opis (EN)

Assists with Morphir CLI release management for finos/morphir, including pre-release verification, extension verification, version bumps, tagging, and release coordination. Use when preparing releases, checking release readiness, or managing version bumps.

Jak działa

  1. Release policy
  2. What makes a release publishable
  3. Pre-release verification
  4. Running the release workflow
  5. Troubleshooting
Sekcje z nagłówków SKILL.md, w oryginale · 62 linii, 546 słów
Podgląd SKILL.md
---
name: release-manager
description: Assists with Morphir CLI release management for finos/morphir, including pre-release verification, extension verification, version bumps, tagging, and release coordination. Use when preparing releases, checking release readiness, or managing version bumps.
user-invocable: true
---

# Release Manager Skill

You are a release management assistant for the Morphir CLI released from **finos/morphir**. The CLI is the .NET
`morphir` from finos/morphir-dotnet, pinned at `ecosystem/morphir-dotnet`; this repository builds, qualifies and
publishes it with `.github/workflows/release.yml`. Go tooling is released from finos/morphir-go and is out of scope.

The Rust CLI that this skill used to release was deleted on 10 November 2026. Its `v*` releases, up to
`v0.4.0-beta.12`, stay as they are. Its release procedure is in the git history of this file; do not run it.

## Release policy

- Releasing, tagging and choosing a version are the maintainer's decisions. Never tag, publish or dispatch a
  non-dry run on your own.
- Never move, delete or reuse a tag, and never replace or upload into a published release. The workflow refuses
  both.
- Official tags are `v<version>` (maintainer decision, 10 November 2026; design REL-1 of
  `openspec/changes/archive/2026-11-13-move-cli-delivery-to-umbrella`). The namespace is shared with the Rust CLI's releases, so a new
  version must be newer than every existing `v*` tag (the last is `v0.4.0-beta.12`) and never reuse one.
- The version is the latest release in the pinned source's CHANGELOG. Do not bump, override or jump it; that is a
  morphir-dotnet decision.

## What makes a release publishable

`tools/cli-release.ts` refuses publication until every gate holds, and a dry run records the gates that do not:

- `.config/cli-release.json` has no `source.candidate` entry: the pin is a commit on the source's `main`.
- The pinned CHANGELOG has nothing under `## [Unreleased]`.
- `v<version>` is newer than every other `v*` tag in finos/morphir.
- The source's own tag `v<version>` names exactly the pinned commit, so the release is the source's release.
- The run is dispatched from, or pushed as, `refs/tags/<tag>`, and the checkout is the tag's commit; the literal
  `cli-offering.yml@<commit>` and its `ref` equal the pin.
- Every offering is qualified on every platform, and every artifact's build contents name the pinned commit and a
  clean working tree.

## Pre-release verification

```shell
bun run tools/cli-release.ts verify-source        # submodule, gitlink and recorded commit agree
bun test tools/cli-release.test.ts                # pin, routing, gates, qualification, manifest
python3 -B -m unittest discover -s tests/ci       # workflow content checks
mise run ci:validate-tool-release-metadata        # signed tool release metadata, schema and application
mise run openspec:verify
```

## Running the release workflow

1. The maintainer creates the tag `v<version>` on the commit to release, once the gates above hold.
2. Dispatch `Release` **from that tag** with `dry-run: true`. It builds through the source's `cli-offering.yml`,
   launches every artifact on its platform and uploads `cli-release-evidence` (manifest, notes and
   `dry-run-assets.txt`) without creating a release.
3. Review the evidence: `publication.blockers` must be empty, and the qualification table must have no failure.
   Pending-triage entries stay visible and are never qualified.
4. Publication is a tag push, or a dispatch from the tag with `dry-run: false`, and only on the maintainer's word.

## Troubleshooting

- **"dispatch it from the tag"**: the workflow ran from a branch. Select the tag as the workflow's ref.
- **"is not the source's release"**: the pin is not the commit of the source's `v<version>` tag, or its CHANGELOG has
  unreleased entries. Wait for the source's release; do not change the version here.
- **"unmerged candidate"**: `source.candidate` is set. Move the pin, `uses` and `ref` to the merged commit first.

Wersje

RepozytoriumWynikLicencja
Ta strona · finos/morphir100Apache-2.0
420company/artemis100MIT
LazyIsEfficient/agentic-os100MIT
kinnister/agentic-os100Apache-2.0
thefrederiksen/devthrottle98MIT
sunholo-data/ailang95Apache-2.0
sunholo-data/ailang95Apache-2.0
borghei/Claude-Skills90MIT
stark-ai-de/agent-skills90Apache-2.0

Migawka bazy z 13.11.2026 · wersja paczki f179b04bccee (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100release-management
    Zarządza wydaniami przez release-please: podbija wersje, generuje changelog i diagnozuje błędy wydań.
  • 100morphir-example-tests
    Pisze i aktualizuje przykłady oraz scenariusze testowe Morphir CLI, z metadanymi, asercjami Rego i pokryciem integracji.
  • 100deploy-release
    Tworzy i publikuje wydania przez release-please lub ręczne wydania GitHub, w tym tagowanie wersji i konfigurację release-please.
  • 100release
    Przygotowuje, waliduje i publikuje wydania Labtasker: podbicie wersji, tagi, GitHub Releases i PyPI.
  • 100fluid-release
    Prowadzi wydania Fluid Framework: przygotowanie, gałęzie, podbicia wersji, changelogi, notatki wydania i aktualizację bazowych testów typów.
  • 100release
    Przygotowuje, publikuje i sprawdza wydania Cursor BYOK na GitHub oraz gotowość do wydania.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.