[DO NOT MERGE] Validate workspace checksum publication - #86
Closed
Divyansh-db wants to merge 2 commits into
Closed
Divyansh-db wants to merge 2 commits into
Divyansh-db wants to merge 2 commits into
Conversation
Diagnostic snapshot only; not a release. The source snapshot predates the latest public release. The following commit isolates the workspace checksum publication change.
The fixed publication workflow changes only go.work.sum relative to the preceding pre-fix sync snapshot. SDK source, module manifests, module sums, and ignore rules are unchanged between the two sync outputs.
Divyansh-db
deleted the
Divyansh-db/workspace-checksum-sync-validation
branch
September 23, 2026 12:32
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.
What changes are proposed in this pull request?
DO NOT MERGE — diagnostic sync validation, not a release. This PR shows the actual published-tree output of regenerating workspace checksums during synchronization, with a pre-fix control to isolate its effect.
The source snapshot predates the latest public release, #85, so the full diff against
mainalso contains unrelated release and generated-code drift. The two commits separate these effects:domainsandsandbox), and five generated source files. The generated API drift includes removal of newer AI Gateway secret/service-credential variants.go.work.sumchanges, from 61 to 25 lines. It remains committed in the public repository. SDK source, public APIs, module manifests, module sums, workspace configuration, and ignore rules are identical to the pre-fix control.The checksum fix regenerates workspace sums against the public checkout's module sums instead of copying checksum state from a different workspace. The overall PR is not API-identical to current main, because it includes the first commit's pre-existing sync drift. No release preparation or version bump was run. Committed files retain the regular-file modes used by the publisher.
How is this tested?
main, both with and without the fix, using the same generated API input and Go toolchain. Comparing the two outputs identified onlygo.work.sumas different.git diff --checkpassed.These checks isolate the checksum fix's effect; they do not make the unrelated baseline rollbacks safe to merge.