1.0.0 #330
Baroshem
announced in
Announcements
1.0.0
#330
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
1.0.0 🎉
After five release candidate versions, we are now ready to present you a stable 1.0.0 release of NuxtSecurity. We have spent a lot of time trying to stabilise the API while constantly improving the security by implementing features like:
From this point I would like to thank @vejja who did an amazing work delivering a lot of functionalities mentioned both above and below. You are a magician! 🚀
And also, huge kudos to all contributors 🎉
✅ Migration Guide (0.14.X -> 1.0.0)
We have tried our best not to include significant breaking changes in the recent stable 1.0.0 version but some changes were necessary to improve quality of the module. Don't worry, we have prepared a migration guide with all the changes and how you should approach when migrating your current application to be up to date with 1.0.0 :)
1. Modifed the structure for
alllowedMethodsRestricter
In the previous version,
alllowedMethodsRestricter
was an array of HTTP methods or'*'
for all methods.Now it is configured like following:
This change allows to pass a
throwError
property that can be useful to return an error response rather than throwing a default Nuxt error.2. Changed the disabled value for
permissionsPolicy
In the previous version, if you wanted to disable certain API like camera you would do something like this:
Now it is configured like following:
This change allows to fix an issue of passing several directives mentioned in #194
3. Changed the type of
interval
inrateLimiter
In the previous version, if you wanted to set the interval for your rateLimiter you would do something like this:
Now it is configured like following:
This change was required to migrate to an updated rateLimiter that supports modern examples.
4. Nonce value
In the previous version,
nonce
could be either an object with a typeNonceOptions
orfalse
.Now it is only a boolean value:
This change was necessary to resolve security vulnerability for nonce reported by vejja #257. Read more about the new usage of nonce in this module https://nuxt-security.vercel.app/documentation/headers/csp#nonce
5. Strict Content Security Policy by default
In this version, we have updated ContentSecurityConfiguration by a mile, specifically we have enabled strict CSP by default to spread good security practices.
If you are experiencing some issues with CSP, check out the new documentation about it:
🍾 New features
This PR introduces per-route configuration of security headers, via
🗞️ Next steps
This is the last release candidate version. In the next weeks we are planning to release stable 1.0.0 version :)
👉 Changelog
compare changes
🚀 Enhancements
credentialless
value toCross-Origin-Embedder-Policy
header🩹 Fixes
upgrade-insecure-requests
cannot be turned off for static build #214)nonce
(fix: remove broken test fornonce
#213)nonce
option is set totrue
📖 Documentation
interval
property🏡 Chore
🤖 CI
❤️ Contributors
What's Changed
nonce
by @trijpstra-fourlights in fix: remove broken test fornonce
#213nonce
docs aboutunsafe-inline
during development by @trijpstra-fourlights in chore: updatenonce
docs aboutunsafe-inline
during development #240false
by @dargmuesli in fix(headers): allow csp value to befalse
#286false
withboolean
by @Mohamed-Kaizen in fix(csrf): replace CSRF optionfalse
withboolean
#284New Contributors
false
withboolean
#284This discussion was created from the release 1.0.0.
Beta Was this translation helpful? Give feedback.
All reactions