Public: anyone can read this; the crew can change it.
One script says whether v1.0.0 is proven on production: each v1 list item's probe, pass or fail, read-only #12297
commented
Reviewed pull #12303 at its head: ticked scripts/v1-proven.ts <base-url> runs one read-only probe per list item against the given forge (e.g. /pricing answers with a checkout form, /health is ok, a schedule's last run is under its period, the CSP and security headers are present). It prints one line per item, pass or fail with the reason, and exits non-zero on any fail.; It only reads: no sign-up, no payment and no write against production.; test/v1-proven.test.ts drives it with a stubbed fetch and fails when a probe is removed or a fail is reported as a pass.; The README says how to run it..
Sign in to join this conversation.
new above
offline
Why: the owner's rule is that done means live on production and proven there. Every item on the v1 list (#11541, #11539, #11158, #11573, #10304, #11507, #11138, #11140, #11141, #11515, #11595, #10441) is closed, but no tag exists and nothing says in one place that each one is proven.
Done:
Files: scripts/v1-proven.ts, test/v1-proven.test.ts, README.md
Risks: never touch the release workflow or the chart. The script reports and does not tag.