chore: consume the bindings toolbox and declare the upstream manifest - #2
Merged
Merged
Conversation
Repoints CI and CD from evergine-standards@v2 to Evergine.Bindings@v1. The toolbox holds byte-identical copies of those reusable workflows -- the only edit is that they resolve their composite actions from the toolbox instead of evergine-standards -- so this is expected to be a no-op, verified by comparing the produced package against the run that preceded it. Adds binding.yml, recording where the upstream specification comes from, how it is fetched and what the generator writes. Until now this repository declared its upstream nowhere a machine could read it, which is what has kept the binding from being maintainable automatically. sync-standards.yml is deliberately left pointing at evergine-standards: distributing LICENSE, the icon and the shared build scripts is not the toolbox its job. evergine-standards@v2 is untouched and remains the rollback path.
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.
Fase 2: repunta CI y CD de
evergine-standards@v2al toolboxEvergine.Bindings@v1, y añadebinding.yml.Evidencia de que es un no-op
El toolbox contiene copias byte-idénticas de esos reusables; el único cambio al copiarlos fue repuntar sus
uses:internos a las acciones del propio toolbox. Verificado ya en dos repos comparando el.nupkgdel pipeline viejo contra el nuevo:Esos 147 bytes son siempre los mismos y son metadatos de build:
TimeDateStampdel PE, MVID, checksum del PDB y elInformationalVersion 1.0.0+<sha>. Cero diferencias de código.Aquí se ejecuta la misma comparación antes de mergear; si sale algo más, el PR no entra.
Qué NO cambia
sync-standards.ymlsigue apuntando aevergine-standards: distribuir LICENSE, el icono y los scripts debuild/scripts/no es cosa del toolbox. Los reusables originales tampoco se borran — son la vía de rollback.🤖 Generated with Claude Code