chore: consume the bindings toolbox and declare the upstream manifest - #23
Merged
Conversation
Repoints CI and CD from evergine-standards@v2 to Evergine.Bindings@v1. The toolbox holds byte-identical copies of those reusable workflows, so this is a no-op verified by comparing the produced package against the run that preceded it. Adds binding.yml. Writing it turned up something worth recording rather than fixing here: the header is taken from Emscripten 3.1.56, while the README states the .NET SDK is coupled to Emscripten 3.1.36 for .NET 10. Whether that is intentional, stale documentation, or a real mismatch needs a person to decide, so the manifest marks the ref as frozen -- tooling may report that a newer Emscripten exists but must not propose the bump. sync-standards.yml is deliberately left pointing at evergine-standards. 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 al toolbox
Evergine.Bindings@v1y añadebinding.yml.Evidencia acumulada de que es un no-op
Siete repos verificados hasta ahora comparando el
.nupkgdel pipeline viejo contra el nuevo. En todos: mismo conjunto de entradas, tamaños idénticos, y el ensamblado difiere solo en metadatos de build.Siempre ~150 bytes con independencia del tamaño del ensamblado, y siempre los mismos:
TimeDateStampdel PE, MVID, checksum del PDB y elInformationalVersion 1.0.0+<sha>. Cero diferencias de código.Hallazgo al escribir el manifiesto
El header viene de Emscripten 3.1.56, pero el README dice que el .NET SDK va acoplado a 3.1.36 para .NET 10. No lo resuelvo aquí: puede ser intencionado, documentación vieja o un desajuste real. El manifiesto deja
refcongelado y lo documenta, que es lo que debe hacer — sacar la pregunta a la luz, no contestarla por su cuenta.🤖 Generated with Claude Code