Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump jsonwebtoken and danger #48

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Feb 25, 2025

Bumps jsonwebtoken to 9.0.2 and updates ancestor dependency danger. These dependencies need to be updated together.

Updates jsonwebtoken from 8.5.1 to 9.0.2

Changelog

Sourced from jsonwebtoken's changelog.

9.0.2 - 2023-08-30

  • security: updating semver to 7.5.4 to resolve CVE-2022-25883, closes #921.
  • refactor: reduce library size by using lodash specific dependencies, closes #878.

9.0.1 - 2023-07-05

  • fix(stubs): allow decode method to be stubbed

9.0.0 - 2022-12-21

Breaking changes: See Migration from v8 to v9

Breaking changes

  • Removed support for Node versions 11 and below.
  • The verify() function no longer accepts unsigned tokens by default. ([834503079514b72264fd13023a3b8d648afd6a16]auth0/node-jsonwebtoken@8345030)
  • RSA key size must be 2048 bits or greater. ([ecdf6cc6073ea13a7e71df5fad043550f08d0fa6]auth0/node-jsonwebtoken@ecdf6cc)
  • Key types must be valid for the signing / verification algorithm

Security fixes

  • security: fixes Arbitrary File Write via verify function - CVE-2022-23529
  • security: fixes Insecure default algorithm in jwt.verify() could lead to signature validation bypass - CVE-2022-23540
  • security: fixes Insecure implementation of key retrieval function could lead to Forgeable Public/Private Tokens from RSA to HMAC - CVE-2022-23541
  • security: fixes Unrestricted key type could lead to legacy keys usage - CVE-2022-23539
Commits
Maintainer changes

This version was pushed to npm by charlesrea, a new releaser for jsonwebtoken since your current version.


Updates danger from 10.9.0 to 12.3.4

Release notes

Sourced from danger's releases.

Release 12.3.4

No release notes provided.

Release 12.3.3

No release notes provided.

Release 12.3.2

No release notes provided.

Release 12.3.1

No release notes provided.

Release 12.3.0

No release notes provided.

Release 12.2.1

No release notes provided.

Release 12.2.0

No release notes provided.

Release 12.1.0

It's been 7 years since I looked at danger init and err, the world of CI has changed quite a bit since then. So, Danger JS's init command now knows that GitHub Actions exists and will correctly offer some advice on how to set up a Dangerfile for it. - [@​orta]


12.0.1

Bumping to 12.x because we've raised the minimum to node version from 14 to 18. This is due to some of our dependencies requiring a newer version of node. This is a breaking change for some folk! Also, 14 has been out of support for quite a while now and Node 18 gives us a full year. - [@​orta]

  • Remove the user checks in GitHub comment/inline comment lookups, to allow using app tokens #1433 - [@​orta]
  • Upgrade node engine from >=14.13.1 to >=18 [@​heltoft]
  • Upgrade @types/node from ^10.11.3 to 18.19.18 [@​heltoft]
  • GitLab: #1386 Move from @gitbeaker/node to @gitbeaker/rest [@​heltoft]
  • GitLab: #1412 Danger fails to create inline comments on Gitlab [@​heltoft]
  • GitLab: #1405 Can't post multiple inline comments [@​heltoft]
  • GitLab: Do not delete system resolved danger inline comments [@​heltoft]
  • Fix for ESM imports in Dangerfiles [@​mgol]

Release 12.0.1

Bumping to 12.x because we've raised the minimum to node version from 14 to 18. This is due to some of our dependencies requiring a newer version of node. This is a breaking change for some folk! Also, 14 has been out of support for quite a while now and Node 18 gives us a full year. - [@​orta]

  • Remove the user checks in GitHub comment/inline comment lookups, to allow using app tokens #1433 - [@​orta]
  • Upgrade node engine from >=14.13.1 to >=18 [@​heltoft]
  • Upgrade @types/node from ^10.11.3 to 18.19.18 [@​heltoft]

... (truncated)

Changelog

Sourced from danger's changelog.

12.3.4

  • Ensure that babel ignores do not cause the transpiler to fall over, by supporting the null return from loadOptions which occurs when a file is ignored.
  • Allow absolute paths for a Dangerfile

12.3.3

  • #1180 Set module properly when tsconfig does not contain compilerOptions.module [@​matthewh]

12.3.2

  • #1180 Adds support for ESM Dangerfiles (by using dangerfile.mts/dangerfile.mjs) [@​matthewh]

12.3.1

  • Fixes for created, modified and deleted files in GitHub - [@​szweier]
  • Dont log about github.pr not being available in pull_request_target - [@​sayali10]

12.3.0

  • Dockerfile changes - [@​glensc]
  • Use node 18 for pre-built versions of danger (used by Danger Swift / Kotlin et al) - [@​heltoft]

12.2.0

  • Adds a log when you run on GitHub Actions without being a pull_request - [@​orta]
  • GitHub: Move to 'List pull request files' API with pagination support [@​fabianehlert]

12.1.0

It's been 7 years since I looked at danger init and err, the world of CI has changed quite a bit since then. So, Danger JS's init command now knows that GitHub Actions exists and will correctly offer some advice on how to set up a Dangerfile for it. - [@​orta]

12.0.0

Bumping to 12.x because we've raised the minimum to node version from 14 to 18. This is due to some of our dependencies requiring a newer version of node. This is a breaking change for some folk! Also, 14 has been out of support for quite a while now and Node 18 gives us a full year. - [@​orta]

  • Remove the user checks in GitHub comment/inline comment lookups, to allow using app tokens #1433 - [@​orta]
  • Upgrade node engine from >=14.13.1 to >=18 [@​heltoft]
  • Upgrade @types/node from ^10.11.3 to 18.19.18 [@​heltoft]
  • GitLab: #1386 Move from @gitbeaker/node to @gitbeaker/rest [@​heltoft]
  • GitLab: #1412 Danger fails to create inline comments on Gitlab [@​heltoft]
  • GitLab: #1405 Can't post multiple inline comments [@​heltyarnoft]
  • GitLab: Do not delete system resolved danger inline comments [@​heltoft]
  • Fix for ESM imports in Dangerfiles [@​mgol]

11.3.1

... (truncated)

Commits
  • 1cdf428 Release 12.3.4
  • 91d5dcf Prepare for release
  • 3e36bde Merge pull request #1476 from TomStrepsil/support_babel_ignores
  • c9cce8d restore es6 object format (did the lint change this??)
  • feebb91 lint
  • 89e6d3e revert update of package version, assumed this will be resolved during releas...
  • 3f3aee7 empty commit to re-start ci
  • 3f5a377 cater for unexpected linting in ci?
  • 6b54378 support files ignored by babel
  • b07053c Merge pull request #1475 from buffcode/patch-1
  • Additional commits viewable in compare view

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @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.

Bumps [jsonwebtoken](https://github.com/auth0/node-jsonwebtoken) to 9.0.2 and updates ancestor dependency [danger](https://github.com/danger/danger-js). These dependencies need to be updated together.


Updates `jsonwebtoken` from 8.5.1 to 9.0.2
- [Changelog](https://github.com/auth0/node-jsonwebtoken/blob/master/CHANGELOG.md)
- [Commits](auth0/node-jsonwebtoken@v8.5.1...v9.0.2)

Updates `danger` from 10.9.0 to 12.3.4
- [Release notes](https://github.com/danger/danger-js/releases)
- [Changelog](https://github.com/danger/danger-js/blob/main/CHANGELOG.md)
- [Commits](danger/danger-js@10.9.0...12.3.4)

---
updated-dependencies:
- dependency-name: jsonwebtoken
  dependency-type: indirect
- dependency-name: danger
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Feb 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants