Closed depfu[bot] closed 3 months ago
:tada: This PR is included in version 2.0.3-develop.21 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
:tada: This PR is included in version 2.0.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ @semantic-release/npm (12.0.0 → 12.0.1) · Repo
Release Notes
12.0.1
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 24 commits:
fix(deps): update dependency execa to v9
ci(action): update actions/checkout action to v4.1.5 (#796)
chore(deps): update dependency sinon to v17.0.2 (#795)
chore(deps): lock file maintenance (#794)
chore(deps): update dependency ava to v6.1.3 (#793)
chore(deps): update npm to v10.7.0 (#788)
chore(deps): update npm to v10.6.0
chore(deps): lock file maintenance (#787)
chore(deps): lock file maintenance (#786)
ci(action): update actions/checkout action to v4.1.4 (#782)
ci(action): update actions/checkout action to v4.1.3 (#781)
chore(deps): lock file maintenance (#780)
chore(deps): lock file maintenance (#778)
chore(deps): update npm to v10.5.2 (#776)
chore(deps): update dependency semantic-release to v23.0.8 (#775)
chore(deps): lock file maintenance (#774)
chore(deps): update npm to v10.5.1
chore(deps): update dependency semantic-release to v23.0.7 (#772)
chore(deps): lock file maintenance (#770)
chore(deps): lock file maintenance (#769)
chore(deps): update dependency semantic-release to v23.0.6 (#768)
chore(deps): lock file maintenance (#760)
chore(deps): update dependency semantic-release to v23.0.5 (#765)
ci(corepack): pinned the expected dev version of npm and explicitly used it for audit signatures (#764)
🆕 @sec-ant/readable-stream (added, 0.4.1)
🆕 is-plain-obj (added, 4.1.0)
🆕 parse-ms (added, 4.0.0)
🆕 pretty-ms (added, 9.0.0)
🆕 yoctocolors (added, 2.0.2)
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands