Skip to content

fix(ci): unblock main — integration-test pom versions + regenerate metamodel-docs#106

Merged
dmealing merged 1 commit into
mainfrom
fix/main-ci-hygiene
Jun 29, 2026
Merged

fix(ci): unblock main — integration-test pom versions + regenerate metamodel-docs#106
dmealing merged 1 commit into
mainfrom
fix/main-ci-hygiene

Conversation

@dmealing

Copy link
Copy Markdown
Member

Clears two pre-existing red gates on main (both unblocking, unrelated):

1. release-gate (java) / (kotlin) — unresolvable parent POM

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 (Non-resolvable parent POM … 7.4.4-SNAPSHOT). Bumped both to 7.5.1-SNAPSHOT (no other stray 7.4.4 refs remain).

2. metamodel-docs-conformance — drifted fixture

The metamodel providers carry authored whenToUse descriptions that were never regenerated into fixtures/metamodel-docs/expected. Regenerated via scripts/regen-metamodel-docs.ts8 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 found fails only locally: 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. Green in clean CI — no code change.

🤖 Generated with Claude Code

…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
@dmealing
dmealing merged commit 2073597 into main Jun 29, 2026
29 checks passed
@dmealing
dmealing deleted the fix/main-ci-hygiene branch June 29, 2026 15:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant