compliance_engine 0.6.0 → 1.0.0

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.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 9f8203b0a0381216d9a1a91c318f0f162bde1d4835bc7731c954156371b6f9b8
4
- data.tar.gz: 784264cbb1aba5772bbf97dafdd952c3b8823fa404236c372af87f1d6dad885b
3
+ metadata.gz: 2b2825442a658e3b82dd5416b52f491b8aaa2ead035a3c47692c9b873fa2c51d
4
+ data.tar.gz: 551f20825476674d946d8dfdc2f86c12132ed882616d09bd47704b46df95b359
5
5
  SHA512:
6
- metadata.gz: 1026ff097b4e46f31b59b2a584e9d25b94baa986014564fa6a0196d70224306956fd0499d923fa19b0c1035d248c490a3ffaaa1bbcf8f55bd222e7726fb25157
7
- data.tar.gz: 588997e4f32f95f7d1edef560a16a09399c59d1b7aba4677ca6cf0bf9d97f38568d9d14c9349a5e489288d16dffe0abc2abc0147cecc9beb5127701270d3594a
6
+ metadata.gz: 27ccd78087cf686a891954f1f9ee2c2731a6542e432073465c4aaef6697574317ec9370c3df182d8d95abf01b9e7efc906a761b54c8868b15af11e374b9fd8e2
7
+ data.tar.gz: 9792d49a21cd6f3929362be5a4b63f7f770438e1658b8a9806caead3e399263ad8918220cca006f74aff7166012f19b8468567ac6e8186ba0a95ea9ea8653ff5
data/AGENTS.md CHANGED
@@ -126,6 +126,10 @@ paths → EnvironmentLoader → ModuleLoader (one per module dir)
126
126
 
127
127
  In practice, only fact confinement is bypassed when `facts` is `nil`; module confinement still applies whenever `environment_data` is available. All confinement and risk/disabled-remediation filtering are effectively bypassed only when both `facts` and `environment_data` are unset and `enforcement_tolerance` is not a positive `Integer` (every fragment is then included). This is useful for offline analysis where system context and enforcement settings are unavailable.
128
128
 
129
+ ### Releases
130
+
131
+ Keep the version in `lib/compliance_engine/version.rb` (`ComplianceEngine::VERSION`) and the `version` field in `metadata.json` in sync — they must always match. Any version bump must also be accompanied by a corresponding entry in `CHANGELOG.md`.
132
+
129
133
  ### Code Style
130
134
 
131
135
  Rubocop is configured via `.rubocop.yml` inheriting from `voxpupuli-test`. Key style choices:
data/CHANGELOG.md CHANGED
@@ -1,3 +1,6 @@
1
+ ### 1.0.0 / 2026-06-04
2
+ * Declare the gem and Puppet module production-ready; no functional changes since 0.6.0
3
+
1
4
  ### 0.6.0 / 2026-05-05
2
5
  * Honor explicit `false` in profile `checks` and `ces` mappings as exclusions that override positive matches (#117)
3
6
  * Coerce non-String `zipfile.name` to `-` for buffer-opened zips (#121)
@@ -1,5 +1,5 @@
1
1
  # frozen_string_literal: true
2
2
 
3
3
  module ComplianceEngine
4
- VERSION = '0.6.0'
4
+ VERSION = '1.0.0'
5
5
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: compliance_engine
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.6.0
4
+ version: 1.0.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Steven Pritchard
@@ -159,7 +159,7 @@ licenses:
159
159
  metadata:
160
160
  homepage_uri: https://simp-project.com/docs/sce/
161
161
  source_code_uri: https://github.com/simp/rubygem-simp-compliance_engine
162
- changelog_uri: https://github.com/simp/rubygem-simp-compliance_engine/releases/tag/0.6.0
162
+ changelog_uri: https://github.com/simp/rubygem-simp-compliance_engine/releases/tag/1.0.0
163
163
  bug_tracker_uri: https://github.com/simp/rubygem-simp-compliance_engine/issues
164
164
  rdoc_options: []
165
165
  require_paths:
@@ -175,7 +175,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
175
175
  - !ruby/object:Gem::Version
176
176
  version: '0'
177
177
  requirements: []
178
- rubygems_version: 4.0.6
178
+ rubygems_version: 4.0.10
179
179
  specification_version: 4
180
180
  summary: Parser for Sicura Compliance Engine data
181
181
  test_files: []