Skip to content

Regenerate workspace checksums from current source - #87

Draft
Divyansh-db wants to merge 1 commit into
mainfrom
Divyansh-db/workspace-checksum-fresh-sync
Draft

Divyansh-db wants to merge 1 commit into
mainfrom
Divyansh-db/workspace-checksum-fresh-sync

Conversation

@Divyansh-db

@Divyansh-db Divyansh-db commented Sep 23, 2026 •

Copy link
Copy Markdown

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 main contains 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 for BackfillFeaturesRequest.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?

  • Ran the full sync into a fresh checkout of public main at 1e4b71bcd4f7a595f6cb8b2aead9f9f7ab184bb3.
  • Go tests across all 92 workspace modules passed with the examples build tag, race detector, and readonly module manifests. Tests ran in a separate copy to preserve the exact sync output.
  • Sync regression and vendor-consistency tests passed.
  • Go formatting and git diff --check passed.

Refresh the published workspace sums and the generated feature backfill comment. SDK APIs, executable code, module requirements, versions, and ignore rules are unchanged.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant