chore(stlc): seal custom-code tracking files - #456
Merged
Merged
Conversation
stainless-sync
Bot
force-pushed
the
stlc/seal-tracking
branch
9 times, most recently
from
September 28, 2026 12:28
b38a09d to
f083a5b
Compare
stainless-sync
Bot
force-pushed
the
stlc/seal-tracking
branch
from
September 29, 2026 00:46
f083a5b to
ac45a80
Compare
aringuyen3
approved these changes
Sep 29, 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.
Automated by the stlc generate workflow:
stlc buildre-sealed custom code (after a spec change onmain, or after absorbing custom code that landed on a staging repo out of band), updating the tracking files understainless/custom-code/. Merging brings the config repo in sync with the SDK repos. Safe to merge — tracking-files-only commits are skipped by this workflow, so it won't trigger another build.The PR appears safe to merge.
Summary
The PR reseals the Python and TypeScript custom-code tracking records with new base and integrated revision IDs. The records still track
main, while tracking-only changes are skipped by the SDK generation workflow.Diagram
sequenceDiagram participant PR as Tracking-file PR participant Repo as Config repository participant Workflow as stlc generate workflow participant SDK as SDK staging repository participant STLC as stlc build PR->>Repo: Update base and integrated SHAs Repo->>Workflow: Merge tracking-only commit Workflow-->>Workflow: Skip tracking-only commit Note over Workflow,SDK: On a later eligible build Workflow->>SDK: Check integrated SHA against staging main SDK-->>Workflow: Return commit history Workflow->>STLC: Run build with tracking records STLC->>SDK: Replay custom-code diff STLC->>Repo: Seal updated tracking recordsReviews (11) · Last reviewed commit: "chore(stlc): seal custom-code tracking f..."