Skip to content

Releases: Baroshem/nuxt-security

2.6.0

Choose a tag to compare

@Baroshem Baroshem released this 12 May 06:39
f35d530

What's Changed

  • feat(csp): add support for Content-Security-Policy-Report-Only header by @Gonzo17 in #672
  • fix: compute CSP hashes from final HTML in render:response by @harlan-zw in #705
    Resolves #704 Backtracking regex issue in plugin cspSsrNonce
    Resolves #684 Default strict: false does not work on Nuxt production build
    Update Node to 24.x
    #674 nuxt/hints#186 (comment)
    Security Advisory GHSA-6cv5-qqmv-j28h
    Security Advisory GHSA-7hcp-x3c6-53f3

New Contributors

Full Changelog: v2.5.1...v2.6.0

2.5.1

Choose a tag to compare

@Baroshem Baroshem released this 16 Jan 07:24
094f564

What's Changed

New Contributors

Full Changelog: v2.5.0...v2.5.1

2.5.0

Choose a tag to compare

@Baroshem Baroshem released this 20 Nov 06:19

What's Changed

Full Changelog: v2.4.0...v2.5.0

2.4.0

Choose a tag to compare

@Baroshem Baroshem released this 21 Aug 05:47
55bb8cb

What's Changed

New Contributors

  • @jelmerdemaat made their first contribution in #644
  • @FBFunnyBunnyFB made their first contribution in #649

Full Changelog: v2.3.0...v2.4.0

2.3.0

Choose a tag to compare

@Baroshem Baroshem released this 23 Jul 05:59
9049b87

What's Changed

New Contributors

Full Changelog: v2.2.0...v2.3.0

v2.2.0

Choose a tag to compare

@Baroshem Baroshem released this 04 Mar 08:04
99019bb

This version introduces a new feature to the rate limiter middleware by adding a whitelist option, along with several related changes to the codebase and documentation.

New Feature: Whitelist Option for Rate Limiter

  • Rate Limiter Configuration:

    • Added a whiteList property to the RateLimiter type, allowing specific IP addresses to bypass rate limiting. (docs/content/3.middleware/1.rate-limiter.md, src/types/middlewares.ts, src/defaultConfig.ts) [1] [2] [3]
    • Updated documentation to include details about the new whiteList property. (docs/content/3.middleware/1.rate-limiter.md)
  • Security Configuration:

    • Fixed an issue where securityConfig was not correctly initialized in the basic authentication middleware. (src/runtime/server/middleware/basicAuth.ts)
  • Nonce Handling:

    • Improved the handling of nonces in CSP headers by ensuring existing nonces are replaced instead of duplicated. (src/runtime/nitro/plugins/40-cspSsrNonce.ts) [1] [2]

What's Changed

New Contributors

Full Changelog: v2.1.5...v2.2.0

v2.1.5

Choose a tag to compare

@vejja vejja released this 30 Nov 15:17
b39dbd9

馃毃Hotfix Release : disable minification by default

This release fixes an issue reported in #576 whereby Nuxt UI v3 styles could break.
The issue was related to minification settings.

This release also deploys the new version of the documentation pages for Nuxt Security
Enjoy reading 馃摉

What's Changed

New Contributors

Full Changelog: v2.1.4...v2.1.5

2.1.4

Choose a tag to compare

@vejja vejja released this 22 Nov 15:19

compare changes

馃┕ Hotfix Release: SRI for PrimeVue

This release introduces specific support for Subresource Integrity with PrimeVue

鉂わ笍 Contributors

What's Changed

  • chore(release): 2.1.3 by @vejja in #566
  • fix: #564 resolves issue with element.replace on non-string elements by @lawren in #567

Full Changelog: v2.1.3...v2.1.4

2.1.3

Choose a tag to compare

@vejja vejja released this 22 Nov 14:50

馃┕ Hotfix Release: Nonce for PrimeVue

This release introduces specific support for Nonce with PrimeVue

鉂わ笍 Contributors

What's Changed

  • chore(release): 2.1.2 by @vejja in #563
  • fix: #564 resolves issue with element.replace on non-string elements by @lawren in #565

New Contributors

Full Changelog: v2.1.2...v2.1.3

2.1.2

Choose a tag to compare

@vejja vejja released this 19 Nov 14:30

馃毃Hotfix release: re-enable console.logs in dev mode

This release prevents the removal of console.log statements by Nuxt-Security in development mode.

Nuxt Security helps you ship safer applications by removing console.log statements when the removeLoggers option is set to true, which is the default value.
However, removing console.log statements by default also in development mode is causing our users to search why their logs are disappearing.

With this release, removeLoggers only removes console.log statements in production builds.

What's Changed

  • fix(core): do not remove loggers in dev mode by @vejja in #561

Full Changelog: v2.1.1...v2.1.2