chore(stlc): seal custom-code tracking files - #23
Conversation
|
stlc-bot seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
8f40d71 to
de380bc
Compare
✱ stlc build✅ go code · compare
✅ java code · compare
✅ kotlin code · compare
✅ node code · compare
✅ python code · compare
✅ ruby code · compare
Diagnostics:
|
| Level | Code | Message | Targets |
|---|---|---|---|
Python/PublishingWithoutOIDC | Publishing security issue: trusted publishing with OIDC is not enabled.#/targets/python/publish/pypi | python |
Build metadata
| Build | bd_76BmJKp2-spare-stripe |
| Timestamp | 2026-08-22T08:29:01.671Z |
| stlc | 20323f6 |
| Spec hash | a93053e99f21 |
| Config hash | 2cae45556ad3 |
This comment is auto-generated by stlc and is kept up to date as you push.
If you push new commits, re-run this workflow to update this comment.
Last updated: 2026-08-22 08:31:34 UTC
de380bc to
3ed5976
Compare
Automated by the stlc generate workflow.