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 5.0.0 #124

Merged
merged 1 commit into from
Aug 26, 2024
Merged

chore: release 5.0.0 #124

merged 1 commit into from
Aug 26, 2024

Conversation

github-actions[bot]
Copy link
Contributor

🤖 I have created a release beep boop

5.0.0 (2024-08-26)

⚠️ BREAKING CHANGES

  • @npmcli/eslint-config now supports node ^18.17.0 || >=20.5.0

Bug Fixes

Dependencies

Chores


This PR was generated with Release Please. See documentation.

Copy link
Contributor Author

github-actions bot commented Aug 26, 2024

Release Manager

Release workflow run: https://github.com/npm/eslint-config/actions/runs/10562538124

Release Checklist for v5.0.0

  • 1. Approve this PR

    gh pr review 124 -R npm/eslint-config --approve
  • 2. Merge release PR 🚨 Merging this will auto publish 🚨

    gh pr merge 124 -R npm/eslint-config --squash
  • 3. 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/eslint-config $(gh run list -R npm/eslint-config -w release -b main -L 1 --json databaseId -q ".[0].databaseId")

@github-actions github-actions bot force-pushed the release-please--branches--main branch from 42b326c to bd1f276 Compare August 26, 2024 15:24
@hashtagchris hashtagchris merged commit 9b0dfca into main Aug 26, 2024
17 checks passed
@hashtagchris hashtagchris deleted the release-please--branches--main branch August 26, 2024 16:37
Copy link
Contributor Author

🤖 Created releases:

Copy link
Contributor Author

github-actions bot commented Aug 26, 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