You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: secure_headers.gemspec
+1-10Lines changed: 1 addition & 10 deletions
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
# frozen_string_literal: true
3
3
Gem::Specification.newdo |gem|
4
4
gem.name="secure_headers"
5
-
gem.version="5.0.4"
5
+
gem.version="5.0.5"
6
6
gem.authors=["Neil Matatall"]
7
7
gem.email=["neil.matatall@gmail.com"]
8
8
gem.description="Manages application of security headers with many safe defaults."
@@ -17,13 +17,4 @@ Gem::Specification.new do |gem|
17
17
gem.require_paths=["lib"]
18
18
gem.add_development_dependency"rake"
19
19
gem.add_dependency"useragent",">= 0.15.0"
20
-
21
-
# TODO: delete this after 4.1 is cut or a number of 4.0.x releases have occurred
22
-
gem.post_install_message=<<-POST_INSTALL
23
-
24
-
**********
25
-
:wave: secure_headers 5.0 introduces a lot of breaking changes (in the name of security!). It's highly likely you will need to update your secure_headers cookie configuration to avoid breaking things. See the upgrade guide for details: https://github.com/twitter/secureheaders/blob/master/docs/upgrading-to-5-0.md
0 commit comments