chore: release 7.0.0 #149
Merged
chore: release 7.0.0 #149
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Author
Release ManagerRelease workflow run: https://github.com/npm/package-json/actions/runs/16526072413 Release Checklist for v7.0.0
|
github-actions
bot
force-pushed
the
release-please--branches--main
branch
from
8171366 to
faf18ac
Compare
Member
|
Waiting on #144 before we cut a release |
github-actions
bot
force-pushed
the
release-please--branches--main
branch
4 times, most recently
from
5b7d9e6 to
7a592e8
Compare
github-actions
bot
force-pushed
the
release-please--branches--main
branch
from
7a592e8 to
c97e76a
Compare
github-actions
bot
force-pushed
the
release-please--branches--main
branch
from
c97e76a to
d01a181
Compare
This was referenced Aug 19, 2025
Merged
owlstronaut
approved these changes
Aug 28, 2025
Contributor
Author
|
🤖 Created releases: 🌻 |
Contributor
Author
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🤖 I have created a release beep boop
7.0.0 (2025-07-25)
package-jsonnow supports node^20.17.0 || >=22.9.0Features
9dd0eb5#144 add syncNormalize (@wraithgar)08eae47#144 add binDir step to normalize function (@wraithgar)Bug Fixes
a5e4ac3#152 align to npm 11 node engine range (@owlstronaut)4695e87#150 useURL.canParseinstead of runtime deprecatedurl.parseapi (fix: useURL.canParseinstead of runtime deprecatedurl.parseapi #150) (@SuperchupuDev)dbc9ef1#144 require an object in fromContent() (@wraithgar)f06eb18#144 remove unused bundleDependenciesFalse (@wraithgar)a8b1cc9#144 secure and unixify paths discovered via directories.bin (@wraithgar)23c29a9#144 remove erroneous bundledDependencies log (@wraithgar)Documentation
14f8141#147 adding sort option docs to README (docs: adding sort option docs to README #147) (@idhard)Dependencies
a0dcfde#152[email protected]41128c1#152[email protected]Chores
a179a87#144 fix tests to await async normalize (@wraithgar)203fec8#144 remove read-package-json (@wraithgar)7bde184#144 remove read-package-json-fast (@wraithgar)394192d#144 remove backward compatiblity tests (@wraithgar)6e89e39#148 bump @npmcli/template-oss from 4.23.6 to 4.25.0 (chore: bump @npmcli/template-oss from 4.23.6 to 4.25.0 #148) (@dependabot[bot], @owlstronaut)This PR was generated with Release Please. See documentation.