build(deps): bump github.com/go-jose/go-jose/v4 from 4.0.2 to 4.1.4#22
build(deps): bump github.com/go-jose/go-jose/v4 from 4.0.2 to 4.1.4#22dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
Bumps [github.com/go-jose/go-jose/v4](https://github.com/go-jose/go-jose) from 4.0.2 to 4.1.4. - [Release notes](https://github.com/go-jose/go-jose/releases) - [Commits](go-jose/go-jose@v4.0.2...v4.1.4) --- updated-dependencies: - dependency-name: github.com/go-jose/go-jose/v4 dependency-version: 4.1.4 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
| go 1.23.1 | ||
|
|
||
| toolchain go1.23.3 | ||
| go 1.24.0 |
There was a problem hiding this comment.
Go version mismatch between go.mod and CI workflows
High Severity
The go.mod minimum Go version was bumped from 1.23.1 to 1.24.0 (required by go-jose/go-jose/v4 v4.1.3+ which dropped Go 1.23 support), but all CI workflow files (.github/workflows/lint.yml, smoke.yml, codeql-analysis.yml, performance.yml, release.yml) still specify go-version: "1.23" in their actions/setup-go steps. This mismatch means CI will either fail or silently auto-download a different Go toolchain than configured, depending on GOTOOLCHAIN settings.


Bumps github.com/go-jose/go-jose/v4 from 4.0.2 to 4.1.4.
Release notes
Sourced from github.com/go-jose/go-jose/v4's releases.
... (truncated)
Commits
0e59876Merge commit from forkddffdbcBump actions/checkout from 5 to 6 (#213)5348b9aReject JWS with an unprotected critical b64 header (#210)9153a5eBump actions/setup-python from 5 to 6 (#208)2126e17Bump actions/setup-go from 5 to 6 (#209)9860c65Bump actions/checkout from 4 to 5 (#206)14239fdRemove Go 1.23 support (#205)a16e158Update CI to run on Go 1.24 and 1.25 (#204)a1565a4testutils/assert: remove True, Nil, NotNil (#202)3a80e13jwe: accept non-pointer JSONWebKey in Recipient (#200)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.