Bump firebase/php-jwt from 6.4.0 to 7.0.0#135
Merged
github-management-service merged 1 commit intomasterfrom Feb 18, 2026
Merged
Bump firebase/php-jwt from 6.4.0 to 7.0.0#135github-management-service merged 1 commit intomasterfrom
github-management-service merged 1 commit intomasterfrom
Conversation
Bumps [firebase/php-jwt](https://github.com/firebase/php-jwt) from 6.4.0 to 7.0.0. - [Release notes](https://github.com/firebase/php-jwt/releases) - [Changelog](https://github.com/firebase/php-jwt/blob/main/CHANGELOG.md) - [Commits](firebase/php-jwt@v6.4.0...v7.0.0) --- updated-dependencies: - dependency-name: firebase/php-jwt dependency-version: 7.0.0 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
dependencies
|
It looks like you are reviewing a Dependabot upgrade PR! 🛠️ We aim to merge Dependabot PRs within the below timeframes. The objectives are based on the severity of the security vulnerability we are mitigating with the upgrade:
🎯 Target merge date for this PR: 04/03/2026 🎯 FAQ What if we aren’t vulnerable to this particular CVE? Do we still have to upgrade the package?It’s still a good idea to upgrade the package if we can. With new code patterns and paths being introduced every day, we have no guarantee that we won’t later make ourselves vulnerable. Keeping packages up to date as a matter of due course is also good hygiene.What if we’re not vulnerable and upgrading is going to be a lot of work?In these cases it’s a good idea to list out the steps you took to confirm we are not vulnerable in this PR. The PR can then be closed and the corresponding Dependabot Alert should be dismissed with the triage steps included as a comment. Please get in touch with Team Application Security via #ask-security before dismissing anyCRITICAL alerts.
This is a major version upgrade that requires substantial code refactoring. What should I do?If the upgrade requires substantial refactoring then it is possible that we will miss the objectives we have outlined above. In these cases, you should add thedependabot-refactor-required label to this PR and ping #ask-security for further advice.
|
github-management-service
approved these changes
Feb 18, 2026
github-management-service
deleted the
dependabot/composer/firebase/php-jwt-7.0.0
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 firebase/php-jwt from 6.4.0 to 7.0.0.
Release notes
Sourced from firebase/php-jwt's releases.
... (truncated)
Changelog
Sourced from firebase/php-jwt's changelog.
... (truncated)
Commits
c03036fchore(main): release 7.0.0 (#614)6b80341feat: add key size validation (#613)a3edb39chore: update release-please secret (#608)f174826feat: store timestamp inExpiredException(#604)4dbfac0feat: add SensitiveParameter attribute to security-critical parameters (#603)223d1b3chore: move release please from app to github action (#606)953b2c8fix: validate iat and nbf on payload (#568)43d70aefix: use DateTime::ATOM instead of ISO8601 in exception messaged1e91ecchore(main): release 6.11.1 (#597)c11113afix: update error text for consistency (#528)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 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)You can disable automated security fix PRs for this repo from the Security Alerts page.