Ecosystem review: catalogue contract gate, current pins, corrected prose - #66
Merged
Merged
Conversation
0.6.0 and 0.6.1 reached npm on 2026-08-30 (16:48 / 17:47 UTC); the weekly bump-linter cron would have delivered them next Monday - the same cadence that merged 0.4.0 and 0.4.1 within minutes of their publish on 2026-08-25 (PRs #60/#61). This is that bump a few days ahead of the cron, with the same gate: abap2ui5lint ran green over the full catalogue (32 files, render included, no findings) on the matched pair. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BuzK8EC2CdQ5PJ6YCdfKJc
scripts/check-catalogue-contract.mjs is the byte-identical copy of abap2UI5/.github/shared/check-catalogue-contract.mjs (check:shared gates it, sync-shared pulls it): it pins the published shape of this repository's catalogue.json - the interface mcp-server, the vscode-extension and the playground parse from GitHub main - including the deliberate divergences between the three sample repositories. Wired into the catalogue check so it runs wherever the catalogue is verified. Green against the current catalogue. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BuzK8EC2CdQ5PJ6YCdfKJc
Same move as in samples: the pin trailed the family at 1.143.0 and the @abaplint/cli lock at 2.120.24; both move to the current state (1.144.0, 2.120.39) a few days ahead of their scheduled bumps. The full check chain ran green - abaplint against the 1.144.0 clone, the abap2UI5 linter with render, every generator and catalogue check. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BuzK8EC2CdQ5PJ6YCdfKJc
The chain-layout comment named npm run check:chains and scripts/chain-format.mjs - both gone since the linter's chain-house-layout took the job over; it now names that rule. The overview-app comment claimed the app is generated by npm run overview - this repository has neither the script nor a generator: the overview is hand-written and held to its shape by scripts/check-overview.mjs, which is what the comment says now. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BuzK8EC2CdQ5PJ6YCdfKJc
abap2UI5 sets timeout-minutes on all of its jobs and most repositories follow; this one had jobs without a ceiling, so a hung run could hold its slot (and in the publish workflows, the downstream pipeline) for GitHub's six-hour default. Values follow the job's real budget. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BuzK8EC2CdQ5PJ6YCdfKJc
'Every check below has a workflow, and every workflow is a step of npm run check - the two lists are the same list' was disproved by its own table in both directions: create-package-branches and deploy-web are build-and-publish jobs that are not steps of npm run check, and check-framework-pin and check-family-nav are steps with workflows the table did not list. The two missing rows are in, and the claim is scoped to the check-* rows with the build jobs named as what they are. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BuzK8EC2CdQ5PJ6YCdfKJc
Re-lands the badge refresh the check-abap2UI5 workflow pushed onto this branch (91 -> 111 rules passed, following the linter bump below): a head pushed by github-actions[bot] leaves every workflow run waiting for manual approval, so the same change lands again under a human account. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BuzK8EC2CdQ5PJ6YCdfKJc
oblomov-dev
force-pushed
the
claude/repo-structure-analysis-6t4t6x
branch
from
August 31, 2026 02:04
e34f76b to
3dfd2b3
Compare
Merged
5 tasks
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.
Six commits from the 2026-08-30 ecosystem review:
scripts/check-catalogue-contract.mjs— byte-identical copy of the new shared checker (source:abap2UI5/.github/shared/), pinning this repository's publishedcatalogue.jsonshape; wired intocheck:catalogue.@abap2ui5/linter+@abap2ui5/render-runtimemove from the ^0.4.1 line (which could never reach 0.5.x/0.6.x) to ^0.6.1 — 0.6.0/0.6.1 reached npm on 2026-08-30, this is the Monday cron's move a few days early, same gate (32 files, render included, no findings). Framework pin 1.143.0 → 1.144.0,@abaplint/clilock → 2.120.39.check:chains/chain-format.mjsor claim the hand-written overview app is generated; the README workflow table's "the two lists are the same list" claim is scoped to what is actually true (the two missingcheck-*rows are in, the build jobs are named as such); timeout ceiling on the deploy job.Validated: full
npm run checkchain green on the new pins.🤖 Generated with Claude Code
https://claude.ai/code/session_01BuzK8EC2CdQ5PJ6YCdfKJc
Generated by Claude Code