Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: release 2.0.1 #54

Closed
wants to merge 1 commit into from
Closed

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Dec 4, 2023

🤖 I have created a release beep boop

2.0.1 (2024-04-21)

Documentation

Chores


This PR was generated with Release Please. See documentation.

Copy link
Contributor Author

github-actions bot commented Dec 4, 2023

Release Manager

Release workflow run: https://github.com/npm/npm-user-validate/actions/runs/8774103848

Release Checklist for v2.0.1

  • 1. Checkout the release branch and test

    gh pr checkout 54 --force
    npm update
    npm test
    gh pr checks 54 -R npm/npm-user-validate --watch
  • 2. Publish

    npm publish --tag=latest
  • 3. Merge release PR

    gh pr merge 54 -R npm/npm-user-validate --squash
    git checkout main
    git fetch
    git reset --hard origin/main
  • 4. Check For Release Tags

    Release Please will run on the just pushed release commit and create GitHub releases and tags for each package.

    gh run watch -R npm/npm-user-validate $(gh run list -R npm/npm-user-validate -w release -b main -L 1 --json databaseId -q ".[0].databaseId")

@github-actions github-actions bot force-pushed the release-please--branches--main branch 2 times, most recently from 630e895 to acd4123 Compare December 7, 2023 22:37
@github-actions github-actions bot force-pushed the release-please--branches--main branch 2 times, most recently from d371d61 to 033cba3 Compare March 20, 2024 14:39
@github-actions github-actions bot force-pushed the release-please--branches--main branch from 033cba3 to 31e2469 Compare April 21, 2024 16:42
@github-actions github-actions bot force-pushed the release-please--branches--main branch from 31e2469 to a33f0c0 Compare April 21, 2024 16:43
@lukekarrys lukekarrys closed this May 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant