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.0.0 #194

Merged
merged 1 commit into from
Jul 28, 2023
Merged

chore: release 15.0.0 #194

merged 1 commit into from
Jul 28, 2023

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Jul 27, 2023

🤖 I have created a release beep boop

15.0.0 (2023-07-28)

⚠️ BREAKING CHANGES

  • the underlying fetch module now uses @npmcli/agent. Backwards compatibility should be fully implemented but due to the scope of this change it was made a breaking change out of an abundance of caution.
  • support for node 14 has been removed

Bug Fixes

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 July 27, 2023 20:10
@github-actions
Copy link
Contributor Author

github-actions bot commented Jul 27, 2023

Release Manager

Release workflow run: https://github.com/npm/npm-registry-fetch/actions/runs/5692683791

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/npm-registry-fetch -f release-pr=194

Release Checklist for v15.0.0

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

    gh pr merge 194 -R npm/npm-registry-fetch --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 -R npm/npm-registry-fetch $(gh run list -R npm/npm-registry-fetch -w release -b main -L 1 --json databaseId -q ".[0].databaseId")
    

@github-actions github-actions bot force-pushed the release-please--branches--main branch 4 times, most recently from 8abf24d to 264314f Compare July 28, 2023 13:48
@github-actions github-actions bot force-pushed the release-please--branches--main branch from 264314f to 84bb4aa Compare July 28, 2023 13:49
@wraithgar wraithgar merged commit 16893c3 into main Jul 28, 2023
14 checks passed
@wraithgar wraithgar deleted the release-please--branches--main branch July 28, 2023 13:58
@github-actions
Copy link
Contributor Author

github-actions bot commented Jul 28, 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