Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: golang-jwt/jwt
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v5.2.2
Choose a base ref
...
head repository: golang-jwt/jwt
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v5.3.0
Choose a head ref
  • 7 commits
  • 38 files changed
  • 5 contributors

Commits on Mar 31, 2025

  1. Configuration menu
    Copy the full SHA
    12384ea View commit details
    Browse the repository at this point in the history

Commits on Apr 9, 2025

  1. 1 Configuration menu
    Copy the full SHA
    497a38e View commit details
    Browse the repository at this point in the history

Commits on May 6, 2025

  1. Bump golangci/golangci-lint-action from 7 to 8 (#440)

    Bumps [golangci/golangci-lint-action](https://github.com/golangci/golangci-lint-action) from 7 to 8.
    - [Release notes](https://github.com/golangci/golangci-lint-action/releases)
    - [Commits](golangci/golangci-lint-action@v7...v8)
    
    ---
    updated-dependencies:
    - dependency-name: golangci/golangci-lint-action
      dependency-version: '8'
      dependency-type: direct:production
      update-type: version-update:semver-major
    ...
    
    Signed-off-by: dependabot[bot] <[email protected]>
    Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
    dependabot[bot] authored May 6, 2025
    Configuration menu
    Copy the full SHA
    048854f View commit details
    Browse the repository at this point in the history

Commits on Jun 12, 2025

  1. replaced interface{} to any (#445)

    * replaced interface{} to any in KeyFunc
    
    * replaced interface{} to its alias any
    
    * updated comments and MIGRATION_GUIDE.md file
    
    * replaced []any to []interface{} in test name because it is not a comment
    aachex authored Jun 12, 2025
    Configuration menu
    Copy the full SHA
    75740f1 View commit details
    Browse the repository at this point in the history

Commits on Jul 1, 2025

  1. Fix bug in validation of multiple audiences (#441)

    * Fix bug in validation of multiple audiences
    
    In a situation where multiple audiences are validated by the
    validator, the order of evaluation of the for-range loop
    affects the result.
    
    If we produce matches such as:
    
    ```
    {
      "example.org": true,
      "example.com": false,
    }
    ```
    
    and we configured the validator to expect a single match on
    audience, the code would either:
    
    1. produce "token has invalid audience" if "example.org" was
    evaluated first
    
    2. produce a passing result if "example.com" was evaluated first
    
    This commit fixes this bug, and adds a suite of tests as well
    as regression tests to prevent this issue in future.
    
    * Adding three more test cases to be sure
    
    * Removing required alltogether form verifyAudience
    
    * Removing required
    
    ---------
    
    Co-authored-by: Christian Banse <[email protected]>
    sfinnman-cotn and oxisto authored Jul 1, 2025
    Configuration menu
    Copy the full SHA
    d83e545 View commit details
    Browse the repository at this point in the history

Commits on Jul 16, 2025

  1. Create CODEOWNERS (#449)

    Should finally tag @oxisto and @mfridman automatically to PRs.
    oxisto authored Jul 16, 2025
    Configuration menu
    Copy the full SHA
    3839817 View commit details
    Browse the repository at this point in the history

Commits on Jul 30, 2025

  1. Bump Go version to indicate correct minimum requirement (#452)

    * Bump Go version to indicate correct minimum requirement
    
    The minimum requirement that we have was silently bumped to 1.21 in #441 because of the `slices` package. It seems that we did not update the `go.mod` when we updated our CI range, because CI did not fail because it was not testing older versions.
    
    We probably should just update the `go.mod` when we update the CI target in the future? Although we could theoretically stay at 1.21 in terms of the code base.
    
    * Removed outdated build tags
    
    * Remove more build tags
    
    * Removed code for Go < 1.20
    oxisto authored Jul 30, 2025
    Configuration menu
    Copy the full SHA
    e9547a1 View commit details
    Browse the repository at this point in the history
Loading