carve-hexapdf 0.1.0 → 0.1.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: d47fc98c98ecd21adba76ed8abb6150aabe535bcb99ad844b6f48705f115dce8
-  data.tar.gz: 3213a192f274a65f6e262ac73009dda8d33d88945406b20096120ce38d5a6158
+  metadata.gz: d9b8c7c6b8002f3587048d1711e0901a180e4f41a85778a2e4654f7daaeed9da
+  data.tar.gz: 6da20e9768485a0afe3aa2b71a73bb670a155a7adfb9e30d593bedead5db5632
 SHA512:
-  metadata.gz: 84ad78a47f2cbb33608373ed0d05e3af1f7a14b2f250ed193ad42586bce5e3bae4bdd0b58659517d58e410e6d5f2d7d4a739d9aacd167597c2ff1ffc44a5834d
-  data.tar.gz: 8f88fe4e7cfb412788e3d4c045937db3a03707d891221561ab181485fc6026577cfbbc058c74334c1a5fb4cd07d38dce5d3a4b21bc1f98024142d8e42731ee89
+  metadata.gz: 41deae43d68f4996a26a2e2ccae432550bb730877b82a164b5203fe3020e14e515e85d0261ff25a603c92bc7cc1957c2494c8ac7cf9b2c4174eed686f8b639c3
+  data.tar.gz: 3256a05ce59a8b4071df645e1df3690d3d9ee56c00d4f588f543330cf756c50e689c97aa39026db77e0caa1ac8f095b993fc57990dea20fecbb04d98fa838438

data/CHANGELOG.md

@@ -5,6 +5,21 @@ All notable changes to this project are documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## Unreleased
+
+## [0.1.1] - 2026-08-27
+
+### Changed
+
+- The development pin moves to released `carve-lang` 0.1.2, so the suite covers
+  the current embedded engine and output surface. The supported consumer range
+  remains `>= 0.1.1, < 0.2.0`: 0.1.1 still satisfies this renderer's API and
+  security requirements. On the engine's own 0.x scheme `0.1` is the major and the third digit
+  the minor, so the previous open range admitted, by the engine's own rules, a
+  release declared breaking - and this gem reads an AST whose node vocabulary
+  was already renamed once inside 0.1
+  ([#26](https://github.com/markup-carve/carve-hexapdf/issues/26)).
+
 ## [0.1.0] - 2026-08-19
 
 ### Added
@@ -38,7 +53,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   URLs show alt text, raw HTML and comments are dropped; the renderer never
   raises.
 
-[Unreleased]: https://github.com/markup-carve/carve-hexapdf/compare/v0.1.0...HEAD
+[Unreleased]: https://github.com/markup-carve/carve-hexapdf/compare/v0.1.1...HEAD
+[0.1.1]: https://github.com/markup-carve/carve-hexapdf/compare/v0.1.0...v0.1.1
 [0.1.0]: https://github.com/markup-carve/carve-hexapdf/releases/tag/v0.1.0
 
 - **Composite figures render as one grouped float.** A bare `::: figure`

data/README.md

@@ -215,6 +215,46 @@ always produces a PDF:
   fetching. Local files and `data:` URIs are embedded.
 - **Raw HTML** blocks/inlines and **comments** are dropped.
 
+## Development
+
+```sh
+bundle install
+bundle exec rake test
+```
+
+### Which engine you are testing against
+
+`bundle install` here does **not** resolve `carve-lang` from RubyGems. `Gemfile`
+pins the engine to a carve-rb revision, so a development run measures one exact
+engine build rather than whatever the registry serves that day:
+
+```sh
+bundle exec ruby script/verify_engine_pin.rb
+# carve-lang 0.1.2 from carve-rb b7f3a91a... (Gemfile pins b7f3a91a4192)
+```
+
+CI runs that before the suite and refuses when the Gemfile, the resolved bundle
+and the loaded library disagree. To develop against a local carve-rb checkout,
+point `CARVE_RB_PATH` at it - it has to be set on purpose, so the surprising
+resolution is the one you asked for:
+
+```sh
+CARVE_RB_PATH=../carve-rb bundle install
+```
+
+An installed copy of this gem resolves differently, through the range
+`carve-hexapdf.gemspec` declares - today `>= 0.1.1, < 0.2.0`. The two are
+deliberately not the same engine, and the difference is not academic: this gem
+reads an AST whose node vocabulary was renamed once already inside 0.1.
+`test/engine_floor_test.rb` asks whether the engine under `bundle exec rake
+test` still publishes the vocabulary the renderer maps, and
+`script/consumer_engine_probe.rb` asks the same of an actual `gem install` -
+daily in `Engine drift`, and again before every release.
+
+There is no committed `Gemfile.lock`, and that is deliberate; the reasoning,
+including why a lockfile would be a weaker pin here and what it would cost the
+Ruby 3.1 job, is at the top of `Gemfile`.
+
 ## Licensing
 
 This gem is **MIT** licensed. However, **HexaPDF is dual-licensed AGPL-3.0 /
@@ -224,7 +264,3 @@ application) or hold a
 [HexaPDF commercial license](https://hexapdf.gettalong.org/#pricing). This gem
 only bridges Carve to HexaPDF; your use of HexaPDF is governed by HexaPDF's own
 terms.
-
-## License
-
-MIT, markup-carve. See [LICENSE](LICENSE).

data/lib/carve/hexapdf/version.rb

@@ -2,6 +2,6 @@
 
 module Carve
   module Hexapdf
-    VERSION = "0.1.0"
+    VERSION = "0.1.1"
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: carve-hexapdf
 version: !ruby/object:Gem::Version
-  version: 0.1.0
+  version: 0.1.1
 platform: ruby
 authors:
 - markup-carve
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2026-08-19 00:00:00.000000000 Z
+date: 2026-09-09 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: carve-lang
@@ -17,6 +17,9 @@ dependencies:
     - - ">="
       - !ruby/object:Gem::Version
         version: 0.1.1
+    - - "<"
+      - !ruby/object:Gem::Version
+        version: 0.2.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
@@ -24,6 +27,9 @@ dependencies:
     - - ">="
       - !ruby/object:Gem::Version
         version: 0.1.1
+    - - "<"
+      - !ruby/object:Gem::Version
+        version: 0.2.0
 - !ruby/object:Gem::Dependency
   name: hexapdf
   requirement: !ruby/object:Gem::Requirement
@@ -107,7 +113,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.4.20
+rubygems_version: 3.4.19
 signing_key:
 specification_version: 4
 summary: Render the Carve markup language to PDF via the pure-Ruby HexaPDF engine.