fix(deps): update dependency @fastify/jwt to v8 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@fastify/jwt	7.2.4 -> 8.0.1

---

Release Notes

fastify/fastify-jwt (@​fastify/jwt)

v8.0.1

Compare Source

What's Changed

• Node 22 no longer logging an unsupported version warning
• docs(readme): fix broken links (https://github.com/fastify/fastify-jwt/pull/326)
• chore(.gitignore): add .tap/ dir (https://github.com/fastify/fastify-jwt/pull/327)
• build(deps): bump fast-jwt from 3.3.3 to 4.0.0 (https://github.com/fastify/fastify-jwt/pull/330)
• build(deps-dev): bump tsd from 0.30.7 to 0.31.0 (https://github.com/fastify/fastify-jwt/pull/333)

Full Changelog: fastify/fastify-jwt@v8.0.0...v8.0.1

v8.0.0

Compare Source

What's Changed

• test: use t.error by @​Uzlopak in https://github.com/fastify/fastify-jwt/pull/322
• build(deps-dev): bump tsd from 0.29.0 to 0.30.0 by @​dependabot in https://github.com/fastify/fastify-jwt/pull/320
• docs(readme): add missing extractToken option by @​dancastillo in https://github.com/fastify/fastify-jwt/pull/324
• Ignore authorization headers if not Bearer by @​cberescu in https://github.com/fastify/fastify-jwt/pull/325

Full Changelog: fastify/fastify-jwt@v7.2.4...v8.0.0

---

Configuration

📅 Schedule: Branch creation - "before 4am on monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

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

[wkillerud]

Ignore authorization headers if not Bearer

Our CLI uses the Bearer format for Authorization, as do all our tests and docs. Would this still be considered a breaking change for @eik/service? What do you think?

Similar questions for the other Fastify plugins we use that have majors.

[digitalsadhu]

Ignore authorization headers if not Bearer

Our CLI uses the Bearer format for Authorization, as do all our tests and docs. Would this still be considered a breaking change for @eik/service? What do you think?

Similar questions for the other Fastify plugins we use that have majors.

Sound like it shouldn't be...