Repository navigation
chore(stlc): seal custom-code tracking files - #465
Open
stainless-sync[bot] wants to merge 1 commit into
Open
stainless-sync[bot] wants to merge 1 commit into
stainless-sync[bot] wants to merge 1 commit into
Conversation
stainless-sync
Bot
force-pushed
the
stlc/seal-tracking
branch
27 times, most recently
from
October 8, 2026 18:21
bba07bc to
44e898c
Compare
stainless-sync
Bot
force-pushed
the
stlc/seal-tracking
branch
from
October 9, 2026 06:30
44e898c to
8f2342d
Compare
stainless-sync
Bot
force-pushed
the
stlc/seal-tracking
branch
29 times, most recently
from
October 19, 2026 06:36
c67009c to
0472131
Compare
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 based on the available evidence.Summary
The PR updates the Python custom-code tracking record after a re-seal so the config repository can sync with the SDK repositories.
Reviews (81) · Last reviewed commit: "chore(stlc): seal custom-code tracking f..." · Reviewed by Greptile