<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-docs-legacy-snapshot.git/.github/workflows/deploy.yml, branch production</title>
<subtitle>Frozen static snapshot of docs.vyos.io EOL versions (1.2 crux, 1.3 equuleus) served via Cloudflare Workers — IS-572 (mirror of https://github.com/vyos/vyos-docs-legacy-snapshot.git)
</subtitle>
<id>https://git.amelek.net/vyos/vyos-docs-legacy-snapshot.git/atom?h=production</id>
<link rel='self' href='https://git.amelek.net/vyos/vyos-docs-legacy-snapshot.git/atom?h=production'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-docs-legacy-snapshot.git/'/>
<updated>2026-07-10T14:02:09+00:00</updated>
<entry>
<title>docs-infra: CR review fixes — wget flag form, PDF validation, R2 seed short-circuit, build-then-swap</title>
<updated>2026-07-10T14:02:09+00:00</updated>
<author>
<name>Yuriy Andamasov</name>
<email>yuriy@vyos.io</email>
</author>
<published>2026-07-10T14:02:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-docs-legacy-snapshot.git/commit/?id=9b6c5d1ecc2eddd44db0beb556711a8be8f65f73'/>
<id>urn:sha1:9b6c5d1ecc2eddd44db0beb556711a8be8f65f73</id>
<content type='text'>
🤖 Generated by [robots](https://vyos.io)
</content>
</entry>
<entry>
<title>docs-infra: PDF secured before deploy; honest UA comment; concurrency guard</title>
<updated>2026-07-10T13:42:18+00:00</updated>
<author>
<name>Yuriy Andamasov</name>
<email>yuriy@vyos.io</email>
</author>
<published>2026-07-10T13:42:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-docs-legacy-snapshot.git/commit/?id=caa255c89013a005c448958aae6d8a355b762c6c'/>
<id>urn:sha1:caa255c89013a005c448958aae6d8a355b762c6c</id>
<content type='text'>
Review fixes on the R2-upload step: (1) the PDF fetch+validate+upload now
runs BEFORE the Worker deploy — fail fast, so a promote=true run can never
leave production HTML pointing at a stale/missing legacy PDF (spec §5
site+PDF consistency); (2) the comment no longer misattributes the
browser-UA/retry flags to snapshot.sh's PDF curl (which has neither) —
they're defensive additions grounded in the wget crawl's CF-challenge
precedent; (3) workflow-level concurrency group legacy-deploy with
cancel-in-progress: false for fleet parity.

🤖 Generated by [robots](https://vyos.io)
</content>
</entry>
<entry>
<title>docs-infra: upload legacy 1.3 PDF to R2 (apex fallback source)</title>
<updated>2026-07-10T13:29:38+00:00</updated>
<author>
<name>Yuriy Andamasov</name>
<email>yuriy@vyos.io</email>
</author>
<published>2026-07-10T13:29:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-docs-legacy-snapshot.git/commit/?id=b59bef90546d0a39332aa0492ec1e781e5253a32'/>
<id>urn:sha1:b59bef90546d0a39332aa0492ec1e781e5253a32</id>
<content type='text'>
r2-staging/ (tools/snapshot.sh's local output) is gitignored, so CI has no
copy of the file to upload. Re-fetch it from the pre-sunset RTD source
directly (same URL/UA/retry precedent as snapshot.sh's PDF curl), sanity
-check the size against the known 25-35 MiB band, then push it to the
shared vyos-docs-artifacts R2 bucket the apex Worker's DOCS_PDFS binding
reads. Idempotent overwrite; runs on every dispatch of this workflow.

🤖 Generated by [robots](https://vyos.io)
</content>
</entry>
<entry>
<title>docs-infra: legacy Worker deploy workflow (manual dispatch, candidate/promote)</title>
<updated>2026-07-10T13:17:54+00:00</updated>
<author>
<name>Yuriy Andamasov</name>
<email>yuriy@vyos.io</email>
</author>
<published>2026-07-10T13:17:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-docs-legacy-snapshot.git/commit/?id=3f10e60b8bc7c19746aa15ac0bf24c24014e777c'/>
<id>urn:sha1:3f10e60b8bc7c19746aa15ac0bf24c24014e777c</id>
<content type='text'>
Manual workflow_dispatch deploys the legacy snapshot tree as a Cloudflare
Worker. Checks out this repo (snapshot/) plus vyos-documentation@rolling
(workers/branch/wrangler.legacy.jsonc source), copies the snapshot into
dist/assets, and deploys via wrangler. Default dispatch targets the
vyos-docs-legacy-candidate name/canary env; promote=true targets the
production vyos-docs-legacy name/env. Not run in this session — the actual
dispatch is an operator/cutover-sequenced step per the task brief.

🤖 Generated by [robots](https://vyos.io)
</content>
</entry>
</feed>
