Regenerate workspace checksums from current source - #87
Draft
Divyansh-db wants to merge 1 commit into
Draft
Divyansh-db wants to merge 1 commit into
Divyansh-db wants to merge 1 commit into
Conversation
Refresh the published workspace sums and the generated feature backfill comment. SDK APIs, executable code, module requirements, versions, and ignore rules are unchanged.
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?
Regenerate workspace checksums from a fresh full SDK sync after updating the source branch to current master. This replaces the stale-snapshot validation in #86.
The diff against public
maincontains exactly two files:go.work.sum: regenerated workspace checksums, from 61 to 25 lines; the file remains committed.features/v1/model.go: generated documentation cleanup forBackfillFeaturesRequest.BackfillRanges.No public API signatures, executable code, module requirements, release versions, workspace configuration, or ignore rules change. This is a sync-validation draft, with no release preparation or version bump.
How is this tested?
mainat1e4b71bcd4f7a595f6cb8b2aead9f9f7ab184bb3.git diff --checkpassed.