Skip to content

chore(stlc): seal custom-code tracking files - #487

Merged
stainless-sync[bot] merged 1 commit into
mainfrom
stlc/seal-tracking
Nov 19, 2026
Merged

stainless-sync[bot] merged 1 commit into
mainfrom
stlc/seal-tracking

Conversation

@stainless-sync

@stainless-sync stainless-sync Bot commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

Automated by the stlc generate workflow: stlc build re-sealed custom code (after a spec change on main, or after absorbing custom code that landed on a staging repo out of band), updating the tracking files under stainless/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.

RetriggerView in GreptileConfidence Score: 5/5

This PR appears safe to merge.

Summary

Updates the commit references used to track custom code in the Python and TypeScript SDKs. No actionable issues found.

  • Python and TypeScript tracking records point to new sealed commits.

Reviews (1) · Last reviewed commit: "chore(stlc): seal custom-code tracking f..." · Reviewed by Greptile

@stainless-sync
stainless-sync Bot requested a review from a team as a code owner November 19, 2026 17:49
@stainless-sync
stainless-sync Bot enabled auto-merge (squash) November 19, 2026 17:49
@stainless-sync
stainless-sync Bot merged commit da53785 into main Nov 19, 2026
15 checks passed
@stainless-sync
stainless-sync Bot deleted the stlc/seal-tracking branch November 19, 2026 17:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant