Skip to content

chore(deps): upgrade aws-jwt-verify 5.1.0 to 5.1.1#142

Merged
dtoxvanilla1991 merged 2 commits into
mainfrom
fix/upgrade/aws-jwt-verify-5.1.1
Apr 30, 2026
Merged

chore(deps): upgrade aws-jwt-verify 5.1.0 to 5.1.1#142
dtoxvanilla1991 merged 2 commits into
mainfrom
fix/upgrade/aws-jwt-verify-5.1.1

Conversation

@dtoxvanilla1991

Copy link
Copy Markdown
Contributor

Summary

Clean replacement for #119 (which has merge conflicts against the current main).

Upgrades aws-jwt-verify from 5.1.0 to 5.1.1 (patch bump). Runtime dependency.
No migration required. All 51 tests pass.


Is this a breaking change?

No. This is a patch release. All changes are additive or internal:

  • feat: support GovCloud ALB ARNs in AlbJwtVerifier — new additive feature, nothing removed or changed
  • fix: UI test works again after Cypress upgrade — internal test fix
  • docs: tweak ALB docs
  • chore: bump form-data in internal test fixtures (security fix in the library's own test suite, not runtime code)

Changes

  • package.json: specifier updated ^5.0.0^5.1.1 (pnpm update also bumped the lower bound to the resolved version)
  • pnpm-lock.yaml: lockfile updated — aws-jwt-verify resolves to 5.1.1

Supersedes: #119

Patch bump of aws-jwt-verify (runtime dependency).

Changes in 5.1.1:
- feat: support GovCloud ALB ARNs in AlbJwtVerifier (additive)
- fix: ui test works again after cypress upgrade (internal tests)
- docs: tweak ALB docs
- Bump form-data in internal tests (security fix in test fixtures)

No breaking changes. No migration required. All 51 tests pass.

Supersedes #119 (renovate PR had merge conflicts against current main).
@dtoxvanilla1991 dtoxvanilla1991 requested a review from a team as a code owner April 27, 2026 23:17
@coderabbitai

coderabbitai Bot commented Apr 27, 2026

Copy link
Copy Markdown
Contributor

Warning

Rate limit exceeded

@dtoxvanilla1991 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 49 minutes and 7 seconds before requesting another review.

To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 00e92d55-b584-4ad5-9b0a-b3515fbda9d8

📥 Commits

Reviewing files that changed from the base of the PR and between 4641089 and 5d3673f.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (1)
  • package.json
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/upgrade/aws-jwt-verify-5.1.1

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
Review rate limit: 0/1 reviews remaining, refill in 49 minutes and 7 seconds.

Comment @coderabbitai help to get the list of available commands and usage tips.

@dtoxvanilla1991 dtoxvanilla1991 self-assigned this Apr 27, 2026
@dtoxvanilla1991 dtoxvanilla1991 merged commit b7ac053 into main Apr 30, 2026
4 checks passed
@dtoxvanilla1991 dtoxvanilla1991 deleted the fix/upgrade/aws-jwt-verify-5.1.1 branch April 30, 2026 22:44
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.

2 participants