Skip to content

ci: clarify toolchain sync statuses and track Gradle major drift - #775

Open
dcalhoun wants to merge 4 commits into
trunkfrom
ci/android-toolchain-sync-table
Open

dcalhoun wants to merge 4 commits into
trunkfrom
ci/android-toolchain-sync-table

Conversation

@dcalhoun

@dcalhoun dcalhoun commented Oct 7, 2026 •

Copy link
Copy Markdown
Member

What?

Iterate on #645. Organize and clarify the information presented in WordPress-Android drift issues.

Why?

The first-ever issue was not the clearest upon first review.

How?

  • Improve table header labels
  • Prefix status cells with emoji to improve glanceability
  • Limit Gradle reports to major versions rather than listing minor/patch drifts that are not impactful
  • Avoid suggesting unnecessary downgrades

Testing Instructions

It's difficult to test this CI task. We will wait for the next occurrence.

Accessibility Testing Instructions

N/A, no user-facing changes.

Screenshots or screencast

N/A, no user-facing changes.


AI-generated details

Table readability. The drift issue's table had a blank header and relied on bold alone to tell blocking drift from a Gradle-only difference. The columns are now Tool | Status | GutenbergKit | WordPress-Android, with 🟢 In sync, 🟢 Compatible, and 🔴 Drifted.

Gradle major drift. The composite build runs this project's build scripts on WordPress-Android's Gradle wrapper, and Gradle removes deprecated APIs only in major releases. So:

  • A Gradle major mismatch now opens an issue; minor differences (which Dependabot creates routinely) show as 🟢 Compatible.
  • The issue marker records only Gradle's major, so a minor bump doesn't reopen a deferred issue.
  • The AGP note names WordPress-Android's Gradle only when ours is older, instead of implying a downgrade.
  • An unreadable Gradle wrapper now fails the run, like an unreadable catalog. Treating it as unknown could close a real Gradle issue as "back in sync" or reopen one deferred as not planned.

Testing. Ran the script with mocked upstream versions covering Kotlin-only, AGP drift with older/newer Gradle, Gradle major-only, and Gradle minor-only (no issue). With an open Gradle-only issue and an unparseable or unfetchable upstream wrapper, the run now fails and leaves the issue untouched; before the fix, it closed the issue.

🤖 Generated with Claude Code

dcalhoun and others added 2 commits October 7, 2026 13:53
The blank header left the column unexplained, and bold was the only cue
separating blocking drift from Gradle-only differences.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The composite build runs this project's build scripts on WordPress-Android's
Gradle wrapper, and Gradle removes deprecated APIs only in major releases.
A major mismatch can break that build, while minor differences, which
Dependabot creates routinely, cannot.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@dcalhoun dcalhoun added [Type] Build Tooling Issues or PRs related to build tooling Android labels Oct 7, 2026
@wpmobilebot

wpmobilebot commented Oct 7, 2026 •

Copy link
Copy Markdown

XCFramework Build

This PR's XCFramework is available for testing. Add the following to your Package.swift:

.package(url: "https://github.com/wordpress-mobile/GutenbergKit", branch: "pr-build/775")

Built from 6b4ceba

dcalhoun and others added 2 commits October 7, 2026 14:37
Gradle can now be the only drift, so reading an unreadable wrapper as
unknown closed a real Gradle issue as back in sync, and changed the marker
of one deferred as not planned. Failing the run leaves the issue untouched,
as an unreadable catalog already does.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The header only mentioned AGP, though Kotlin and now Gradle majors also
open issues.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@dcalhoun
dcalhoun marked this pull request as ready for review October 7, 2026 19:49
@dcalhoun
dcalhoun requested a review from a team as a code owner October 7, 2026 19:49
@dcalhoun
dcalhoun requested a review from oguzkocer October 7, 2026 19:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Android [Type] Build Tooling Issues or PRs related to build tooling

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants