Skip to content
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

Updated to Fastify v4 #227

Merged
merged 1 commit into from
May 10, 2022
Merged

Updated to Fastify v4 #227

merged 1 commit into from
May 10, 2022

Conversation

mcollina
Copy link
Member

@mcollina mcollina commented May 9, 2022

Checklist

@@ -501,6 +501,6 @@ function fastifyJwt (fastify, options, next) {
}

module.exports = fp(fastifyJwt, {
fastify: '>=3.0.0',
name: 'fastify-jwt'
fastify: '4.x',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

does it mean we don't support v3.x?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is it better to use ^3.0.0 | ^4.0.0-2?

Copy link
Member

@climba03003 climba03003 May 10, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

does it mean we don't support v3.x?

No, we can backport the feature or fix to old version branch. That's for fastify@3.

is it better to use ^3.0.0 | ^4.0.0-2?

No, it means we need to duplicate the CI and increase maintenance difficulty

@mcollina mcollina merged commit 9c7d970 into master May 10, 2022
@Fdawgs Fdawgs deleted the update-to-fastify-v4 branch May 11, 2022 05:01
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.

4 participants