release-package

name	Release Package
description	Instructions and guidelines on how package versioning, changelog generation, and NPM releases are managed using semantic-release in the tanstack-i18n monorepo.

Package Versioning & Release Workflow

This skill explains how versioning and package releases are managed using semantic-release in the tanstack-i18n repository.

[!IMPORTANT] AI Agent Responsibility Boundary: When asked to prepare a feature or fix for release, DO NOT manually create changeset files or edit package.json versions.

Releasable changes are driven entirely by Conventional Commit messages. When your commits are merged to main, GitHub Actions automatically runs semantic-release to analyze commits, update CHANGELOG.md, bump package.json, and publish to NPM.

---

1. Conventional Commits and Version Bumps

Package version bumps are automatically calculated based on the commit history on main:

Commit Type	Version Bump	Example
fix:, perf:	patch	fix(tanstack-i18n): parse max-age correctly
feat:	minor	feat(tanstack-i18n): add solid-start adapter
feat!: or BREAKING CHANGE: footer	major	feat(tanstack-i18n)!: remove deprecated runtime option
chore:, docs:, test:, refactor:, ci:	no release	docs(docs): update setup instructions

---

2. Automated Release Execution (GitHub Actions)

Releases are run exclusively by the GitHub Actions runner (release.yml) on main:

• When a push to main completes the CI workflow successfully, release.yml executes pnpm exec semantic-release in packages/tanstack-i18n.
• semantic-release:
  1. Determines the next release version from new commits.
  2. Generates release notes.
  3. Updates packages/tanstack-i18n/CHANGELOG.md and packages/tanstack-i18n/package.json.
  4. Publishes @wadiou/tanstack-i18n to NPM.
  5. Pushes a GitHub Release and git tag.
  6. Commits release changes back to main with [skip ci].