pq_crypto-seal 0.1.2 → 0.1.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 0e2f25bfc50a4e95892fb3c9e25992ff359bd16cc65535dacf3863d943c34e52
-  data.tar.gz: 40462d41fa188924ba4abbd5d76b4ad22c48377964d70a4544bae919ec4f5140
+  metadata.gz: f595c15cfe06676ee508888c302a9bb5bab8083ffdef97540d6b6d19d877e270
+  data.tar.gz: 7e8107699dbdead218debc3c870d5ad98ba0f279a23f2c2698c3918bc0060d45
 SHA512:
-  metadata.gz: 8a3f087d4c922637fcbf5af86cae6a9e118b688215f9a218c6572e524555643e2d444f7452416575c2904f08a8c34742adc0e2cb4bfab6e33a0267015f03d177
-  data.tar.gz: e1746e895c1be25bd755fc358c4eac0291b21c6c638b7d87fb1603e08229783e942adcecbdc4c095e4ae1fde9ca00d49a7f472a89cc1ef183339a94f9546e025
+  metadata.gz: 9cc59508eea68e697e16ceee595718319b1f10c9ee4aceea186565ba3f9d1133e9b6717aa198de1a33f1e4782812caa6a2c32e6bce7ba557a9ba9c7d923e20fc
+  data.tar.gz: e2fcec77d71028fa2615a62af722441277dfda52b24e05c4e2d3ffa50621b3435c28ab14b742788237ef18c3ad4f3d0c12770e0de0488de858f7243d57dbb2f4

data/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Changelog
 
+## 0.1.3
+
+- Runtime dependency relaxed from `pq_crypto = 0.6.4` to `pq_crypto ~> 0.6`
+  so patch/minor releases on the 0.6 line (including 0.6.7) resolve without a
+  Seal bump. Wire suite 1 remains pinned by algorithm id and exact
+  key/ciphertext/shared-secret sizes inside Seal; do not treat this as carte
+  blanche for a future `1.x` / breaking KEM wire change.
+
 ## 0.1.2
 
 ### Security

data/FORMAT.md

@@ -55,7 +55,7 @@ Every complete recipient-section rebuild creates a new random section ID and
 recreates all real and dummy slots. Mixed wrapping suites are forbidden.
 
 Wrap suite `1` fixes MLKEM768-X25519/X-Wing **draft-10**-compatible encapsulation
-(`pq_crypto = 0.6.4` algorithm `:ml_kem_768_x25519_xwing`), HKDF-SHA256, AEGIS-256
+(`pq_crypto ~> 0.6` algorithm `:ml_kem_768_x25519_xwing`), HKDF-SHA256, AEGIS-256
 DEK wrapping, and 32-byte wrap nonces/tags. The suite id freezes that behaviour
 for at-rest data even if a later RFC text diverges. Exact sizes:
 

data/README.md

@@ -12,17 +12,17 @@ random DEK → AEGIS-256 → document
 `libaegis` 0.10.3 is vendored and compiled into the extension. The existing
 `pq_crypto` gem supplies the hybrid KEM and OpenSSL-backed primitives.
 
-> **Status:** 0.1.2 is experimental cryptographic software; format v1; not
+> **Status:** 0.1.3 is experimental cryptographic software; format v1; not
 > independently audited. Read `SECURITY.md` before using it for irreplaceable data.
 >
-> `wrap_suite_id = 1` is pinned to `:ml_kem_768_x25519_xwing` and `pq_crypto = 0.6.4`
+> `wrap_suite_id = 1` is pinned to `:ml_kem_768_x25519_xwing` and `pq_crypto ~> 0.6`
 > (X-Wing draft-10 wire sizes). Content suite 1 is AEGIS-256 via libaegis 0.10.3.
 
 ## Installation
 
 ```ruby
-gem "pq_crypto", "~> 0.6.4"
-gem "pq_crypto-seal", "~> 0.1.2"
+gem "pq_crypto", "~> 0.6"
+gem "pq_crypto-seal", "~> 0.1.3"
 ```
 
 Ruby `>= 2.7.1` and OpenSSL `>= 3.0` development files are required for a

data/RELEASING.md

@@ -1,7 +1,7 @@
 # Releasing
 
 1. Run `bundle exec ruby script/vendor_libs.rb --check`.
-2. Confirm `pq_crypto` dependency remains `= 0.6.4` and `WRAP_KEM_ALGORITHM`
+2. Confirm `pq_crypto` dependency remains `~> 0.6` and `WRAP_KEM_ALGORITHM`
    is still `:ml_kem_768_x25519_xwing` with the documented sizes.
 3. Run `bundle exec ruby script/release_contract_check.rb` (also enforced in CI).
 4. Run the full CI matrix: test, sanitize, fuzz, release_contract, gem-smoke.

data/SECURITY.md

@@ -1,7 +1,7 @@
 # Security
 
 This project has not received an independent cryptographic or implementation
-audit. Do not treat version 0.1.2 as a substitute for a reviewed storage design.
+audit. Do not treat version 0.1.3 as a substitute for a reviewed storage design.
 
 Experimental cryptographic software; format v1; not independently audited.
 
@@ -128,7 +128,7 @@ independent of future RFC text:
 
 | Component | Pin |
 |---|---|
-| `wrap_suite_id = 1` | MLKEM768-X25519 / X-Wing **draft-10** compatible via `pq_crypto = 0.6.4` algorithm `:ml_kem_768_x25519_xwing` (PK 1216, CT 1120, SS 32) |
+| `wrap_suite_id = 1` | MLKEM768-X25519 / X-Wing **draft-10** compatible via `pq_crypto ~> 0.6` algorithm `:ml_kem_768_x25519_xwing` (PK 1216, CT 1120, SS 32) |
 | `content_suite_id = 1` | AEGIS-256, 32-byte nonce/tag, inner-frame-v1, via vendored **libaegis 0.10.3** |
 | AEGIS KATs | CFRG AEGIS draft-18 positive/negative vectors in `test/aegis_vectors_test.rb` |
 | X-Wing KATs | draft-10 decapsulation vectors in `test/fixtures/xwing-draft-10-vector-*.json` (see `test/xwing_kat_test.rb`) |

data/VENDORING.md

@@ -13,7 +13,7 @@ libaegis 0.10.3.
   this snapshot, not to a future RFC that may diverge.
 
 X-Wing / MLKEM768-X25519 wrap suite 1 is supplied by runtime dependency
-`pq_crypto = 0.6.4` (not vendored here). External draft-10 decapsulation KATs
+`pq_crypto ~> 0.6` (not vendored here). External draft-10 decapsulation KATs
 live in `test/fixtures/xwing-draft-10-vector-*.json`.
 
 The complete source snapshot is retained, while the Ruby extension compiles only the AEGIS-256 and common implementation files it exposes. No system libaegis is

data/lib/pq_crypto/seal/version.rb

@@ -2,6 +2,6 @@
 
 module PQCrypto
   module Seal
-    VERSION = "0.1.2"
+    VERSION = "0.1.3"
   end
 end

data/pq_crypto-seal.gemspec

@@ -45,7 +45,7 @@ Gem::Specification.new do |spec|
   spec.require_paths = ["lib"]
   spec.extensions = ["ext/pq_crypto_seal/extconf.rb"]
 
-  spec.add_runtime_dependency "pq_crypto", "= 0.6.4"
+  spec.add_runtime_dependency "pq_crypto", "~> 0.6"
   spec.add_development_dependency "minitest", "~> 5.14"
   spec.add_development_dependency "rake", "~> 13.0"
   spec.add_development_dependency "rake-compiler", "~> 1.2"

metadata

@@ -1,29 +1,28 @@
 --- !ruby/object:Gem::Specification
 name: pq_crypto-seal
 version: !ruby/object:Gem::Version
-  version: 0.1.2
+  version: 0.1.3
 platform: ruby
 authors:
 - Roman Khaidarov
-autorequire:
 bindir: exe
 cert_chain: []
-date: 2026-07-21 00:00:00.000000000 Z
+date: 1980-01-02 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: pq_crypto
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - '='
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.6.4
+        version: '0.6'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - '='
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.6.4
+        version: '0.6'
 - !ruby/object:Gem::Dependency
   name: minitest
   requirement: !ruby/object:Gem::Requirement
@@ -139,7 +138,6 @@ licenses:
 metadata:
   source_code_uri: https://github.com/roman-haidarov/pq_crypto-seal
   changelog_uri: https://github.com/roman-haidarov/pq_crypto-seal/blob/main/CHANGELOG.md
-post_install_message:
 rdoc_options: []
 require_paths:
 - lib
@@ -154,8 +152,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.4.22
-signing_key:
+rubygems_version: 3.6.7
 specification_version: 4
 summary: Post-quantum envelope encryption for Ruby
 test_files: []