diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index 14eea0b..6e90ba3 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -17,6 +17,11 @@ jobs: environment: release permissions: id-token: write + env: + # Keep the bundle out of the system gems. release-gem signs the gem + # with an unbundled `gem exec` that sees the system gems, and the json + # version in Gemfile.lock can break the signer there. + BUNDLE_PATH: vendor/bundle steps: - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1 with: @@ -36,4 +41,17 @@ jobs: # zizmor complains that 'v1' is a ref that can be provided by both the branch and tag namespaces. # specify that we want the v1 branch. - - uses: rubygems/release-gem@7f9650160c1a4e7989fdc9855807bdbd421d8b6b # v1.4.1 + - uses: rubygems/release-gem@5c53f5308233b7c0f47411f0471b3faae6fa57b2 # v1.4.2 + + # release-gem pushes the gem without an attestation if signing fails, + # and the job still passes. Fail the job so that someone notices. + - name: Check that RubyGems.org has an attestation + run: | + for gem in pkg/*.gem; do + name="$(basename "$gem" .gem)" + if ! curl -fsS "https://rubygems.org/api/v1/attestations/$name.json" | + jq -e 'length > 0' >/dev/null; then + echo "::error::RubyGems.org has no attestation for $name." + exit 1 + fi + done diff --git a/CHANGELOG.md b/CHANGELOG.md index 2f9ddc5..655cce7 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,23 @@ # Changelog +## 1.7.1 (2026-11-17) + +* No code changes. This release republishes 1.7.0 with a Sigstore + attestation. The release workflow failed to sign 1.7.0 and pushed it + without one. + +## 1.7.0 (2026-11-17) + +* The minimum version of the `maxmind-db` gem is now 1.5.0. This version + limits the work and memory of each record decode and of the metadata decode + when a database is opened: 65,536 decoded values, 512 levels of nesting, and + 2 MiB of string, bytes, and integer payload. Opening a database or looking up + an IP address raises `MaxMind::DB::InvalidDatabaseError` if a decode exceeds + a limit. It also rejects pointers that target pointers, and it makes lookups + faster. MaxMind databases are well within the limits, but a custom database + that worked before may now fail. See the + [maxmind-db 1.5.0 changelog](https://github.com/maxmind/MaxMind-DB-Reader-ruby/blob/v1.5.0/CHANGELOG.md). + ## 1.6.0 (2026-07-16) * A new `residential` object has been added to the `anonymizer` object on diff --git a/Gemfile.lock b/Gemfile.lock index 851c0d9..27e72d4 100644 --- a/Gemfile.lock +++ b/Gemfile.lock @@ -1,10 +1,10 @@ PATH remote: . specs: - maxmind-geoip2 (1.6.0) + maxmind-geoip2 (1.7.1) connection_pool (>= 2.2, < 4.0) http (>= 4.3, < 7.0) - maxmind-db (~> 1.4) + maxmind-db (~> 1.5) GEM remote: https://rubygems.org/ diff --git a/lib/maxmind/geoip2/version.rb b/lib/maxmind/geoip2/version.rb index ffa8058..16e3915 100644 --- a/lib/maxmind/geoip2/version.rb +++ b/lib/maxmind/geoip2/version.rb @@ -3,6 +3,6 @@ module MaxMind module GeoIP2 # The Gem version. - VERSION = '1.6.0' + VERSION = '1.7.1' end end diff --git a/maxmind-geoip2.gemspec b/maxmind-geoip2.gemspec index 42be6ca..d0efcc4 100644 --- a/maxmind-geoip2.gemspec +++ b/maxmind-geoip2.gemspec @@ -31,7 +31,7 @@ Gem::Specification.new do |s| s.add_dependency 'connection_pool', '>= 2.2', '< 4.0' s.add_dependency 'http', '>= 4.3', '< 7.0' - s.add_dependency 'maxmind-db', ['~> 1.4'] + s.add_dependency 'maxmind-db', ['~> 1.5'] s.add_development_dependency 'minitest' s.add_development_dependency 'rake'