Repository navigation
chore(release): anotar 0.2.0 sin publicar el paquete - #181
Merged
Merged
Conversation
El tag v0.2.0 registra la versión de código desde v0.1.0. La GitHub Release del AppImage espera validación con tests.
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: 7b9137fb-be80-408d-9721-0bcddf3d5480) |
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.
Objetivo
Anotar la versión de código
0.2.0de este hilo y dejar el tagv0.2.0sin publicar la release de paquete.IDs trazados
Sin requisito nuevo. Canal de paquete: DEC-011 /
docs/10-delivery/packaging-release.md. El contrato de productor sigue en0.1.0(PRODUCER_VERSION,PIPELINE_VERSION).Cambios
0.2.0en el workspace Cargo, Tauri,package.jsony el changelog.v0.1.0no se mueve.v*ya no dispara el AppImage.release.ymlpublica solo conworkflow_dispatchypublish_package=true.Fuera de alcance
Sin
gh release create. Sin AppImage nuevo. Sin moverv0.1.0. Sin fusionar #178. Sin ISO, sin USB y sin escribir el SSD. P6 y F7 no se marcan passed.Contratos/migraciones
Ninguno. Los ejemplos y pruebas que citan
0.1.0como versión de target o de productor no cambian.Seguridad/privilegios
El workflow de release sigue deny-by-default en el tag: el job de empaquetado no corre.
Accesibilidad/visual
Sin cambios de cara.
Pruebas y evidencias
cargo metadata --locked --offlineve los crates en0.2.0.tools/test_run_archify_diagrams.pysale 0.tools/check_product_naming.pysale 0. El tag se crea después del merge, sobre ese commit demain.Documentación
CHANGELOG.mdsección[0.2.0]. README separa versión de código y release binaria.packaging-release.mddescribe la espera del AppImage.Checklist DoD
0.2.0en manifiestos y changelog.v0.2.0en el merge de este PR, sin GitHub Release.0.2.0: espera validación con tests.not_run.Note
Medium Risk
Changes when the release workflow builds and publishes supply-chain artifacts; tags are deny-by-default until manual
publish_package=true.Overview
Bumps the code identity to
0.2.0across the Cargo workspace, root/@archmaker/webpackage.json, and Tauri (tauri.conf.json/Cargo.lock) whilev0.1.0stays the only published AppImage and producer contracts (PRODUCER_VERSION/PIPELINE_VERSION) remain0.1.0.Release policy change: pushing a
v*tag no longer runs the AppImage pipeline.release.ymladds aholdjob for tag pushes (and dispatch without the flag) and gatespackage(and downstream sign/publish jobs) behindworkflow_dispatchwithpublish_package=true, so a version tag only annotates code until a validated AppImage is ready.Docs and traceability:
CHANGELOG.md[0.2.0], README (code vs binary release layers),packaging-release.md, and updated as-built manifest hashes for touched files.Reviewed by Cursor Bugbot for commit 9245633. Configure here.