Repository navigation
gardener: upgrade task titles say plainly that we move to the new version - #2694
Merged
Merged
Conversation
|
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
Contributor
|
✅ agents import sizes: no significant changes ( |
agents
@cloudflare/ai-chat
@cloudflare/codemode
hono-agents
@cloudflare/shell
@cloudflare/think
@cloudflare/voice
@cloudflare/worker-bundler
commit: |
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.
The first
opencode-upgradePR was titled "chore(agents): test against opencode 2.1.4" (#2692), although it upgrades to 2.1.4. The tasks only pointed at #2594 and #2617, which are both Pi range changes, so the model had no example for a dev-pin-only upgrade.The title guidance now gives example titles (
chore(deps): upgrade opencode to <version>,fix(agents): support Pi <version>) and leaves the type and wording to the model, as long as the title plainly says we move to the new version. It is guidance, not a template..gardener/gardener.lock.jsonand the two workflows are regenerated.