moxml 0.6.13 → 0.6.14

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: adf6e5f1ca76598320e65ebac94a1e9bbd062cbf1174ede7291bf59fff917e03
4
- data.tar.gz: e59147df518ce7edf4bd02ecbabe183dd2cd5aef8824069ce2b49b44b41db52c
3
+ metadata.gz: 6f98fed507060aa402438904c53219866a92d2a3dcf36bfb0fc9fa15a8782ac8
4
+ data.tar.gz: a5f2791889fdc6c98f420065a9c8ba502421b38f37d2600c02680ba00877d1a3
5
5
  SHA512:
6
- metadata.gz: 313b2865b50d5180b39d387c8f3fbf36d31e0df383a9a3e2b573eac31a43f582363ae71e525c9a850f7db4dfcb49f719ea8aff60562d87c59df9098e2ce79f9a
7
- data.tar.gz: 1e558f7beb60d77b082b28e8aeb79f1c91549d7e4207c5aa5e7c40ba2ef9f619503427b07a129d8c1cf78ad05ca4fa93041fe4876c988ebebbc98734e682c593
6
+ metadata.gz: 8be80b6ab392cda9f819e157fd7ffc470f102ade4d89e5ef76374516741942c46def843df7caeaf5b2a09d82344958edd7dd65680042d1be8dfa6cc54cb769a4
7
+ data.tar.gz: 312977967cf7d123db6f1bfd1c55d94f14f8a81ab966d562d4fb6f28c8199d9e7df07f726b3832cc0b77d6ef21b55f21d43903603cb7ec4b66117dec00a5f049
@@ -0,0 +1,45 @@
1
+ name: moxml-testsuite
2
+
3
+ on:
4
+ push:
5
+ branches: [ main ]
6
+ paths-ignore:
7
+ - '**.adoc'
8
+ pull_request:
9
+ paths-ignore:
10
+ - '**.adoc'
11
+ workflow_dispatch:
12
+
13
+ # The certifier runs against THIS checkout: the testsuite gem pins the
14
+ # dataset rows, so a model answer change that stales the vendored
15
+ # dataset (schema 5) goes red here — the same early warning the
16
+ # moxml-rs/moxml-ts vendored pins provide.
17
+ #
18
+ # The dependent-rake shared workflow cannot carry this repo: its
19
+ # gemspec line-filter drops every line containing the gem name, and
20
+ # a gem named moxml-testsuite mentions "moxml" on nearly every line
21
+ # (spec.name, the version require_relative, the homepage). The local
22
+ # path override binds the checkout without touching the gemspec.
23
+
24
+ jobs:
25
+ testsuite:
26
+ runs-on: ubuntu-latest
27
+ name: certify main (3.4)
28
+ steps:
29
+ - uses: actions/checkout@v6
30
+ - uses: actions/checkout@v6
31
+ with:
32
+ repository: lutaml/moxml-testsuite
33
+ path: testsuite
34
+ - uses: ruby/setup-ruby@v1
35
+ with:
36
+ ruby-version: '3.4'
37
+ - name: Bind the testsuite to this checkout
38
+ working-directory: testsuite
39
+ run: |
40
+ bundle config set --local local.moxml "$GITHUB_WORKSPACE"
41
+ rm -f Gemfile.lock
42
+ bundle install
43
+ - name: Certify
44
+ working-directory: testsuite
45
+ run: bundle exec rspec
data/Gemfile CHANGED
@@ -12,7 +12,7 @@ gem "base64"
12
12
  gem "benchmark"
13
13
  gem "benchmark-ips"
14
14
  gem "get_process_mem"
15
- gem "leptris", "~> 1.9.420.2"
15
+ gem "leptris", "~> 1.9.423"
16
16
  gem "libxml-ruby", ">= 5.0"
17
17
  gem "nokogiri", "~> 1.18"
18
18
  gem "oga"
data/README.adoc CHANGED
@@ -128,7 +128,7 @@ pair serves; cross-import schema sets (`Context#xsd_set`) ride the
128
128
  compile_set face (1.9.386.0 ✓, the floor now requires it).
129
129
  |===
130
130
 
131
- NOTE: moxml's dev Gemfile pins `leptris ~> 1.9.420.2` (the tested pair; the gemspec itself has zero runtime dependencies). The adapter enforces the floor at load.
131
+ NOTE: moxml's dev Gemfile pins `leptris ~> 1.9.423` (the tested pair; the gemspec itself has zero runtime dependencies). The adapter enforces the floor at load.
132
132
  `ox ~> 2.14`, `libxml-ruby >= 5.0`, and the vendored oga fork — the CI
133
133
  matrix tests exactly those floors.
134
134
 
@@ -92,12 +92,22 @@ vendored at its release pin, driven by `cargo test`.
92
92
  |link:https://github.com/lutaml/moxml-ts[@lutaml/moxml] — fetches the
93
93
  pinned wasm bundles (`scripts/fetch-wasm.sh`), drives the families
94
94
  through the engine and model faces with vitest.
95
+
96
+ |Suite gem
97
+ |link:https://github.com/lutaml/moxml-testsuite[moxml-testsuite] — the
98
+ certification gem: the dataset vendored, the runner driving any object
99
+ that implements the certification protocol (parse, serialize,
100
+ canonicalize, XSD validation, and the decision faces). The bundled
101
+ moxml-backed Reference certifies a moxml engine; a facade that cannot
102
+ answer a family sees it SKIP, never a quiet pass.
95
103
  |===
96
104
 
97
105
  The vendored-pin chain moxml → moxml-rs → moxml-ts means every tier
98
106
  tests the same rows: a dataset revision ships as a moxml release, the
99
107
  Rust crate re-vendors it at its next release, and the TS package pins
100
- both bundles.
108
+ both bundles. The suite gem vendors the same rows for third-party
109
+ engines: certification is open — implement the protocol, run the
110
+ families, publish the report.
101
111
 
102
112
  == Why data, not prose
103
113
 
data/lib/moxml/version.rb CHANGED
@@ -1,5 +1,5 @@
1
1
  # frozen_string_literal: true
2
2
 
3
3
  module Moxml
4
- VERSION = "0.6.13"
4
+ VERSION = "0.6.14"
5
5
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: moxml
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.6.13
4
+ version: 0.6.14
5
5
  platform: ruby
6
6
  authors:
7
7
  - Ribose Inc.
@@ -24,6 +24,7 @@ files:
24
24
  - ".github/workflows/dependent-repos.json"
25
25
  - ".github/workflows/dependent-tests.yml"
26
26
  - ".github/workflows/docs.yml"
27
+ - ".github/workflows/moxml-testsuite.yml"
27
28
  - ".github/workflows/nightly-fuzz.yml"
28
29
  - ".github/workflows/performance-release.yml"
29
30
  - ".github/workflows/performance.yml"