Skip to content

chore(deps): bump github.com/go-jose/go-jose/v4 from 4.1.3 to 4.1.4#263

Open
dependabot[bot] wants to merge 1 commit intomasterfrom
dependabot/go_modules/github.com/go-jose/go-jose/v4-4.1.4
Open

chore(deps): bump github.com/go-jose/go-jose/v4 from 4.1.3 to 4.1.4#263
dependabot[bot] wants to merge 1 commit intomasterfrom
dependabot/go_modules/github.com/go-jose/go-jose/v4-4.1.4

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot bot commented on behalf of github Apr 3, 2026

Bumps github.com/go-jose/go-jose/v4 from 4.1.3 to 4.1.4.

Commits

Dependabot compatibility score

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 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 [github.com/go-jose/go-jose/v4](https://github.com/go-jose/go-jose) from 4.1.3 to 4.1.4.
- [Release notes](https://github.com/go-jose/go-jose/releases)
- [Commits](go-jose/go-jose@v4.1.3...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>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file go Pull requests that update Go code labels Apr 3, 2026
@dependabot dependabot bot requested a review from a team as a code owner April 3, 2026 04:14
@dependabot dependabot bot added dependencies Pull requests that update a dependency file go Pull requests that update Go code labels Apr 3, 2026
@codacybeta codacybeta enabled auto-merge (squash) April 3, 2026 04:14
@codacy-production
Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 duplication

Metric Results
Duplication 0

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

Run reviewer

TIP This summary will be updated as you push new changes. Give us feedback

Copy link
Copy Markdown

@codacy-production codacy-production bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This pull request updates the github.com/go-jose/go-jose/v4 dependency from 4.1.3 to 4.1.4. While the change to go.mod is correct and Codacy quality checks are passing, the implementation is currently incomplete.

The update lacks a corresponding change to the go.sum file. This omission prevents the verification of dependency checksums and risks breaking reproducible builds. This should be addressed by running 'go mod tidy' to ensure the lock file is synchronized with the module changes.

About this PR

  • The PR only includes changes to 'go.mod'. Typically, a Go dependency update should also include changes to 'go.sum' to lock the specific version hash and ensure build integrity. Please run 'go mod tidy' and include the updated go.sum in this PR.

Test suggestions

  • Verify that the project compiles and existing functionality remains intact with the new version of the library.
Prompt proposal for missing tests
Consider implementing these tests if applicable:
1. Verify that the project compiles and existing functionality remains intact with the new version of the library.

🗒️ Improve review quality by adding custom instructions

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 go Pull requests that update Go code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant