parse_a_changelog 1.3.3 → 1.3.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. checksums.yaml +4 -4
  2. data/CHANGELOG.md +7 -1
  3. data/SECURITY.md +2 -38
  4. metadata +2 -2
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 684eac9caf9ec74bb72c8dd649d71b47baf57c698d11f34ef9d30d49e4b7ebf2
4
- data.tar.gz: f3c459ea80b75a2f25f62e9000d9e4863f8177e05db04e42ccda47641f37e313
3
+ metadata.gz: 385170da8c354b364628ebac03f40fc719f1ac6616689bbb8125e222def15044
4
+ data.tar.gz: 1c84465bdd1857700160d3c6f30b825a077339537a12387217e683e4f7c67cb8
5
5
  SHA512:
6
- metadata.gz: 873fe4fe84e8c8f8ca7822f243c582f072d787d80070954618d0b77078214e9de7ffb0cf5741f113ce9b85b12101d52c3af7dc10e59127a56a8c3fb2cf1a65c3
7
- data.tar.gz: 22e35de5e29599402757262c5ef93863f246712bd57592841b699d7e8beb66c4590085a494fffc97ad2b6183ad496b08f7059194b1f8c9a27a36a0491b680c8b
6
+ metadata.gz: 66f11e4c08336c8842e3e978fe39bf742572c4686000d7770380f2af142415a1c1a911a898078298414f0ab4fa77e5ac310e2bf75b2e901dc87df88fc4dea975
7
+ data.tar.gz: a3080c71ecf4480f7f9dc98b1e0ee10229f00dfdc20807fec59c44eda902d2dae0919ad5ddff8ffe0bae72d5d65ed113453794bd78f392ecd22fe120f1fb1e5c
data/CHANGELOG.md CHANGED
@@ -6,6 +6,10 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
6
6
 
7
7
  ## [Unreleased]
8
8
 
9
+ ## [1.3.4] - 2025-10-16
10
+ ### Changed
11
+ - Updated documentation to align with Conjur Enterprise name change to Secrets Manager. (CNJR-11000)
12
+
9
13
  ## [1.3.3] - 2024-11-08
10
14
  ### Changed
11
15
  - Decrease Docker image size by using ruby:3-alpine base image (CNJR-5578)
@@ -94,7 +98,9 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
94
98
  - Open source license and contributing information
95
99
  - Change log and versioning information
96
100
 
97
- [Unreleased]: https://github.com/cyberark/parse-a-changelog/compare/v1.3.1...HEAD
101
+ [Unreleased]: https://github.com/cyberark/parse-a-changelog/compare/v1.3.4...HEAD
102
+ [1.3.4]: https://github.com/cyberark/parse-a-changelog/compare/v1.3.3...v1.3.4
103
+ [1.3.3]: https://github.com/cyberark/parse-a-changelog/compare/v1.3.2...v1.3.3
98
104
  [1.3.2]: https://github.com/cyberark/parse-a-changelog/compare/v1.3.0...v1.3.2
99
105
  [1.3.0]: https://github.com/cyberark/parse-a-changelog/compare/v1.2.0...v1.3.0
100
106
  [1.2.0]: https://github.com/cyberark/parse-a-changelog/compare/v1.1.0...v1.2.0
data/SECURITY.md CHANGED
@@ -1,42 +1,6 @@
1
1
  # Security Policies and Procedures
2
2
 
3
- This document outlines security procedures and general policies for the CyberArk Conjur
4
- suite of tools and products.
5
-
6
- * [Reporting a Bug](#reporting-a-bug)
7
- * [Disclosure Policy](#disclosure-policy)
8
- * [Comments on this Policy](#comments-on-this-policy)
9
-
10
3
  ## Reporting a Bug
4
+ CyberArk takes product security very seriously. If you believe you have found a vulnerability in one of our products, we ask that you follow responsible disclosure guidelines and contact product_security@cyberark.com and work with us toward a quick resolution to protect our customers.
11
5
 
12
- The CyberArk Conjur team and community take all security bugs in the Conjur suite seriously.
13
- Thank you for improving the security of the Conjur suite. We appreciate your efforts and
14
- responsible disclosure and will make every effort to acknowledge your
15
- contributions.
16
-
17
- Report security bugs by emailing the lead maintainers at security@conjur.org.
18
-
19
- The maintainers will acknowledge your email within 2 business days. Subsequently, we will
20
- send a more detailed response within 2 business days of our acknowledgement indicating
21
- the next steps in handling your report. After the initial reply to your report, the security
22
- team will endeavor to keep you informed of the progress towards a fix and full
23
- announcement, and may ask for additional information or guidance.
24
-
25
- Report security bugs in third-party modules to the person or team maintaining
26
- the module.
27
-
28
- ## Disclosure Policy
29
-
30
- When the security team receives a security bug report, they will assign it to a
31
- primary handler. This person will coordinate the fix and release process,
32
- involving the following steps:
33
-
34
- * Confirm the problem and determine the affected versions.
35
- * Audit code to find any potential similar problems.
36
- * Prepare fixes for all releases still under maintenance. These fixes will be
37
- released as fast as possible.
38
-
39
- ## Comments on this Policy
40
-
41
- If you have suggestions on how this process could be improved please submit a
42
- pull request.
6
+ Refer to [CyberArk's Security Vulnerability Policy](https://www.cyberark.com/cyberark-security-vulinerability-policy.pdf) for more details
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: parse_a_changelog
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.3.3
4
+ version: 1.3.4
5
5
  platform: ruby
6
6
  authors:
7
7
  - John Tuttle
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2024-11-12 00:00:00.000000000 Z
11
+ date: 2025-10-16 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: treetop