Skip to content

build(gomod): ⚡ major gomod (major) #193

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.

Sign up for GitHub

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

Jump to bottom
Open
renovate wants to merge 1 commit into
base: main
Choose a base branch
from
Open

build(gomod): ⚡ major gomod (major) #193

renovate wants to merge 1 commit into from

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented May 6, 2025 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
github.com/caarlos0/env/v6 v6.10.1 → v11.3.1 age adoption passing confidence
github.com/golang-jwt/jwt/v4 v4.5.2 → v5.3.0 age adoption passing confidence
github.com/posener/complete v1.2.3 → v2.1.0 age adoption passing confidence

Release Notes

caarlos0/env (github.com/caarlos0/env/v6)

v11.3.1

Compare Source

Changelog

Bug fixes
Other work

Released with GoReleaser Pro!

v11.3.0

Compare Source

Changelog

New Features
Bug fixes
Documentation updates
Other work

Released with GoReleaser Pro!

v11.2.2

Compare Source

Changelog

Documentation updates

Released with GoReleaser Pro!

v11.2.1

Compare Source

Changelog

Bug fixes
Documentation updates

Released with GoReleaser Pro!

v11.2.0

Compare Source

Changelog

New Features
Documentation updates

Released with GoReleaser Pro!

v11.1.0

Compare Source

Changelog

Bug fixes
Other work

Released with GoReleaser Pro!

v11.0.1

Compare Source

Changelog

Bug fixes
Documentation updates

Released with GoReleaser Pro!

v11.0.0

Compare Source

Changelog

Breaking changes
  • Updated module's Go version to 1.18
New Features
Bug fixes
Documentation updates
Other work

Released with GoReleaser Pro!

v10.0.0

Compare Source

Changelog

Breaking changes
New Features
Documentation updates
Other work

Released with GoReleaser Pro!

v9.0.0

Compare Source

Changelog

New Features
Bug fixes
Documentation updates

Migrating from v8

Replace envExpand:"true" with ,expand, e.g.:

type Foo struct {
    Foo string `env:"FOO,expand"`
}

Released with GoReleaser Pro!

v8.0.0

Compare Source

Changelog

Other work

Updating from v7

  • if you use env.Parse with no options, no change is required.
  • if you use env.Parse with one Options{}, call env.ParseWithOptions instead.
  • if you use env.Parse with options, and pass more than one Options{}, merge them into a single one, and use env.ParseWithOptions instead.
  • if you use env.ParseWithFuncs, use env.ParseWithOptions instead, and put your parsers into Options{ FuncMap: <here> }.

Released with GoReleaser Pro!

v7.1.0

Compare Source

Changelog

New Features
Bug fixes
Documentation updates

Released with GoReleaser Pro!

v7.0.0

Compare Source

Changelog

Breaking changes
Documentation updates
Other work

Released with GoReleaser Pro!

golang-jwt/jwt (github.com/golang-jwt/jwt/v4)

v5.3.0

Compare Source

This release is almost identical to to v5.2.3 but now correctly indicates Go 1.21 as minimum requirement.

What's Changed

Full Changelog: golang-jwt/jwt@v5.2.3...v5.3.0

v5.2.3

Compare Source

What's Changed

New Contributors

Full Changelog: golang-jwt/jwt@v5.2.2...v5.2.3

v5.2.2

Compare Source

What's Changed

New Contributors

Full Changelog: golang-jwt/jwt@v5.2.1...v5.2.2

v5.2.1

Compare Source

What's Changed

New Contributors

Full Changelog: golang-jwt/jwt@v5.2.0...v5.2.1

v5.2.0

Compare Source

What's Changed

New Contributors

Full Changelog: golang-jwt/jwt@v5.1.0...v5.2.0

v5.1.0

Compare Source

What's Changed

New Contributors

Full Changelog: golang-jwt/jwt@v5.0.0...v5.1.0

v5.0.0

Compare Source

🚀 New Major Version v5 🚀

It's finally here, the release you have been waiting for! We don't take breaking changes lightly, but the changes outlined below were necessary to address some of the challenges of the previous API. A big thanks for @​mfridman for all the reviews, all contributors for their commits and of course @​dgrijalva for the original code. I hope we kept some of the spirit of your original v4 branch alive in the approach we have taken here.
~@​oxisto, on behalf of @​golang-jwt/maintainers

Version v5 contains a major rework of core functionalities in the jwt-go library. This includes support for several validation options as well as a re-design of the Claims interface. Lastly, we reworked how errors work under the hood, which should provide a better overall developer experience.

Starting from v5.0.0, the import path will be:

"github.com/golang-jwt/jwt/v5"

For most users, changing the import path should suffice. However, since we intentionally changed and cleaned some of the public API, existing programs might need to be updated. The following sections describe significant changes and corresponding updates for existing programs.

Parsing and Validation Options

Under the hood, a new validator struct takes care of validating the claims. A long awaited feature has been the option to fine-tune the validation of tokens. This is now possible with several ParserOption functions that can be appended to most Parse functions, such as ParseWithClaims. The most important options and changes are:

  • Added WithLeeway to support specifying the leeway that is allowed when validating time-based claims, such as exp or nbf.
  • Changed default behavior to not check the iat claim. Usage of this claim is OPTIONAL according to the JWT RFC. The claim itself is also purely informational according to the RFC, so a strict validation failure is not recommended. If you want to check for sensible values in these claims, please use the WithIssuedAt parser option.
  • Added WithAudience, WithSubject and WithIssuer to support checking for expected aud, sub and iss.
  • Added WithStrictDecoding and WithPaddingAllowed options to allow previously global settings to enable base64 strict encoding and the parsing of base64 strings with padding. The latter is strictly speaking against the standard, but unfortunately some of the major identity providers issue some of these incorrect tokens. Both options are disabled by default.

Changes to the Claims interface

Complete Restructuring

Previously, the claims interface was satisfied with an implementation of a Valid() error function. This had several issues:

  • The different claim types (struct claims, map claims, etc.) then contained similar (but not 100 % identical) code of how this validation was done. This lead to a lot of (almost) duplicate code and was hard to maintain
  • It was not really semantically close to what a "claim" (or a set of claims) really is; which is a list of defined key/value pairs with a certain semantic meaning.

Since all the validation functionality is now extracted into the validator, all VerifyXXX and Valid functions have been removed from the Claims interface. Instead, the interface now represents a list of getters to retrieve values with a specific meaning. This allows us to completely decouple the validation logic with the underlying storage representation of the claim, which could be a struct, a map or even something stored in a database.

type Claims interface {
	GetExpirationTime() (*NumericDate, error)
	GetIssuedAt() (*NumericDate, error)
	GetNotBefore() (*NumericDate, error)
	GetIssuer() (string, error)
	GetSubject() (string, error)
	GetAudience() (ClaimStrings, error)
}
Supported Claim Types and Removal of StandardClaims

The two standard claim types supported by this library, MapClaims and RegisteredClaims both implement the necessary functions of this interface. The old StandardClaims struct, which has already been deprecated in v4 is now removed.

Users using custom claims, in most cases, will not experience any changes in the behavior as long as they embedded RegisteredClaims. If they created a new claim type from scratch, they now need to implemented the proper getter functions.

Migrating Application Specific Logic of the old Valid

Previously, users could override the Valid method in a custom claim, for example to extend the validation with application-specific claims. However, this was always very dangerous, since once could easily disable the standard validation and signature checking.

In order to avoid that, while still supporting the use-case, a new ClaimsValidator interface has been introduced. This interface consists of the Validate() error function. If the validator sees, that a Claims struct implements this interface, the errors returned to the Validate function will be appended to the regular standard validation. It is not possible to disable the standard validation anymore (even only by accident).

Usage examples can be found in example_test.go, to build claims structs like the following.

// MyCustomClaims includes all registered claims, plus Foo.
type MyCustomClaims struct {
	Foo string `json:"foo"`
	jwt.RegisteredClaims
}

// Validate can be used to execute additional application-specific claims
// validation.
func (m MyCustomClaims) Validate() error {
	if m.Foo != "bar" {
		return errors.New("must be foobar")
	}

	return nil
}

Changes to the Token and Parser struct

The previously global functions DecodeSegment and EncodeSegment were moved to the Parser and Token struct respectively. This will allow us in the future to configure the behavior of these two based on options supplied on the parser or the token (creation). This also removes two previously global variables and moves them to parser options WithStrictDecoding and WithPaddingAllowed.

In order to do that, we had to adjust the way signing methods work. Previously they were given a base64 encoded signature in Verify and were expected to return a base64 encoded version of the signature in Sign, both as a string. However, this made it necessary to have DecodeSegment and EncodeSegment global and was a less than perfect design because we were repeating encoding/decoding steps for all signing methods. Now, Sign and Verify operate on a decoded signature as a []byte, which feels more natural for a cryptographic operation anyway. Lastly, Parse and SignedString take care of the final encoding/decoding part.

In addition to that, we also changed the Signature field on Token from a string to []byte and this is also now populated with the decoded form. This is also more consistent, because the other parts of the JWT, mainly Header and Claims were already stored in decoded form in Token. Only the signature was stored in base64 encoded form, which was redundant with the information in the Raw field, which contains the complete token as base64.

type Token struct {
	Raw       string                 // Raw contains the raw token
	Method    SigningMethod          // Method is the signing method used or to be used
	Header    map[string]interface{} // Header is the first segment of the token in decoded form
	Claims    Claims                 // Claims is the second segment of the token in decoded form
	Signature []byte                 // Signature is the third segment of the token in decoded form
	Valid     bool                   // Valid specifies if the token is valid
}

Most (if not all) of these changes should not impact the normal usage of this library. Only users directly accessing the Signature field as well as developers of custom signing methods should be affected.

What's Changed

New Contributors

Full Changelog: golang-jwt/jwt@v4.5.0...v5.0.0

posener/complete (github.com/posener/complete)

v2.1.0: Switch to Go 1.20 errors package

Compare Source

v2.0.0

Compare Source

Configuration

📅 Schedule: Branch creation - "after 10pm,before 3am" in timezone America/Chicago, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from a team as a code owner May 6, 2025 20:43
@renovate renovate bot added the dependencies label May 6, 2025
@renovate renovate bot requested a review from pacificcode May 6, 2025 20:43
@renovate
Copy link
Contributor Author

renovate bot commented May 6, 2025 •
edited
Loading

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: go.sum
Command failed: mod upgrade --mod-name=github.com/caarlos0/env/v6 -t=11
could not load package: err: exit status 1: stderr: go: inconsistent vendoring in /tmp/renovate/repos/github/DelineaXPM/dsv-cli:
	github.com/caarlos0/env/v11@v11.3.1: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
	github.com/golang-jwt/jwt/v4@v4.5.0: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
	github.com/golang-jwt/jwt/v5@v5.3.0: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
	github.com/posener/complete@v1.1.1: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
	github.com/posener/complete/v2@v2.1.0: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
	github.com/golang-jwt/jwt/v4@v4.5.2: is marked as explicit in vendor/modules.txt, but not explicitly required in go.mod
	github.com/posener/complete@v1.2.3: is marked as explicit in vendor/modules.txt, but not explicitly required in go.mod

	To ignore the vendor directory, use -mod=readonly or -mod=mod.
	To sync the vendor directory, run:
		go mod vendor

@renovate renovate bot enabled auto-merge (squash) May 6, 2025 20:43
@snyk-io
Copy link

snyk-io bot commented May 7, 2025 •
edited
Loading

⚠️ Snyk checks are incomplete. No issues have been found so far.

⚠️ security/snyk check encountered an error. (View Details)

⚠️ license/snyk check encountered an error. (View Details)

✅ code/snyk check is complete. No issues have been found. (View Details)

@renovate renovate bot force-pushed the renovate/major-gomod branch 3 times, most recently from 70a7cbd to c95fde4 Compare May 7, 2025 12:07
@renovate renovate bot force-pushed the renovate/major-gomod branch from c95fde4 to d4faf89 Compare June 4, 2025 15:56
@renovate renovate bot force-pushed the renovate/major-gomod branch from d4faf89 to 25d851d Compare July 15, 2025 15:28
@renovate renovate bot force-pushed the renovate/major-gomod branch from 25d851d to 6f5a117 Compare July 30, 2025 16:57
@renovate renovate bot force-pushed the renovate/major-gomod branch from 6f5a117 to 9716ff8 Compare September 22, 2025 08:54
@renovate renovate bot force-pushed the renovate/major-gomod branch from 9716ff8 to cbb15a4 Compare September 22, 2025 13:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@renovate-approve renovate-approve[bot] renovate-approve[bot] approved these changes

@pacificcode pacificcode Awaiting requested review from pacificcode pacificcode is a code owner automatically assigned from DelineaXPM/dsv-contributors

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

dependencies

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants