Backport post_training CLI import fix to 0.3.x#306
Merged
ashwinb merged 2 commits intollamastack:release-0.3.xfrom Nov 20, 2025
Merged
Backport post_training CLI import fix to 0.3.x#306ashwinb merged 2 commits intollamastack:release-0.3.xfrom
ashwinb merged 2 commits intollamastack:release-0.3.xfrom
Conversation
…lamastack#293) Closes llamastack/llama-stack#3958 Co-authored-by: stainless-app[bot] <142633134+stainless-app[bot]@users.noreply.github.com>
ashwinb
approved these changes
Nov 20, 2025
Contributor
ashwinb
left a comment
There was a problem hiding this comment.
this looks good. I will look into enabling Mergify for all the llamastack repos. I thought we had it enabled.
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.
Description
I'm backporting this fix to
release-0.3.x, as discussed in #288.Pretty much I've cherry-picked the commit from #293 and then synced with
uv.Notes to the Reviewers/Maintainers
I see in the docs there are guidelines for releases. However I'd like some guidance if there are any required steps I should take.