-
Notifications
You must be signed in to change notification settings - Fork 0
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
chore(deps): update dependency helmet to v8 #91
base: main
Are you sure you want to change the base?
Conversation
Reviewer's Guide by SourceryThis pull request updates the helmet dependency from version 3.21.1 to 8.0.0. This is a major version update, which includes breaking changes. The update was performed by renovate bot. No diagrams generated as the changes look simple and do not need a visual representation. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have skipped reviewing this pull request. It seems to have been created by a bot (hey, renovate[bot]!). We assume it knows what it's doing!
c52b4fa
to
4ae254d
Compare
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
4ae254d
to
6104a4f
Compare
This PR contains the following updates:
^3.21.1
->^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
v4.6.0
Compare Source
Added
helmet.contentSecurityPolicy
: theuseDefaults
option, defaulting tofalse
, lets you selectively override defaults more easilypackage.json
. See #303v4.5.0
Compare Source
Added
helmet.crossOriginEmbedderPolicy
: a new middleware for theCross-Origin-Embedder-Policy
header, disabled by defaulthelmet.crossOriginOpenerPolicy
: a new middleware for theCross-Origin-Opener-Policy
header, disabled by defaulthelmet.crossOriginResourcePolicy
: a new middleware for theCross-Origin-Resource-Policy
header, disabled by defaultChanged
true
enables a middleware with default options. Previously, this would fail with an error if the middleware was already enabled by default.originAgentCluster
at the top levelFixed
v4.4.1
Compare Source
Changed
v4.4.0
Compare Source
Added
helmet.originAgentCluster
: a new middleware for theOrigin-Agent-Cluster
header, disabled by defaultv4.3.1
Compare Source
Fixed
helmet.contentSecurityPolicy
: broken TypeScript types. See #283v4.3.0
Compare Source
Added
helmet.contentSecurityPolicy
: setting thedefault-src
tohelmet.contentSecurityPolicy.dangerouslyDisableDefaultSrc
disables itChanged
helmet.frameguard
: slightly improved error messages for non-stringsv4.2.0
Compare Source
Added
helmet.contentSecurityPolicy
: get the default directives withcontentSecurityPolicy.getDefaultDirectives()
Changed
helmet()
now supports objects that don't haveObject.prototype
in their chain, such asObject.create(null)
, as optionshelmet.expectCt
:max-age
is now first. See #264v4.1.1
Compare Source
Changed
v4.1.0
Compare Source
Added
helmet.contentSecurityPolicy
:Changed
Removed
HelmetOptions
interface is no longer exported. This only affects TypeScript users. If you need the functionality back, see this commentv4.0.0
Compare Source
See the Helmet 4 upgrade guide for help upgrading from Helmet 3.
Added
helmet.contentSecurityPolicy
:default-src
directive is supplied, an error is thrownChanged
helmet.contentSecurityPolicy
:helmet.xssFilter
now disables the buggy XSS filter by default. See #230Removed
helmet.featurePolicy
. If you still need it, use thefeature-policy
package on npm.helmet.hpkp
. If you still need it, use thehpkp
package on npm.helmet.noCache
. If you still need it, use thenocache
package on npm.helmet.contentSecurityPolicy
:browserSniff
anddisableAndroid
parameters). See helmetjs/csp#97reportOnly
. Read this if you need help.setAllHeaders
parameter). Read this if you need help.loose
optionhelmet.frameguard
:ALLOW-FROM
action. Read more here.helmet.hidePoweredBy
no longer accepts arguments. See this article to see how to replicate the removed behavior. See #224.helmet.hsts
:includeSubdomains
with a lowercase D. See #231setIf
. Read this if you need help. See #232helmet.xssFilter
no longer accepts options. Read "How to disable blocking with X-XSS-Protection" and "How to enable thereport
directive with X-XSS-Protection" if you need the legacy behavior.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.