Skip to content

Conversation

@NSeydoux
Copy link
Contributor

@NSeydoux NSeydoux commented Jul 4, 2024

This PR bumps the version to 0.0.1.

Release Steps

  1. Look at the CHANGELOG.md to determine whether the release should be a major, minor, or patch release. Coordinate with the team to ensure the next version is agreed upon.
  2. Run npm version -- <major|minor|patch> --no-push with the decided on version (to prevent the tag from being pushed).
  3. Update the CHANGELOG.md to release the latest the version, and set the release date.
  4. Add the @since X.Y.Z annotations to new APIs.
  5. Commit the changes on a release/vX.Y.Z branch
  6. Push to GitHub, create a PR, and merge once CI passes.
  7. Create a release on GitHub for the new version, using a combination of the release notes from the CHANGELOG.md and the automatically generated changes.
    The release should have a new tag matching the new version number: vx.y.z, and point to the release commit.

@NSeydoux NSeydoux requested a review from a team as a code owner July 4, 2024 14:23
Copy link
Contributor

@edwardsph edwardsph left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@NSeydoux NSeydoux enabled auto-merge (squash) July 8, 2024 09:39
@NSeydoux NSeydoux merged commit 5ca1279 into main Jul 8, 2024
@NSeydoux NSeydoux deleted the release/0.0.1 branch July 8, 2024 09:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants