Skip to content

RELEASING.md

Latest commit

 

History

History
47 lines (33 loc) · 1.11 KB

RELEASING.md

File metadata and controls

47 lines (33 loc) · 1.11 KB

Release Process

1. Bump Version

Update version in both files:

# Edit Cargo.toml - update workspace.package.version
# Edit crates/monty-js/package.json - update version

# Update Cargo.lock
make lint-rs

Both Cargo.toml and package.json should have the same version (e.g., 0.0.2).

2. Commit and Push

git add Cargo.toml Cargo.lock crates/monty-js/package.json
git commit -m "Bump version to X.Y.Z"
git push

3. Create Release via GitHub UI

  1. Go to https://github.com/pydantic/monty/releases/new
  2. Click "Choose a tag" and type the new tag name (e.g., v0.0.2)
  3. Select "Create new tag on publish"
  4. Set the release title (e.g., v0.0.2)
  5. Add release notes
  6. Click "Publish release"

4. CI Handles Publishing

Once the tag is pushed, CI will:

  • Build wheels for all platforms
  • Publish to PyPI (pydantic-monty)
  • Publish to NPM (@pydantic/monty)

Monitor the workflow at https://github.com/pydantic/monty/actions

Pre-release Tags

For pre-releases (alpha, beta, rc), use a tag like v0.0.2-beta.1:

  • PyPI: Published normally
  • NPM: Published with --tag next (not latest)
⚡