forked from github/secure_headers
-
Notifications
You must be signed in to change notification settings - Fork 0
/
secure_headers.gemspec
29 lines (26 loc) · 1.39 KB
/
secure_headers.gemspec
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
# -*- encoding: utf-8 -*-
# frozen_string_literal: true
Gem::Specification.new do |gem|
gem.name = "secure_headers"
gem.version = "4.0.0"
gem.authors = ["Neil Matatall"]
gem.email = ["neil.matatall@gmail.com"]
gem.description = "Manages application of security headers with many safe defaults."
gem.summary = 'Add easily configured security headers to responses
including content-security-policy, x-frame-options,
strict-transport-security, etc.'
gem.homepage = "https://github.com/twitter/secureheaders"
gem.license = "Apache Public License 2.0"
gem.files = `git ls-files`.split($INPUT_RECORD_SEPARATOR)
gem.executables = gem.files.grep(%r{^bin/}).map { |f| File.basename(f) }
gem.test_files = gem.files.grep(%r{^(test|spec|features)/})
gem.require_paths = ["lib"]
gem.add_development_dependency "rake"
gem.add_dependency "useragent", ">= 0.15.0"
# TODO: delete this after 4.1 is cut or a number of 4.0.x releases have occurred
gem.post_install_message = <<-POST_INSTALL
**********
:wave: secure_headers 4.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/upgrading-to-4-0.md
**********
POST_INSTALL
end