chore: bump semver from 7.5.4 to 7.6.0 #1673
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps [semver](https://github.com/npm/node-semver) from 7.5.4 to 7.6.0. - [Release notes](https://github.com/npm/node-semver/releases) - [Changelog](https://github.com/npm/node-semver/blob/main/CHANGELOG.md) - [Commits](npm/node-semver@v7.5.4...v7.6.0) --- updated-dependencies: - dependency-name: semver dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
dependencies
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1673 +/- ##
==========================================
- Coverage 92.03% 91.80% -0.24%
==========================================
Files 16 16
Lines 854 854
Branches 167 167
==========================================
- Hits 786 784 -2
- Misses 51 52 +1
- Partials 17 18 +1 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
https://app.codecov.io/gh/electron/packager/pull/1673/indirect-changes
Not a blocker, but it is kind of weird for a semver/minor dependency bump to change our code coverage.
Approving, but leaving unmerged pending a 2nd reviewer's opinion
|
Oh I see, other PRs bumping other dependencies are showing the same results, e.g. https://app.codecov.io/gh/electron/packager/pull/1672/indirect-changes. Looks to me like this is unrelated to semver per se, probably something's changed in CI or main and even an empty commit PR would trigger the same codecov warning. |
|
🎉 This PR is included in version 18.2.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Bumps semver from 7.5.4 to 7.6.0.
Release notes
Sourced from semver's releases.
Changelog
Sourced from semver's changelog.
Commits
377f709chore: release 7.6.0 (#661)a7ab13afeat: preserve pre-release and build parts of a version on coerce (#671)816c7b2chore: postinstall for dependabot template-oss PR0bd24d9chore: bump@npmcli/template-ossfrom 4.21.1 to 4.21.3e521932chore: postinstall for dependabot template-oss PR8873991chore: chore: chore: postinstall for dependabot template-oss PRf317dc8chore: bump@npmcli/template-ossfrom 4.19.0 to 4.21.07303db1chore: add clean() test for build metadata (#658)6240d75chore: add missing quotes in README.md (#656)14d263fchore: postinstall for dependabot template-oss PRDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)