verikloak-rails 1.2.0 → 1.2.1

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: 4ab889b6413e152dc2be695f2f4f738d7e2b90712b54559cc596e6d1c92166ed
4
- data.tar.gz: b97dd2c56aca7b021daf781ffc2ad834bc0b42c4b72efdd9cdda1d609495f4a6
3
+ metadata.gz: '05904a396b0bc210cb216f983bdc9c170d8192b82853f0bcc16e4d5ad0683d81'
4
+ data.tar.gz: 2a14889e6525024d20c1e45530e109fe8c56653b04d35cc432ba8f5e33019a65
5
5
  SHA512:
6
- metadata.gz: 5bdf562dbadfbede90f0d2d32ab69f62072636abd5a7ff0a3580a1fe6a58cb2dd24ee35a0468b4d0b1d5fe91174e9e49dc481b2cfee862a9030a909b58742c78
7
- data.tar.gz: 3ec0f43f095dd1002e6f612af4061beda81f29da93b2bc6e09d0fb37d67dfce477d4cc4194705441e11318ad11902f37fac2ab42768b4986eb0fcdc092a3bd66
6
+ metadata.gz: c1806b6e9a46f0cd22e3c06417de86b0c3d1482bd9760cb4f7fdbb99f49a262ba3efcacc52f0b7883ac0a4b41b4aa2a985f3f22db9fb5b0475d929a1571288d3
7
+ data.tar.gz: d45ec2512255976e4754529dce28e279a157854743a28e6e7aaef4073fb989571908388356eff2db72bd64d6d30b021b297c441416d421bf94804030236bc8d6
data/CHANGELOG.md CHANGED
@@ -7,6 +7,17 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
7
7
 
8
8
  ---
9
9
 
10
+ ## [1.2.1] - 2026-07-03
11
+
12
+ ### Fixed
13
+ - **CI coverage was silently never measured**: the RSpec step set `SIMPLECOV: true` as step-level env, but `docker compose run` does not pass host env vars into the container, so `spec_helper` never enabled SimpleCov and the uploaded `rspec-coverage` artifact contained no report. The step now forwards it explicitly (`docker compose run -e SIMPLECOV`), matching verikloak core.
14
+ - **Order-dependent spec failures under random ordering**: `spec/integration/rails_integration_spec.rb` could leave custom `user_env_key` / `token_env_key` values on the process-global configuration after its last example, breaking the `Testing::MiddlewareStub` default-key specs when they happened to run next (first caught by the new CI matrix, seed 29776). `spec_helper` now resets the global `Verikloak::Rails` configuration after every example.
15
+
16
+ ### Added
17
+ - **CI Ruby compatibility matrix (3.1/3.2/3.3)**: a new non-docker `compatibility` job verifies the gemspec's `required_ruby_version >= 3.1` claim on every supported minor Ruby (the docker `rspec` job keeps covering the pinned development Ruby 3.4). It bundles with the new `gemfiles/compat.gemfile` because the main `Gemfile.lock` pins Rails 8.1 / zeitwerk 2.7 (Ruby >= 3.2 only); each matrix Ruby resolves the newest Rails it supports (7.2 on 3.1, 8.1 on 3.2+), which also covers a Rails series older than the pinned development one (the declared Rails minimum `>= 6.1` itself is not exercised).
18
+
19
+ ---
20
+
10
21
  ## [1.2.0] - 2026-07-03
11
22
 
12
23
  ### Fixed
@@ -2,6 +2,6 @@
2
2
 
3
3
  module Verikloak
4
4
  module Rails
5
- VERSION = '1.2.0'
5
+ VERSION = '1.2.1'
6
6
  end
7
7
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: verikloak-rails
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.2.0
4
+ version: 1.2.1
5
5
  platform: ruby
6
6
  authors:
7
7
  - taiyaky
@@ -98,7 +98,7 @@ metadata:
98
98
  source_code_uri: https://github.com/taiyaky/verikloak-rails
99
99
  changelog_uri: https://github.com/taiyaky/verikloak-rails/blob/main/CHANGELOG.md
100
100
  bug_tracker_uri: https://github.com/taiyaky/verikloak-rails/issues
101
- documentation_uri: https://rubydoc.info/gems/verikloak-rails/1.2.0
101
+ documentation_uri: https://rubydoc.info/gems/verikloak-rails/1.2.1
102
102
  rubygems_mfa_required: 'true'
103
103
  rdoc_options: []
104
104
  require_paths: