Skip to content

Releases: jagaapple/next-secure-headers

v2.2.0 - Support navigation directives for CSP

25 Feb 16:22
af1d126
Compare
Choose a tag to compare
  • Add navigation directives #41 - @naotone
    • Support form-action frame-ancestors directives
    • Move to navigation-to directive from ReportingDirective to NavigationDirective
  • Add about frame-ancestors CSP directive to readme #46 - @mattdell
  • Improve development environment

v2.1.0 - Support chain-case styles in CSP directives

26 Dec 20:31
87f6129
Compare
Choose a tag to compare
  • Add support for Node.js 14 #36 - @jagaapple
  • Add support for chain-case directive styles to CSP #40 - @jagaapple
  • Fix readme #37 - @jagaapple
  • Fix invalid bin field warning #39 - @jagaapple
  • Fix report-to directive #38
    • Fix parse processes
    • Fix invalid value like undefined <directive-name> when report-uri or report-to is specified
  • Improve development environment

v2.0.0 - Support static pages

08 Aug 09:41
2921f83
Compare
Choose a tag to compare

❗️Breaking Changes

The default export has been removed, withSecureHeaders function has been exported as named export instead.
You have to import withSecureHeaders like the following.

- import withSecureHeaders from "next-secure-headers";
+ import { withSecureHeaders } from "next-secure-headers";

v1.0.1

13 Dec 17:28
7120dd9
Compare
Choose a tag to compare
  • Fix setting headers after sending #10 - @jagaapple
  • Improve development environment
    • Enable automatic code formatting for VS Code #8 - @jagaapple

v1.0.0 - Initial public release

04 Dec 21:45
4b52e97
Compare
Choose a tag to compare