chore(github-deps): bump llamastack/llama-stack from 76bcb6657de312160c726fbe069275cd5537b702 to c518b35a65f8bd1370c938c688dfb2e2a00cceab

[dependabot]

Bumps llamastack/llama-stack from 76bcb66 to c518b35.

Changelog

Sourced from llamastack/llama-stack's changelog.

Llama Stack Release Process

This document outlines the release process for Llama Stack, providing predictability for the community on feature delivery timelines and release expectations.

Release Schedule

Llama Stack follows Semantic Versioning with three release streams:

Release Type	Cadence	Description
Major (X.0.0)	Every 6-8 months	Breaking changes, major new features, architectural changes
Minor (0.Y.0)	Monthly	New features, non-breaking API additions, significant improvements
Patch (0.0.Z)	Weekly	Bug fixes, security patches, documentation updates

Version Numbering

Releases follow the X.Y.Z pattern:

• X (Major): Incremented for breaking changes or significant architectural updates
• Y (Minor): Incremented for new features and non-breaking enhancements
• Z (Patch): Incremented for bug fixes and minor improvements

Release Candidates

For minor and major releases, release candidates (RC) are published before the final release:

• Format: vX.Y.ZrcN (e.g., v0.4.0rc1, v0.4.0rc2)
• Python RC packages are published to test.pypi for community testing
• Multiple RCs may be issued until the release is stable

Branching Strategy

• main: Active development branch, always contains the latest code
• release-X.Y.x: Release branches for each minor version (e.g., release-0.3.x, release-0.4.x)
• Patch releases are made from release branches
• Critical fixes are backported from main to active release branches using Mergify

Milestone Management

Tracking Work

• Issues only: Add only issues to milestones, not PRs (avoids duplicate tracking)
• Milestone creation: Create milestones for each planned minor and major release
• Small fixes: Quick-landing PRs for small fixes don't require milestone tracking

Release Criteria

A version is released when:

1. All issues in the corresponding milestone are completed, OR
2. Remaining issues are moved to a future milestone with documented rationale

Triaging

... (truncated)

Commits

• c518b35 fix: update together to work with latest api.together.xyz service (circa feb ...
• 1c8ad0e chore: revert "fix: disable together banner (#4517)" (#4856)
• a473f5b chore(test): add test to verify responses params make it to backend service (...
• 730f3b3 fix: Exclude null 'strict' field in function tools to prevent OpenAI … (#4795)
• 54a4818 chore: bump fallback version to 0.5.1 (#4846)
• f2eed5f docs: add technical release steps and improvements to RELEASE_PROCESS.md (#4792)
• c1fb485 chore: reduce uses of models.llama.datatypes (#4847)
• a27363d fix: Arbitrary file write via a non-default configuration (#4844)
• 8c40307 feat!: improve consistency of post-training API endpoints (#4606)
• 04ba9f5 chore: update convert_tooldef_to_openai_tool to match its usage (#4837)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)