Skip to content

fix: remove jwt key validation to allow new api keys #212

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.

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

Merged
merged 2 commits into from
Jun 20, 2025

Conversation

silentworks
Copy link
Collaborator

What kind of change does this PR introduce?

Bug fix, feature, docs update, ...

What is the current behavior?

Please link any relevant issues here.

What is the new behavior?

Feel free to include screenshots if it includes visual changes.

Additional context

Add any other context or screenshots.

@silentworks silentworks requested a review from grdsdev June 20, 2025 22:20
@coveralls
Copy link

Pull Request Test Coverage Report for Build 15788796593

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage decreased (-0.1%) to 98.077%

Totals Coverage Status
Change from base Build 15763562986: -0.1%
Covered Lines: 204
Relevant Lines: 208

💛 - Coveralls

@silentworks silentworks merged commit 5b852e4 into main Jun 20, 2025
12 checks passed
@silentworks silentworks deleted the silentworks/remove-valid-jwt-check branch June 20, 2025 22:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants