Bump cookiejar from 2.1.3 to 2.1.4 - #54
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [cookiejar](https://github.com/bmeck/node-cookiejar) from 2.1.3 to 2.1.4. - [Release notes](https://github.com/bmeck/node-cookiejar/releases) - [Commits](https://github.com/bmeck/node-cookiejar/commits) --- updated-dependencies: - dependency-name: cookiejar dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
the
dependencies
foxpatch-aleph
left a comment
foxpatch-aleph
left a comment
There was a problem hiding this comment.
This is a Dependabot security update bumping cookiejar from 2.1.3 to 2.1.4. The actual change is straightforward and correct — only the cookiejar version is updated in both package-lock.json and yarn.lock. The bulk of the diff consists of unrelated lockfile changes: @solana/web3.js being upgraded from 0.90.5 to 1.73.0 (with its updated dependency tree), jayson from 3.6.5 to 3.7.0, rpc-websockets from 7.4.16 to 7.5.0, and numerous packages being re-classified as devDependencies. These changes appear to be pre-existing lockfile drift that Dependabot resolved during its rebase, not introduced by this PR's author. No source code changes are present. The cookiejar update itself addresses a ReDoS vulnerability (CVE-2022-25901) and the upgrade is safe to merge.
package-lock.json (line None): The lockfile contains significantly more changes than just the cookiejar bump — notably @solana/web3.js jumps from 0.90.5 to 1.73.0, which is a major version upgrade with substantial API changes. This appears to be pre-existing drift that Dependabot resolved when rebasing. It's worth verifying that the project's actual package.json still pins @solana/web3.js appropriately and that CI tests pass, since this indirect upgrade could have behavioral implications at runtime.
This branch has not been deployed
1 participant
Bumps cookiejar from 2.1.3 to 2.1.4.
Commits
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 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 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)@dependabot use these labelswill set the current labels as the default for future PRs for this repo and language@dependabot use these reviewerswill set the current reviewers as the default for future PRs for this repo and language@dependabot use these assigneeswill set the current assignees as the default for future PRs for this repo and language@dependabot use this milestonewill set the current milestone as the default for future PRs for this repo and languageYou can disable automated security fix PRs for this repo from the Security Alerts page.