Bump yargs-parser and electron-packager #22
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.
Bumps yargs-parser to 21.1.1 and updates ancestor dependency electron-packager. These dependencies need to be updated together.
Updates
yargs-parser
from 16.1.0 to 21.1.1Release notes
Sourced from yargs-parser's releases.
... (truncated)
Changelog
Sourced from yargs-parser's changelog.
... (truncated)
Commits
3aba24c
chore(main): release yargs-parser 21.1.1 (#455)d69f9c3
fix(typescript): ignore .cts files during publish (#454)90067a0
chore(main): release yargs-parser 21.1.0 (#446)d07bcdb
fix: node version check now uses process.versions.node (#450)c0c6079
chore(deps): update dependency puppeteer to v16 (#451)a89259f
feat: allow the browser build to be imported (#443)c474bc1
fix(halt-at-non-option): prevent known args from being parsed when "unknown-o...fd30238
chore(deps): update dependency serve to v14 (#449)a072f9a
chore(deps): update dependency puppeteer to v15 (#444)4f1060b
fix: parse options ending with 3+ hyphens (#434)Maintainer changes
This version was pushed to npm by oss-bot, a new releaser for yargs-parser since your current version.
Updates
electron-packager
from 14.2.1 to 17.1.1Release notes
Sourced from electron-packager's releases.
... (truncated)
Changelog
Sourced from electron-packager's changelog.
... (truncated)
Commits
7eb0ce5
17.1.1745d286
fix: allow packaging twice simultaneously (#1439)c772bff
17.1.0fff1487
feat: add new afterFinalizePackageTargets hook (#1437)5aac8c9
feat: New lifecycle hooks: afterAsar, afterComplete, afterCopyExtraResources,...df3383c
refactor: migrate from electron-notarize to@electron/notarize
(#1433)b56ea8a
17.0.034c3c4e
docs: update NEWS.md for v17.0.021bb953
refactor: migrate from asar to@electron/asar
(#1431)274c686
feat!: upgrade electron-osx-sign to@electron/osx-sign
(#1428)Maintainer changes
This version was pushed to npm by georgexu99, a new releaser for electron-packager since your current version.
Dependabot 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 rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major version
will 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 version
will 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 dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.