fix(ci): unblock main — integration-test pom versions + regenerate metamodel-docs#106
Merged
Conversation
…tamodel-docs Two pre-existing red gates on main, unrelated to each other, both unblocking: 1. release-gate (java)/(kotlin): server/java/integration-tests/pom.xml and integration-tests-kotlin/pom.xml pinned parent 7.4.4-SNAPSHOT, but the reactor is 7.5.1-SNAPSHOT — these two modules sit outside the root <modules> reactor, so the 7.5.0 release's `mvn versions:set` skipped them and the parent POM no longer resolves. Bump both to 7.5.1-SNAPSHOT. 2. metamodel-docs-conformance: the committed fixture had drifted — the metamodel providers carry authored `whenToUse` descriptions that were never regenerated into fixtures/metamodel-docs/expected. Regenerated (8 files, purely additive "When to use" guidance) via scripts/regen-metamodel-docs.ts. (A third local-only failure, cli detectPackageManager, is NOT a code bug: the impl correctly walks to the FS root for a lockfile, and a stray /tmp/package-lock.json on the dev box makes it resolve "npm" locally. Green in clean CI; no change needed.) Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LuZWKnWzYGVnESijL7uuky
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
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.
Clears two pre-existing red gates on
main(both unblocking, unrelated):1.
release-gate (java)/(kotlin)— unresolvable parent POMserver/java/integration-tests/pom.xmlandintegration-tests-kotlin/pom.xmlpinned parent7.4.4-SNAPSHOT, but the reactor is7.5.1-SNAPSHOT. These two modules sit outside the root<modules>reactor, so the 7.5.0 release'smvn versions:setskipped them and the parent POM no longer resolves (Non-resolvable parent POM … 7.4.4-SNAPSHOT). Bumped both to7.5.1-SNAPSHOT(no other stray7.4.4refs remain).2.
metamodel-docs-conformance— drifted fixtureThe metamodel providers carry authored
whenToUsedescriptions that were never regenerated intofixtures/metamodel-docs/expected. Regenerated viascripts/regen-metamodel-docs.ts— 8 files, purely additive (74 inserted lines, 0 deletions; all**When to use:**guidance). The conformance test passes after regen.Not fixed (not a bug)
cli › detectPackageManager › returns bun as default when no lockfile is foundfails only locally: the impl correctly walks to the FS root for a lockfile, and a stray/tmp/package-lock.jsonon the dev box makes it resolvenpm. Green in clean CI — no code change.🤖 Generated with Claude Code