chore: bump xmi pin to 0.6+; tighten lutaml-uml pin to 0.5.0+#16
Merged
Conversation
xmi: the Phase 2 transformer work depends on features added in xmi 0.6.0 — Xmi::Uml::Slot, OpaqueExpression, InterfaceRealization, ValueSpecification polymorphic hierarchy (LiteralInteger / LiteralUnlimitedNatural / LiteralString), Uml::Base pattern, and the Phase 2 attribute set on PackagedElement (visibility, is_abstract, classifier, aggregation, interface_realization, slot). xmi 0.5.x lacks all of these. Verified against local checkout of xmi 0.6.0 and published 0.6.1. lutaml-uml: the prior '~> 0.5' pin is functionally correct (the bridge API surface — Lutaml::Uml::Document, UmlClass, Association, DataType, Enum, Generalization, Operation, Package, Realization, TaggedValue, TopElement, TopElementAttribute, Value, Cardinality, Constraint, Dependency, Diagram, DiagramLink, DiagramObject, GeneralAttribute, Instance, Validation — is intact from 0.2 through 0.5+; the major-bump cadence never carried the rename the old comment threatened). Tightened to '~> 0.5.0' for explicitness and amended the comment to describe what was actually verified. Verification: ea full suite 2036 examples, 0 failures, 37 pending. QeaToXmi specs: 130 examples, 0 failures.
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.
Summary
Two gemspec pin updates that unblock the contributor's Phase 2 transformer work and align with the actual API compatibility surface.
xmi:~> 0.5, >= 0.5.2→~> 0.6, >= 0.6.0The Phase 2 QeaToXmi transformer (on
feat/qeatoxmi-via-xmi-gem) depends on features added in xmi 0.6.0:Xmi::Uml::Slot,Xmi::Uml::OpaqueExpression,Xmi::Uml::InterfaceRealizationXmi::Uml::ValueSpecificationpolymorphic hierarchy (LiteralInteger,LiteralUnlimitedNatural,LiteralString)Xmi::Uml::BasepatternPackagedElement:visibility,is_abstract,is_leaf,is_active,classifier,interface_realization,slot,specificationaggregationandvisibilityonOwnedEndVerified by inspecting xmi 0.6.0 local checkout and published 0.6.1.
lutaml-uml:~> 0.5→~> 0.5.0Tightened the pessimistic pin for explicitness. Verified the entire bridge API surface used by
lib/ea/is intact in lutaml-uml 0.5.0 — all 23 constants the bridge references exist unchanged:Association, AssociationGeneralization, Cardinality, Constraint, DataType, Dependency, Diagram, DiagramLink, DiagramObject, Document, Enum, GeneralAttribute, Generalization, Instance, Operation, Package, Realization, TaggedValue, TopElement, TopElementAttribute, UmlClass, Validation, Value.
The prior comment claimed "1.x renamed these constants" — that rename never happened. Updated the comment to describe what was actually verified.
Verification
bundle installresolves cleanly against../xmi(0.6.0 local) and../lutaml-uml(0.5.0 local).Test plan
feat/qeatoxmi-via-xmi-gembranch (which depends on these features) rebases cleanly once this lands on main.