# Release

> Release a new version of the coerce-form-data npm package. Bump version, build, publish, and create a GitHub release. Use when the user mentions releasing, publishing, cutting a release, or shipping a new version.

- Skill: `seasonedcc/release-7` (Agent Skill)
- Install (CLI): `npx get-skill add seasonedcc/release-7`
- Raw SKILL.md: https://api.skillmd.com/api/skills/seasonedcc/release-7/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: seasonedcc (https://skillmd.com/u/seasonedcc)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/seasonedcc/release-7

---


# Release

Automate the release workflow for the `coerce-form-data` npm package.

## Instructions

### 1. Determine the next version

Find the latest git tag:

```bash
git tag --list 'v*' --sort=-version:refname | head -1
```

Read the current version from `package.json`.

Get the diff since the last release tag:

```bash
git log <last-tag>..HEAD --oneline
git diff <last-tag>..HEAD --stat
```

Determine the next version following semver:
- **patch** for bug fixes and dependency updates
- **minor** for new features that are backwards-compatible
- **major** for breaking changes

Bump the patch version unless the user specifies otherwise.

### 2. Bump version in package.json

Edit `package.json` to set the new version number.

### 3. Run pnpm install

```bash
pnpm install
```

This updates the lockfile with the new version.

### 4. Run checks

```bash
pnpm run lint-fix && pnpm run lint && pnpm run tsc && pnpm run test && pnpm run build
```

All must pass before proceeding.

### 5. Commit and push

Commit `package.json` and `pnpm-lock.yaml` with message `v<new-version>`. Push to `main`.

### 6. Ask the user to publish

Tell the user to run:

```bash
npm publish
```

**Do not run `npm publish` yourself** — it requires an OTP. Wait for the user to confirm they've published before continuing.

### 7. Create the GitHub release

Once the user confirms the publish, create a GitHub release.

Write release notes by analyzing the diff between the previous tag and `HEAD`. Follow the pattern from previous releases:

- For **major releases**: Include narrative sections describing breaking changes and new features, followed by a `## What's Changed` section with PR links and a `**Full Changelog**` compare link.
- For **minor/patch releases**: A `## What's Changed` section with bullet points linking to merged PRs, and a `**Full Changelog**` compare link.

List merged PRs between the two tags:

```bash
gh pr list --search "is:merged merged:>=<last-tag-date>" --json number,title,author --limit 100
```

Format each PR as:

```
* <title> by @<author> in https://github.com/seasonedcc/coerce-form-data/pull/<number>
```

End with:

```
**Full Changelog**: https://github.com/seasonedcc/coerce-form-data/compare/v<previous>...v<new>
```

Create the release:

```bash
gh release create v<new-version> --title "v<new-version>" --notes "<release-notes>"
```

Use a HEREDOC for the notes to preserve formatting.

