Skip to content

ci: verify Gradle plugin resolution fix (validation only, do not merge) - #7

Closed
Klaas-Ritense wants to merge 1 commit into
mainfrom
ci/verify-plugin-resolution
Closed

ci: verify Gradle plugin resolution fix (validation only, do not merge)#7
Klaas-Ritense wants to merge 1 commit into
mainfrom
ci/verify-plugin-resolution

Conversation

@Klaas-Ritense

Copy link
Copy Markdown
Member

Validation-only PR. No file changes — this is an empty commit.

main already carries the plugin-resolution fix (b525091). The problem: publish-backend.yaml filters on paths: backend/**, so a root-level settings.gradle.kts change never triggers the workflow that runs ./gradlew :backend:plugin:test. CodeQL only covers actions and javascript-typescript, so it never invokes Gradle either. The fix therefore landed on main without any CI run exercising it.

pr-checks.yaml has no path filter, so this PR runs :backend:plugin:test against main's current state and confirms cn.lalaki.central resolves.

To be closed, not merged, once green.

Validation only -- carries no file changes. main already contains the
plugin-resolution fix (b525091); pr-checks.yaml has no path filter, so
this PR runs :backend:plugin:test against it. To be closed, not merged.
@Klaas-Ritense

Copy link
Copy Markdown
Member Author

Green — Backend tests passed in 2m24s against main with the fix. Closing unmerged as planned; carried no file changes.

@Klaas-Ritense
Klaas-Ritense deleted the ci/verify-plugin-resolution branch August 20, 2026 10:25
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