Ashwin Bharambe fdb144f009 revert: feat(ci): use @next branch from llama-stack-client (#3593) ... Reverts llamastack/llama-stack#3576 When I edit Stainless and codegen succeeds, the `next` branch is updated directly. It provides us no chance to see if there might be something unideal going on. If something is wrong, all CI will start breaking immediately. This is not ideal. I will likely create another staging branch `next-release` or something to accomodate the special workflow that Stainless requires.		2025-09-29 10:41:04 -07:00
..
actions	revert: feat(ci): use @next branch from llama-stack-client (#3593)	2025-09-29 10:41:04 -07:00
ISSUE_TEMPLATE	docs: update documentation links (#3459)	2025-09-17 10:37:35 -07:00
workflows	chore(github-deps): bump actions/cache from 4.2.4 to 4.3.0 (#3577)	2025-09-29 10:04:58 +02:00
CODEOWNERS	chore: Add slekkala1 to codeowners (#2817)	2025-07-18 10:33:30 -07:00
dependabot.yml	fix(ci): dependabot update had a bug	2025-08-20 16:34:50 -07:00
PULL_REQUEST_TEMPLATE.md	chore: fix visible comments in pr template (#2279)	2025-05-27 15:42:33 +02:00
TRIAGERS.md	chore: Update TRIAGERS.md (#3186)	2025-08-18 10:23:51 -07:00