Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^4.2.0
->^8.0.0
Release Notes
helmetjs/helmet (helmet)
v8.0.0
Compare Source
Changed
Strict-Transport-Security
now has a max-age of 365 days, up from 180Content-Security-Policy
middleware now throws an error if a directive should have quotes but does not, such asself
instead of'self'
. See #454Content-Security-Policy
'sgetDefaultDirectives
now returns a deep copy. This only affects users who were mutating the resultStrict-Transport-Security
now throws an error when "includeSubDomains" option is misspelled. This was previously a warningRemoved
v7.2.0
Compare Source
Changed
Content-Security-Policy
middleware now warns if a directive should have quotes but does not, such asself
instead of'self'
. This will be an error in future versions. See #454v7.1.0
Compare Source
Added
helmet.crossOriginEmbedderPolicy
now supports theunsafe-none
directive. See #477v7.0.0
Compare Source
Changed
Cross-Origin-Embedder-Policy
middleware is now disabled by default. See #411Removed
Expect-CT
is no longer part of Helmet. If you still need it, you can use theexpect-ct
package. See #378v6.2.0
Compare Source
strictTransportSecurity
for theStrict-Transport-Security
header, instead ofhsts
)v6.1.5
Compare Source
Fixed
v6.1.4
Compare Source
Fixed
v6.1.3
Compare Source
Fixed
v6.1.2
Compare Source
Fixed
main
to package to help with some build toolsv6.1.1
Compare Source
Fixed
v6.1.0
Compare Source
Changed
v6.0.1
Compare Source
Fixed
crossOriginEmbedderPolicy
did not accept options at the top level. See #390v6.0.0
Compare Source
Changed
helmet.contentSecurityPolicy
no longer setsblock-all-mixed-content
directive by defaulthelmet.expectCt
is no longer set by default. It can, however, be explicitly enabled. It will be removed in Helmet 7. See #310helmet.frameguard
no longer offers a specific error when trying to useALLOW-FROM
; it just says that it is unsupported. Only the error message has changedRemoved
v5.1.1
Compare Source
Changed
v5.1.0
Compare Source
Added
Cross-Origin-Embedder-Policy
: supportcredentialless
policy. See #365Content-Security-Policy
andContent-Security-Policy-Report-Only
Changed
Origin-Agent-Cluster
v5.0.2
Compare Source
Changed
v5.0.1
Compare Source
Changed
Removed
v5.0.0
Compare Source
Added
import helmet from "helmet"
andimport { frameguard } from "helmet"
). See #320Changed
helmet.contentSecurityPolicy
:useDefaults
option now defaults totrue
helmet.contentSecurityPolicy
:form-action
directive is now set to'self'
by defaulthelmet.crossOriginEmbedderPolicy
is enabled by defaulthelmet.crossOriginOpenerPolicy
is enabled by defaulthelmet.crossOriginResourcePolicy
is enabled by defaulthelmet.originAgentCluster
is enabled by defaulthelmet.frameguard
: add TypeScript editor autocomplete. See #322helmet()
function is slightly fasterRemoved
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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.
This PR was generated by Mend Renovate. View the repository job log.