release-management
Release checklist, version strategy, and publishing workflow for JSR/npm. Use when bumping versions, creating releases, or managing the release pipeline.
Works with
--- 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. license: Apache-2.0 --- # Release Management Unified release process for 42 synchronized packages. ## Quick Start 1. `deno task cli ok` — verify clean state; tree must be clean and pushed 2. `eser codebase release <patch|minor|major|same> --dry-run` — preview the version and changelog it would write 3. `eser codebase release <patch|minor|major|same>` — bumps VERSION and every `package.json`, generates the CHANGELOG section, commits `chore(codebase): release v<version>`, pushes, then creates and pushes the annotated `v<version>` tag 4. Watch the tag run at https://github.com/eser/stack/actions ## 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` — pushing it triggers the entire release run in `build.yml` (release-gate → publish → release-notes and the binary chain), not just the release notes - CI never creates tags: a tag pushed by its `GITHUB_TOKEN` dispatches nothing, so the CLI pushes it under the developer's credentials ## 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 — `release-gate` fails the tag run when `CHANGELOG.md` has no section for the tagged version. **"The publish failed, I'll just retag the same version"** Only while nothing has been published. JSR is immutable (yank only) and npm answers a republish with 403, so once `publish` or `publish-ajan` has written anything, re-run the failed jobs (infrastructure error) or cut a new patch version (code fix). ## References See [rules.md](references/rules.md) for full release checklist and hotfix process.
More Deployment & CI/CD skills
finetuning
microsoft/azure-skills
Fine-tune models on Microsoft Foundry using SFT (supervised), DPO (preference), or RFT (reinforcement with graders). Covers dataset preparation, training job submission, deployment, and evaluation. USE FOR: fine-tune, SFT, DPO, RFT, training data, grader, distillation, fine-tuned model, training job, large file upload, calibrate grader, deploy fine-tuned model, evaluate fine-tuned model. DO NOT USE FOR: general model deployment without fine-tuning (use deploy-model), agent creation (use agents), prompt optimization without training (use prompt-optimizer).
prisma-compute
prisma/skills
Prisma Compute deployment and hosting guide. Use whenever the user mentions Prisma Compute, `prisma.compute.ts`, `defineComputeConfig`, deploying or hosting a Prisma app, `@prisma/cli app deploy`, `compute:deploy`, `create-prisma --deploy`, `PRISMA_SERVICE_TOKEN`, Compute auth/workspaces, apps/deployments/build logs/domains, localhost vs `0.0.0.0`, deploy port binding, or framework deploy readiness for Hono, Elysia, Next.js, TanStack Start, Astro, Nuxt, Svelte, Nest, Turborepo, or custom/prebuilt artifacts.
azure-quotas
microsoft/azure-skills
Check/manage Azure quotas and usage across providers. For deployment planning, capacity validation, region selection. WHEN: \"check quotas\", \"service limits\", \"current usage\", \"request quota increase\", \"quota exceeded\", \"validate capacity\", \"regional availability\", \"provisioning limits\", \"vCPU limit\", \"how many vCPUs available in my subscription\".
