leptris 1.9.59 → 1.9.76.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: e2a400c8a5129b1a0485f8ec239fc11abe6261c5f930e46369ce2481ee5c7ea0
4
- data.tar.gz: 2fcdb3f77738362d51d5dd65c1bbea8d1a495c21b141e602b6f8e663b2e97b4b
3
+ metadata.gz: dd428731fd9d7dfc106f99400c4a33af748b7c68977c0e58fa443af84e86cf4a
4
+ data.tar.gz: 757b26092a6d7c2c37c9a5b415a695a131ec6855639483b67f08d65896a5322f
5
5
  SHA512:
6
- metadata.gz: af3f53eef914d192c152054c35d979ae09098684d25aadf1bf3eb50fca7d67736faf05a9f32f48434e8388eb09ebebd4b5ef00f8d7f21e6d563b144faaae045b
7
- data.tar.gz: f14d0cfaa7696949a7cf50cb1af6b095289ef8877f54c1968f7f0147083066c10059232f3f6b1df691600345e3f04615ce1793fd0f3512c6a886f55d113ed875
6
+ metadata.gz: e8f1cf4805a41cd0eb286dd9621189fab886b484d7b32b88ac755b6b2002bb6ecb19ad923f8a60458234d6d043f664b65f780dc7a9bd73714bfd2b8b455626e4
7
+ data.tar.gz: 37670ab91e6ae96f62c6b42f4b523d17279543c4584c65edd248610f9267f58a2e9d985aff2f66569f3c60b097a2f5c991972c4066ac0b5f37c2359e8434d82b
data/CHANGELOG.md CHANGED
@@ -5,6 +5,25 @@ All notable changes to Leptris will be documented in this file.
5
5
  The format is based on [Keep a Changelog](https://keepachangelog.com/1.0.0/),
6
6
  and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
7
7
 
8
+ ## [1.9.76.0] - 2026-09-04
9
+
10
+ ### Changed
11
+
12
+ - **Version scheme: `{libleptris full semver}.{binding patch}`.**
13
+ The gem's version now carries the C library's complete semver
14
+ plus a binding-only patch segment: `1.9.76.0` pairs with
15
+ libleptris `1.9.76`. Binding-only changes bump the fourth
16
+ segment (`1.9.76.1`); adopting a new libleptris release moves to
17
+ `{C}.0`. No functional change — `1.9.59` was the last
18
+ three-segment release and shipped this exact libleptris 1.9.76
19
+ content (equivalent to `1.9.76.0`).
20
+ - The release workflow's guard now accepts `x.y.z.w` and its
21
+ relative `patch` bump targets the BINDING (fourth) segment.
22
+ - CLAUDE.md's lockstep paragraph documents the scheme.
23
+
24
+ No libleptris change (pin stays 1.9.76); this is the scheme-switch
25
+ release.
26
+
8
27
  ## [1.9.59] - 2026-09-04
9
28
 
10
29
  ### Added
data/CLAUDE.md CHANGED
@@ -13,10 +13,13 @@ with the shared library vendored inside: x86_64/aarch64-linux (glibc
13
13
  and musl), x86_64/arm64-darwin, x64-mingw32/ucrt, aarch64-mingw-ucrt,
14
14
  plus the pure-Ruby fallback gem.
15
15
 
16
- Version lockstep: the gem's major.minor tracks the C library
17
- (`libleptris 1.6.x` <-> `leptris 1.6.x`). A C release means one PR
18
- carrying version.rb + the Rakefile `LIBLEPTRIS_VERSION` pin + the
19
- CHANGELOG entry, then the release workflow.
16
+ Version lockstep: the gem version is
17
+ `{libleptris full semver}.{binding patch}` gem `1.9.76.0` pairs
18
+ with libleptris `1.9.76`; binding-only changes bump the fourth
19
+ segment (`1.9.76.1`), an upstream adoption moves to `{C}.0`. A C
20
+ release means one PR carrying version.rb + the Rakefile
21
+ `LIBLEPTRIS_VERSION` pin + the CHANGELOG entry, then the release
22
+ workflow (`next_version={C}.0`).
20
23
 
21
24
  ## Commands
22
25
 
@@ -1,5 +1,5 @@
1
1
  # frozen_string_literal: true
2
2
 
3
3
  module Leptris
4
- VERSION = "1.9.59"
4
+ VERSION = "1.9.76.0"
5
5
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: leptris
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.9.59
4
+ version: 1.9.76.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Ribose Inc.