Repository navigation
Lint the examples' ABAP with abaplint 2.120.75 - #16
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Te3BRpRpxNhZAYnrQL6Gdt
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
2 participants
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.
What changes
@abaplint/cli^2.120.73 -> ^2.120.75, lockfile regenerated withnpm install. The CI runsnpm run abaplintfrom the lockfile, so no workflow change.Why
CONVENTIONS §4: one abaplint version across the ecosystem; 2.120.75 is the current release (2026-10-12).
Checked
npm run lint,npm run format:check,npm run abaplint(0 issues, 11 files - no new findings),npm run build. CI:checkandbspgreen.Both
e2elegs are red exactly as on main: the same 14 freestyle tests (7 x UI5 1.136 / 1.71 - endpoint/params, query/fragment refused, restart(), invisible control, frontend load retried from the own endpoint) test embed-control 0.2.0 features, while npm still serves 0.1.1. They go green after embed-control 0.2.0 is published and pinned here; nothing in this change touches them.🤖 Generated with Claude Code
https://claude.ai/code/session_01Te3BRpRpxNhZAYnrQL6Gdt