chore: update agents to toolbox v1.3.0 - #30
Merged
Merged
Conversation
Repins the installed agent workflows from v1.2.0 to the current release. The workflow text is unchanged -- v1.3.0 only touched binding-xml-cd.yml -- so this alters no behaviour. What it changes is that the dashboard stops reporting this repository as a release behind, which it was, accurately, and with no failing run to show for it. Worth stating plainly because it is the whole reason the version chip exists: moving the v1 tag does nothing until a repository is recompiled against it. Nothing breaks in the meantime, which is exactly what makes the drift easy to accumulate.
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
1 participant
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.
Repinea los workflows de agente instalados de
v1.2.0a la release actual.El texto de los workflows no cambia —
v1.3.0solo tocóbinding-xml-cd.yml— así que esto no altera ningún comportamiento. Lo que cambia es que el dashboard deja de marcar este repo como una release por detrás, cosa que era cierta y no tenía ningún run en rojo que lo delatara.Merece decirlo claro porque es la razón entera de que exista el chip de versión: mover el tag
v1no hace nada hasta que un repo se recompila contra él. Entretanto no se rompe nada, que es justo lo que hace fácil acumular el desfase.🤖 Generated with Claude Code