원클릭으로 Manus에서 모든 스킬 실행

publish-semver

스타0

포크0

업데이트2026년 6월 27일 14:13

Set up semantic or calendar versioning and package publishing across supported ecosystems. Use when configuring release automation or changelogs.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

r3dlex

r3dlex/skills

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

publish-semver

Version Model

Every push to main creates a pre-release. A Release-Please PR merge or semantic-release stable tag promotes it to stable.

0.1.3-pre.1   ← push to main
0.1.3-pre.2   ← push to main
0.1.3         ← stable release

Commit type controls the next stable bump:

fix: → patch (0.1.2 → 0.1.3)
feat: → minor (0.1.2 → 0.2.0)
feat!: / BREAKING CHANGE: → major (0.1.2 → 1.0.0)

Step 1: Pick Your Host

Host	CI system	Private registry
GitHub	GitHub Actions	GitHub Packages
Azure DevOps	Azure Pipelines	Azure Artifacts

Read the host file first. It contains the full CI job scaffold, auth patterns, visibility checks, and floating tag steps.

GitHub → host-github.md
Azure DevOps → host-ado.md

Step 2: Pick Your Strategy

Strategy	How it works	Best for
Release-Please	Accumulates commits into a release PR. Stable publish on PR merge.	Teams that want a review gate.
semantic-release	Tags and publishes on every qualifying push to `main`.	Fully automated pipelines.

Both produce pre-releases on every push to main.

Step 3: Pick Your Ecosystem

Ecosystem	File
JS/TS + npm	js-npm.md
Python + PyPI	python-pypi.md
Elixir + Hex	elixir-hex.md
Elixir + Burrito binaries	elixir-burrito.md
Rust + crates.io	rust-crates.md
C# + NuGet	csharp-nuget.md
Dart / Flutter + pub.dev	dart-pub.md
Java + Maven Central	java-maven.md
Kotlin + Gradle + Maven Central	kotlin-gradle.md
Erlang + Hex	erlang-hex.md

Step 4: Compose the Workflow

Ecosystem files provide publish commands and version bump logic only. The host file provides the full CI job scaffold. Combine them:

Copy the job scaffold from the host file.
Replace the # ECOSYSTEM PUBLISH STEPS placeholder with commands from the ecosystem file.
Add required secrets from the ecosystem file to your CI secret store.

Supporting References

Need	File
Floating major version tags	floating-tags.md
CHANGELOG and release file conventions	release-files.md

이 저장소의 다른 Skills

같은 저장소

ai-catapult-init

r3dlex/skills

Bootstrap AI-ready repo governance, traceability, cascade, catalog audits, validation. Deprecated compatibility aliases: init-ai-repo, ai-sdlc-init. Use when setting up AI SDLC.

2026-07-020

ai-sdlc-init

r3dlex/skills

Deprecated compatibility alias for ai-catapult-init. Use only when legacy prompts invoke "ai-sdlc-init"; otherwise use "ai-catapult-init".

2026-07-010

autobahn

r3dlex/skills

Ship a northstar handoff's goals in an ai-catapult-init repo — ultragoal one-PR-per-goal, deterministic engine-pick, peer review, CI gate, fail-closed merge, cascade closure.

2026-07-010

eval-a-skill

r3dlex/skills

Scaffold a structurally valid eval triplet for a target skill under .ai/evals/. CI checks structure only; the LM-judge runs out-of-band, never in CI.

2026-07-010

init-ai-repo

r3dlex/skills

Deprecated compatibility alias for ai-catapult-init. Use only when legacy prompts invoke "init-ai-repo"; otherwise use "ai-catapult-init".

2026-07-010

northstar

r3dlex/skills

Intake intent into a tracked, sliced plan in an ai-catapult-init repo — deep-interview + skippable grill-me, always raise an issue, ralplan, write the A→B handoff.

2026-07-010

publish-semver

Version Model

Every push to main creates a pre-release. A Release-Please PR merge or semantic-release stable tag promotes it to stable.

0.1.3-pre.1 ← push to main 0.1.3-pre.2 ← push to main 0.1.3 ← stable release

Commit type controls the next stable bump:

fix: → patch (0.1.2 → 0.1.3)

feat: → minor (0.1.2 → 0.2.0)

feat!: / BREAKING CHANGE: → major (0.1.2 → 1.0.0)

Step 1: Pick Your Host

Host

CI system

Private registry

GitHub

GitHub Actions

GitHub Packages

Azure DevOps

Azure Pipelines

Azure Artifacts

Read the host file first. It contains the full CI job scaffold, auth patterns, visibility checks, and floating tag steps.

Step 2: Pick Your Strategy

Strategy

How it works

Best for

Release-Please

Accumulates commits into a release PR. Stable publish on PR merge.

Teams that want a review gate.

semantic-release

Tags and publishes on every qualifying push to main.

Fully automated pipelines.

Both produce pre-releases on every push to main.

Step 3: Pick Your Ecosystem

Ecosystem

File

JS/TS + npm

js-npm.md

Python + PyPI

python-pypi.md

Elixir + Hex

elixir-hex.md

Elixir + Burrito binaries

elixir-burrito.md

Rust + crates.io

rust-crates.md

C# + NuGet

csharp-nuget.md

Dart / Flutter + pub.dev

dart-pub.md

Java + Maven Central

java-maven.md

Kotlin + Gradle + Maven Central

kotlin-gradle.md

Erlang + Hex

erlang-hex.md

Step 4: Compose the Workflow

Ecosystem files provide publish commands and version bump logic only. The host file provides the full CI job scaffold. Combine them:

Copy the job scaffold from the host file.

Replace the # ECOSYSTEM PUBLISH STEPS placeholder with commands from the ecosystem file.

Add required secrets from the ecosystem file to your CI secret store.

Supporting References

Need

File

Floating major version tags

floating-tags.md

CHANGELOG and release file conventions

release-files.md

name	publish-semver
description	Set up semantic or calendar versioning and package publishing across supported ecosystems. Use when configuring release automation or changelogs.