Skip to content

docs: require release tags #32

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
max23468 merged 1 commit into from
May 31, 2026
Merged

docs: require release tags #32

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -114,7 +114,7 @@ Il deploy operativo MVP passa da GitHub Actions:
- successo anche se vengono trovati cambiamenti;
- fallimento se c'è un errore tecnico o se un'email necessaria non parte.

Tag e GitHub Release sono ammessi solo per release del tool o della dashboard
Tag Git `vX.Y.Z` e GitHub Release sono obbligatori per release del tool o della dashboard
secondo `docs/decisions/0003-tag-e-github-release.md`. Non crearli per semplici
scan, report, snapshot o aggiornamenti data-only.

Expand Down
2 changes: 1 addition & 1 deletion docs/CONTEXT.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@
- Workflow operativo: `.github/workflows/sentinel.yml`.
- Dashboard online: app Next.js in `app/`, proxy Basic Auth in `proxy.ts`,
payload Blob pubblicato con `sentinel publish-dashboard`.
- Release versionate: tag `vX.Y.Z` e GitHub Release solo per release del tool o
- Release versionate: tag `vX.Y.Z` e GitHub Release obbligatori per release del tool o
della dashboard, secondo ADR `docs/decisions/0003-tag-e-github-release.md`.

## Ultimo contesto utile
Expand Down
2 changes: 1 addition & 1 deletion docs/DECISIONS_PENDING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ Decisioni chiuse:

- Release versionate: chiusa con
`docs/decisions/0003-tag-e-github-release.md`. Sentinel resta runtime
operativo continuo; tag e GitHub Release valgono solo per release del tool o
operativo continuo; tag e GitHub Release sono obbligatori per release del tool o
della dashboard, non per scan/report/output data-only.

- Runtime operativo dopo la pausa Actions: chiusa con riavvio e verifica del
Expand Down
2 changes: 1 addition & 1 deletion docs/TOOLCHAIN.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -69,7 +69,7 @@ Questa pagina descrive runtime, comandi e guardrail effettivi di Sentinel.
- Il deploy della dashboard web passa da Vercel CLI e non richiede GitHub
Actions.
- Non esiste VPS.
- Tag e GitHub Release sono ammessi solo per release del tool o della dashboard
- Tag Git `vX.Y.Z` e GitHub Release sono obbligatori per release del tool o della dashboard
secondo ADR `docs/decisions/0003-tag-e-github-release.md`.
- Il workflow esegue scan, genera `reports/dashboard.html` e può committare
`data/`, `snapshots/` e `reports/`.
Expand Down
4 changes: 2 additions & 2 deletions docs/decisions/0003-tag-e-github-release.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,13 +18,13 @@ GitHub Actions.

Sentinel mantiene il runtime operativo continuo come comportamento predefinito.

Tag Git e GitHub Release si usano solo quando viene rilasciata una nuova
Tag Git e GitHub Release sono obbligatori quando viene rilasciata una nuova
versione del tool o della dashboard:

- la source of truth della versione è `package.json`;
- il tag Git deve avere formato `vX.Y.Z` e corrispondere esattamente alla
versione in `package.json`;
- la GitHub Release, se creata, parte da quel tag e descrive cambiamenti del
- la GitHub Release deve essere creata da quel tag e descrivere cambiamenti del
tool o della dashboard, non semplici output di scansione;
- scan, report, baseline, snapshot e aggiornamenti di dashboard data-only non
creano tag e non creano GitHub Release;
Expand Down
Loading