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 15.1.2 #268

Merged
merged 1 commit into from
Apr 20, 2023
Merged

chore: release 15.1.2 #268

merged 1 commit into from
Apr 20, 2023

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Apr 3, 2023

🤖 I have created a release beep boop

15.1.2 (2023-04-20)

Documentation

Dependencies


This PR was generated with Release Please. See documentation.

@github-actions github-actions bot requested a review from a team as a code owner April 3, 2023 17:44
@github-actions github-actions bot removed the request for review from a team April 3, 2023 17:44
@github-actions github-actions bot requested a review from nlf April 3, 2023 17:44
@github-actions
Copy link
Contributor Author

github-actions bot commented Apr 3, 2023

Release Manager

Release workflow run: https://github.com/npm/pacote/actions/runs/4758533139

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/pacote -f release-pr=268

Release Checklist for v15.1.2

  • 1. Merge release PR 🚨 Merging this will auto publish 🚨

    gh pr merge 268 -R npm/pacote --rebase
  • 2. 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/pacote -w release -b main -L 1 --json databaseId -q ".[0].databaseId"`
    

@github-actions github-actions bot force-pushed the release-please--branches--main branch 3 times, most recently from 179076e to 4cb2dc0 Compare April 3, 2023 17:48
@github-actions github-actions bot force-pushed the release-please--branches--main branch 3 times, most recently from 8d105e4 to f691508 Compare April 12, 2023 18:49
@github-actions github-actions bot force-pushed the release-please--branches--main branch 2 times, most recently from c0ac9f7 to 7ca6b24 Compare April 20, 2023 20:15
@wraithgar
Copy link
Member

Don't land before #275

@github-actions github-actions bot force-pushed the release-please--branches--main branch from 7ca6b24 to dba601b Compare April 20, 2023 20:20
@github-actions github-actions bot force-pushed the release-please--branches--main branch from dba601b to bfe1a0c Compare April 20, 2023 20:21
@wraithgar wraithgar merged commit 7d96b7b into main Apr 20, 2023
@wraithgar wraithgar deleted the release-please--branches--main branch April 20, 2023 20:32
@github-actions
Copy link
Contributor Author

github-actions bot commented Apr 20, 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