v3 line: require relaton v3 (the monogem) - #133
Merged
Merged
Conversation
3 tasks
The dependency floor becomes relaton >= 3.0.0.pre.alpha (the monogem) and Relaton::Cli.registry resolves Relaton::Db::Registry directly — the v2 fallback stays on the 2.x line (PR #132).
The released 3.0.0.pre.alpha gems lag relaton main (the pubid v2 base_identifier rename), so CI resolves main until the next pre ships.
…d iso_2146 cassette - version: drop the relaton-bib line and only print processor gems that are actually loaded — the v3 monogem ships every flavor, so neither relaton-bib nor per-flavor gems exist anymore - fetch specs: derive the Recognised types expectation from the registry instead of the hardcoded v2 flavor list - iso_2146.yml: re-record against the v3 index-v2.zip fetch flow. Recorded out-of-band with stdlib psych (yeptris#168 makes any dump through the rebind emit unparseable/mangled bytes): the zip body is byte-identical to the live download (sha-verified) and carried as a core !binary scalar
…s deterministic - fetch_document rescues Parslet::ParseFailed and reports "<code>" is not a recognized standards identifier (port of relaton 05add9456, which landed on the monorepo's gems/relaton-cli after this branch forked) — an unparseable reference was an uncaught pubid ParseError with exit 1 on the v3 line - the acceptance shell-outs invoke bundle exec relaton instead of the ambient binstub, so they exercise this branch's exe rather than whatever gem is installed; the undefined-standard expectation moves to the friendly message
Adapter selection is an end-user concern: relaton-cli owns its choice the same way the library stopped owning it. Pins nokogiri for now (lutaml-model#856 blocks leptris for derived map_content).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
New major line for relaton v3 (the monogem).
relaton >= 3.0.0.pre.alpha.Relaton::Cli.registryresolvesRelaton::Db::Registrydirectly — no v2 fallback (the 2.x line keeps the dual resolution in Resolve the processor registry on either relaton line #132).Relaton::Registry.instanceuses (cli.rb, command.rb, data_fetcher.rb, yaml_convertor.rb) go through the accessor.The gem's own version number for this line is deliberately left at the current value until the release version is decided.