Repository navigation
release: 1.1.0 + 1.1.1 — native-siblings UI pass, four sweep fixes, JitPack channel - #5
Merged
Merged
Conversation
Completes the redesign across the browser dashboard and the Android in-app inspector, then fixes what a full feature sweep of the running build found. Every list row in the dashboard rendered without its path or summary: the row's fixed columns totalled 318px inside a 320px list pane, leaving the flexible text column 2px. Widened the pane (440px default, 360px floor), tightened the row gap to 8px, and re-aligned the header cells. SDK health reported 0 published and 0 dropped events in every shipping build -- those counters live on an EventPipeline the runtime never instantiates, while real captures go through CaptureTimelineBridge. Wired both to the paths that actually run. Malformed request bodies answered 500 INTERNAL_ERROR; they now answer 400 or 415, so a 500 from this server means only a genuine server fault. Added POST /api/v1/mocks/enabled so the browser can re-enable mocking after the kill switch instead of requiring an app restart. Also removes internal task IDs, commit hashes, and design-doc references from shipped comments.
…ting The kill-switch section said mocks stay off "until re-enabled" without saying how -- and until POST /api/v1/mocks/enabled landed, the browser had no way to. Spells out both directions, why turning mocking on needs the mocks editing capability while turning it off does not, and how the global switch relates to per-rule toggles.
signAllPublications() wires a signing task unconditionally, and that task fails with "no configured signatory" rather than skipping when no key is present. Any build that is not the maintainer's release machine hit it -- including the publishToMavenLocal step CONTRIBUTING.md asks contributors to run, and any CI building from a clean checkout. Release signing is unchanged: verified 5 signatures with the key, 0 and a green build without. Also shortens comments added earlier in this branch to one or two lines, moving the reasoning here where it belongs.
Pins the JDK to 17 (JitPack defaults to 8; AGP 8.13 and jvmToolchain(17) both need 17) and skips Dokka, whose 31-module HTML generation is the slowest part of the build and produces nothing a JitPack consumer reads.
Central stays the supported channel; JitPack covers trying a branch or an unreleased fix. Verified against the real service rather than inferred: group is com.github.devconsole-android.DevConsole, and devconsole-api:feature~native-siblings-redesign-SNAPSHOT resolves with its transitives from a scratch consumer project. Also drops the install: block from jitpack.yml. An install: block replaces JitPack's default command rather than extending it, and that default already passes -xtest -xlint -xsignMavenPublication -- so the override would have run the full unit suite on every consumer-triggered build. Only the 31 library modules are served; gradle-plugin is an includeBuild and JitPack does not list it, so JitPack consumers name coordinates directly and give up the plugin's variant-policy check.
No SDK code changed; the public API is the 1.1.0 surface unchanged. 1.1.0 could not be built by anything lacking the maintainer's signing key, which ruled out contributors, clean-checkout CI, and JitPack alike. signAllPublications() registers both a signing task and the .asc files as publication artifacts. Without a key the task fails outright, and even when it is excluded (as JitPack does) the publication still demands .asc files nothing produced. Now applied only when a key is genuinely configured. Adds JitPack as a secondary channel for unreleased code, verified against the live service: group com.github.devconsole-android.DevConsole, and a scratch consumer resolved devconsole-api with its transitives.
Screenshots were captured before the native-siblings redesign and showed the old UI. Recaptured all three from the running 1.1.1 sample on a Pixel 6 plus the browser dashboard, added a network-inspector shot, and sized them to what the page actually displays at 2x. Total image weight drops from 1.1 MB to 560 KB despite adding one. Rewrites the prose in README, CONTRIBUTING, the docs index, the FAQ, and the three getting-started guides: one declarative opening sentence rather than a dense paragraph, shorter sentences, far fewer em-dash asides, and a contents strip for a README that had grown past 400 lines. Follows the shape the best-read Android library READMEs use. Also corrects CONTRIBUTING's stale '25-module' count to 31, matching settings.gradle.kts and the published artifact set, and moves the versioning policy out of the opening paragraph into its own section.
Shakibuzzaman3104
requested review from
maksudur03,
nur-shuvo,
rash-john and
zakaria5729
August 12, 2026 03:18
nur-shuvo
approved these changes
Aug 12, 2026
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.
Completes the native-siblings redesign across the browser dashboard and the Android in-app inspector, fixes four defects a full feature sweep of the running build turned up, and adds JitPack as a distribution channel.
Ships as 1.1.0 and 1.1.1. Plugin live on the Gradle Plugin Portal for both; JitPack live at 1.1.1; two Central deployments validated and awaiting the Publish click.
1.1.0 — the redesign and the sweep
Two additive methods on
DevConsoleRuntimeand one new REST route. No existing surface changed; theapiCheckdiff is additive only.Every dashboard list row rendered without its path or summary. A
.row's fixed columns — checkbox 24px, badge 54px, duration 74px, status 62px, flag 24px, five 12px gaps, 20px padding — totalled 318px inside a list pane whose default width was 320px. The flexible text column got 2px and clipped to nothing, so Network, Timeline, WebSockets, Push and Crashes all showed rows identifiable only by badge and duration. The detail pane had the full URL all along, which is what kept this from being obvious. Pre-existing, not a regression from this branch: the row geometry was byte-identical tomain.Fixed by widening the list column (440px default, 360px floor, still drag-resizable) and tightening the row gap to 8px — deliberately not by narrowing
.row-duration/.row-status, which was the first attempt and broke Timeline. Those slots are shared by five lists, and Timeline puts a full event type (socket.frame.text.received) where Network puts "198 ms".SDK health reported 0 published and 0 dropped events in every shipping build. Both counters live on
EventPipeline, which nothing in the runtime instantiates — real captures funnel throughCaptureTimelineBridge.emit(), andDevConsoleRuntime's ownSdkHealthonly ever trackedinitializationCountandstate. The dropped count is the consequential half: it is the SDK's only signal that capture lost data to buffer overflow, and it could never rise.A malformed request body answered
500 INTERNAL_ERROR. Form-body routes callreceiveParameters(), which throws when handed JSON or noContent-Type. That reached the catch-all boundary and came back as a server error, sending third-party client authors hunting an SDK bug for their own malformed request. Now400 VALIDATION_FAILED/415 UNSUPPORTED_MEDIA_TYPE. The dashboard was never affected — it sets the right content type on every one of these calls.InspectorPillButtonclipped its own label — the More screen's "Code" action rendered as "Cod".Added
POST /api/v1/mocks/enabled— the way back from the mock kill switch. The browser could disable all mocking but had no route to turn it back on, so resuming meant restarting the host app, while the Android inspector had a two-way toggle the whole time. The directions gate differently on purpose: turning mocking off stays ungated (falling back to real traffic is always allowed); turning it on requires the host'smocksediting capability.1.1.1 — buildable without the signing key, plus JitPack
No SDK code changed; the public API is the 1.1.0 surface unchanged.
1.1.0 could not be built by anything lacking the maintainer's signing key.
signAllPublications()registers both a signing task and the resulting.ascfiles as publication artifacts. With no key the task fails outright ("no configured signatory"); even when the task is explicitly excluded, the publication still demands.ascfiles nothing produced ("artifact file does not exist: …-release.aar.asc"). That broke three audiences at once: contributors running the exactpublishToMavenLocalcommandCONTRIBUTING.mdasks for, CI building from a clean checkout, and JitPack. Publications are now signed only when a key is genuinely configured — the key itself, not the id/password a maintainer's machine keeps between releases.docs/MAVEN_PUBLISHING.mdhas claimed since 1.0.0 that signing "no-ops when no key is configured"; that is now true rather than aspirational.JitPack added as a secondary channel for trying a branch or an unmerged fix; Central remains the supported one. Verified against the live service rather than inferred — group
com.github.devconsole-android.DevConsole, and a scratch consumer project resolveddevconsole-api:1.1.1with its transitives. Documented with its three real limits: the Gradle plugin is not served (it is anincludeBuild, absent from JitPack's module list, so consumers lose the variant-policy enforcement), artifacts are unsigned, and-SNAPSHOTrefs move.jitpack.ymlcarries only a JDK pin. Aninstall:block replaces JitPack's default command rather than extending it, and that default already passes-xtest -xlint -xsignMavenPublication— an override would have run the full unit suite on every consumer-triggered build.Also
Removed internal residue from shipped comments: task IDs (D1/D4/D7/E1/E2/E4/E6), commit hashes, and "design brief"/"verification report" pointers. Shortened the comments added on this branch to one or two lines, with the reasoning moved into commit messages.
Verification
Static gates alone caught none of the four 1.1.0 defects — they were found by running the thing.
apiCheck,ktlintCheck,detekt, full unit suite, and the gradle-plugin functional suite: green.verifyDevConsoleProtectedArtifacts.CRASHED) and ANR.Note for the reviewer
Two Central deployments are pending, 1.1.0 (
52fbfedc…) and 1.1.1 (f1818a81…). Recommendation is to publish 1.1.1 and drop 1.1.0 — functionally identical, and only 1.1.1 builds on every channel. If 1.1.0 is dropped, its changelog section should fold into 1.1.1 so the documented history matches Central. Plugin 1.1.0 is already live on the Portal and cannot be withdrawn; that is harmless, since 1.1.1'sDEFAULT_SDK_VERSIONpoints at the 1.1.1 coordinates.