Skip to content

chore(release): anotar 0.2.0 sin publicar el paquete - #181

Merged
Alexendros merged 1 commit into
mainfrom
chore/version-0.2.0
Oct 18, 2026
Merged

Alexendros merged 1 commit into
mainfrom
chore/version-0.2.0

Conversation

@Alexendros

@Alexendros Alexendros commented Oct 18, 2026 •

Copy link
Copy Markdown
Owner

Objetivo

Anotar la versión de código 0.2.0 de este hilo y dejar el tag v0.2.0 sin 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 en 0.1.0 (PRODUCER_VERSION, PIPELINE_VERSION).

Cambios

  • Versión 0.2.0 en el workspace Cargo, Tauri, package.json y el changelog. v0.1.0 no se mueve.
  • Un tag v* ya no dispara el AppImage. release.yml publica solo con workflow_dispatch y publish_package=true.
  • Hashes as-built de los ficheros tocados.

Fuera de alcance

Sin gh release create. Sin AppImage nuevo. Sin mover v0.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.0 como 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 --offline ve los crates en 0.2.0. tools/test_run_archify_diagrams.py sale 0. tools/check_product_naming.py sale 0. El tag se crea después del merge, sobre ese commit de main.

Documentación

CHANGELOG.md sección [0.2.0]. README separa versión de código y release binaria. packaging-release.md describe la espera del AppImage.

Checklist DoD

  • Versión 0.2.0 en manifiestos y changelog.
  • Tag anotado v0.2.0 en el merge de este PR, sin GitHub Release.
  • AppImage de 0.2.0: espera validación con tests.
  • SSD: 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.0 across the Cargo workspace, root/@archmaker/web package.json, and Tauri (tauri.conf.json / Cargo.lock) while v0.1.0 stays the only published AppImage and producer contracts (PRODUCER_VERSION / PIPELINE_VERSION) remain 0.1.0.

Release policy change: pushing a v* tag no longer runs the AppImage pipeline. release.yml adds a hold job for tag pushes (and dispatch without the flag) and gates package (and downstream sign/publish jobs) behind workflow_dispatch with publish_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.

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.
@cursor

cursor Bot commented Oct 18, 2026

Copy link
Copy Markdown

Bugbot couldn't run - usage limit reached

Bugbot 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)

@Alexendros
Alexendros merged commit 10cb1a6 into main Oct 18, 2026
24 checks passed
@Alexendros
Alexendros deleted the chore/version-0.2.0 branch October 18, 2026 21:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant