Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

release-management

Estrelas128

Forks5

Atualizado15 de abril de 2026 às 07:42

Release checklist, version strategy, and publishing workflow for JSR/npm. Use when bumping versions, creating releases, or managing the release pipeline.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

eser

eser/stack

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

Explorador de arquivos

2 arquivos

SKILL.md

readonly

name	release-management
description	Release checklist, version strategy, and publishing workflow for JSR/npm. Use when bumping versions, creating releases, or managing the release pipeline.

Release Management

Unified release process for 29+ synchronized packages.

Quick Start

deno task validate — verify clean state
deno task cli codebase versions <patch|minor|major> — bump all packages
Update CHANGELOG.md — move Unreleased to new version section
PR to main → merge triggers JSR + npm publish

Key Principles

All packages share one version — no independent releases
JSR primary (OIDC auth), npm secondary (only @eserstack/cli as eser)
patch: bug fixes, docs, deps. minor: new features. major: breaking changes
Always update CHANGELOG before releasing
Tag format: vx.y.z (triggers release-notes-sync workflow)

Anti-Patterns

"I'll just edit one package's version" No. Use the version-bump script. Manual edits break synchronization.

"Skip the changelog, it's a small fix" No. Every release needs a changelog entry for traceability.

References

See rules.md for full release checklist and hotfix process.

Mais deste repositório

mesmo repositório

javascript-practices

eser/stack

JavaScript/TypeScript conventions: ES modules, Deno runtime, React patterns, async/await, and type handling. Use when writing .ts, .tsx, or .js files, configuring imports, or building React components.

2026-04-15128

tooling-standards

eser/stack

Development tooling: Deno runtime, JSR package registry, deno.json and package.json configuration, and editor settings. Use when setting up projects, choosing packages, or configuring build tools.

2026-04-15128

agent-guidelines

eser/stack

Agent roles, safety rules, file ownership, and cross-package change protocol. Use when AI agents work on this codebase, plan multi-package changes, or need boundary guidance.

2026-04-15128

security-practices

eser/stack

Security practices: secrets in env vars, input validation, SSRF prevention, error sanitization, and production hardening. Use when handling authentication, secrets, user input, or preparing production deployments.

2026-04-15128

architecture-guidelines

eser/stack

System architecture: ES modules, hexagonal architecture, project structure, ADRs, and testing strategy. Use when designing systems, planning directory layout, writing ADRs, or reviewing architecture.

2026-04-15128

ci-cd-practices

eser/stack

CI/CD operations: GitHub Actions, Kubernetes, ArgoCD, and CI timeout configuration. Use when configuring pipelines, debugging deployments, or working with GitHub Actions. Do NOT use for general development workflow.

2026-04-15128

name	release-management
description	Release checklist, version strategy, and publishing workflow for JSR/npm. Use when bumping versions, creating releases, or managing the release pipeline.

Release Management

Unified release process for 29+ synchronized packages.

Quick Start

deno task validate — verify clean state
deno task cli codebase versions <patch|minor|major> — bump all packages
Update CHANGELOG.md — move Unreleased to new version section
PR to main → merge triggers JSR + npm publish

Key Principles

All packages share one version — no independent releases
JSR primary (OIDC auth), npm secondary (only @eserstack/cli as eser)
patch: bug fixes, docs, deps. minor: new features. major: breaking changes
Always update CHANGELOG before releasing
Tag format: vx.y.z (triggers release-notes-sync workflow)

Anti-Patterns

"I'll just edit one package's version" No. Use the version-bump script. Manual edits break synchronization.

"Skip the changelog, it's a small fix" No. Every release needs a changelog entry for traceability.

References

See rules.md for full release checklist and hotfix process.