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 4.12.0 #280

Merged
merged 1 commit into from
Mar 2, 2023
Merged

chore: release 4.12.0 #280

merged 1 commit into from
Mar 2, 2023

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Feb 7, 2023

🤖 I have created a release beep boop

4.12.0 (2023-02-13)

Features

Bug Fixes


This PR was generated with Release Please. See documentation.

@github-actions github-actions bot requested a review from a team as a code owner February 7, 2023 23:08
@github-actions github-actions bot requested review from nlf and removed request for a team February 7, 2023 23:08
@github-actions
Copy link
Contributor Author

github-actions bot commented Feb 7, 2023

Release Manager

Release workflow run: https://github.com/npm/template-oss/actions/runs/4168836508

Force CI to Update This Release

This PR will be updated and CI will run for every non-chore: commit that is pushed to main. To force CI to update this PR, run this command:

gh workflow run release.yml -r main -R npm/template-oss -f release-pr=280

Release Checklist for v4.12.0

  • 1. Checkout the release branch and test

    gh pr checkout 280 --force
    npm update
    npm test
    gh pr checks --watch
  • 2. Publish

    npm publish 
  • 3. Merge release PR

    gh pr merge --rebase
    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 `gh run list -R npm/template-oss -w release -b main -L 1 --json databaseId -q ".[0].databaseId"`
    

@github-actions github-actions bot force-pushed the release-please--branches--main branch 5 times, most recently from f12946d to 3b64b5e Compare February 8, 2023 20:40
@github-actions github-actions bot changed the title chore: release 4.11.5 chore: release 4.12.0 Feb 13, 2023
@github-actions github-actions bot force-pushed the release-please--branches--main branch from 3b64b5e to 37f9449 Compare February 13, 2023 23:33
@github-actions github-actions bot force-pushed the release-please--branches--main branch from 37f9449 to 164e41e Compare February 13, 2023 23:34
@lukekarrys lukekarrys merged commit ec46755 into main Mar 2, 2023
@lukekarrys lukekarrys deleted the release-please--branches--main branch March 2, 2023 18:31
@github-actions
Copy link
Contributor Author

github-actions bot commented Mar 2, 2023

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