Skip to content

chore: update agents to the current toolbox release - #9

Open
evergine-bindings-automation[bot] wants to merge 1 commit into
mainfrom
chore/toolbox-update
Open

chore: update agents to the current toolbox release#9
evergine-bindings-automation[bot] wants to merge 1 commit into
mainfrom
chore/toolbox-update

Conversation

@evergine-bindings-automation

Copy link
Copy Markdown
Contributor

Repins the installed agentic workflows to the current
v1 of EvergineTeam/Evergine.Bindings.

Installed 0afb85d204706b58bb4b0aee8127be4a55ce460e
Current ace4e8d477b877e973e5c748a81aff8f24c6fe42

Moving the toolbox tag does not update anything on its own — a
repository keeps the commit it was compiled against until something
recompiles it, and nothing fails in the meantime. That is what makes
the drift easy to accumulate and invisible without looking.

Review the diff as you would any workflow change: the compiled
.lock.yml files are generated, but the .md frontmatter is not.

Repins the installed agentic workflows from
0afb85d204706b58bb4b0aee8127be4a55ce460e to
ace4e8d477b877e973e5c748a81aff8f24c6fe42 and recompiles.
@evergine-bindings-automation evergine-bindings-automation Bot added the agent:toolbox-update Pull request repinning the installed agents label Aug 10, 2026
@github-actions

Copy link
Copy Markdown
Contributor

API gate: additive

Every symbol that existed still exists, unchanged. Nothing that compiled before stops compiling.

Target framework Added Removed
net10.0 +0 -0

Enum and constant values are part of the measured surface: a renumbering keeps compiling and sends the wrong number to the driver, so it counts as a removal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

agent:toolbox-update Pull request repinning the installed agents

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant