chore: reconcile production->development divergence (content sync) (#63)

2026-06-07T15:28:37+00:00

* returned lost sentrium.svg image * changed phone number to valid one * Remove explicit branch reference from the checkout action * Use a variable for branch checkout * Add an option to take the branch from the inputs * Update the release status for 1.4.0 GA * [release status] Do not render security advisory table headers if there are no advisories * added one month date of expiration for user's cookie consent (cherry picked from commit 7863f97ba712fe6e7801eee8c29c955000b6560a) * minisign: T6610: update the rolling release signing key (cherry picked from commit c471f8ee728dd5a0b599f8ed61518716cfba37b1) * Update to checkout@v4 (cherry picked from commit f5934afca8a7d790c15e77e19ce4a1d651411b07) * nightly-builds: rename GitHub repo (cherry picked from commit 2f993bbe13e083efc65f7b05825f94f05fcfb615) * moved deployment to AWS Amplify * Update README.md * added a new step to check Amplify build status [no ci] * fixed access to variables [no ci] * trigger rebuild * Remove the mention of LTS source code being public It's now available only to people who legitimately acquired binaries, as per the GPL requirements * Add an anchor to the stream release link * Remove the legacy LTS application form We'll encourage everyone to get VyOS Stream or rolling release * Remove the mention of oudated support subscriptions * Change the wording from "sofrware access subscription" to just "subscription" * Remove Sentrium from the footer since it no longer exists as an independent company * Update the hsforms library to v4 * Revert "Update the hsforms library to v4" This reverts commit 0b0916da4f60f58fc9ed988d97e35769bffc222b. * Add links to VyOS Stream 2025-Q2 * Add VyOS Stream 2025.11 * cosmetic bug: Fix image allign (cherry picked from commit e8107f90846c7256184983a42a0fc8a3f5f36c66) * Update the release status for 1.4.4 * Remove now-EOLd 1.3.x from release status * Add VyOS Stream 2026.03 * Ignore .soupault-cache/ build artifact directory Soupault 5.x writes incremental build caches under `.soupault-cache/` in the repo root. The directory appears as untracked after any local build and `gh pr create` warns about it. Add it to .gitignore alongside `build/*` so clean checkouts stay clean. Co-Authored-By: Claude Opus 4.7 * ci: T8943: retarget main.yml push trigger main->development (rollout 1c) (#59) The default-branch reorg renamed main->development (production is now the default). main.yml deploys by mirroring github.ref_name to an AWS Amplify branch, so the dead main trigger is replaced with development. The Amplify app has a matching development branch (operator-confirmed). amplify/production trigger entries left unchanged. Tracking: T8943 * ci: T8947: point CLA check at vyos-cla-signatures@production (rollout 1c follow-up) (#60) Rollout 1c (IS-503) renamed vyos-cla-signatures' default branch to `production`, but cla-check.yml still called the reusable at @current. The `current` branch of vyos-cla-signatures has diverged from `production` and its copy of cla-reusable.yml writes signatures to `branch: 'current'` — so CLA signatures from this repo's PRs were landing on the stale `current` branch instead of `production`. Flip the ref to @production (whose cla-reusable.yml writes to `branch: 'production'`). Note: migrating/reconciling signatures already accumulated on vyos-cla-signatures@current (and whether to delete that branch) is a separate operator decision tracked in IS-504 / T8947. 🤖 Generated by [robots](https://vyos.io) * T8943: ci: remove dead amplify branch from CI push trigger (#61) The amplify branch no longer exists in this repo; the trigger entry is unreachable. main was already retargeted to development in #59 (rollout 1c). This completes the trigger cleanup so the list matches real branches. 🤖 Generated by [robots](https://vyos.io) --------- Co-authored-by: bogdankol <68349689+bogdankol@users.noreply.github.com> Co-authored-by: Daniil Baturin Co-authored-by: Daniil Baturin Co-authored-by: Christian Breunig Co-authored-by: Yevhen Bondarenko Co-authored-by: lemeshovich <17667824+lemeshovich@users.noreply.github.com> Co-authored-by: Viacheslav Hletenko Co-authored-by: Claude Opus 4.7

Address Copilot review: preconnect order + staging-gate cookies-policy script

2026-04-18T10:09:09+00:00

Two fixes flagged by the Copilot reviewer on #35: 1. Preconnect hints were appended to the end of while the GTM loader is prepended to the top, so GTM's async script creation fired before the browser ever saw the preconnect tags — they provided no benefit. Switches insert-preconnect-hints to prepend_child and adds `after = "insert-google-tag-manager-head"` so the widget runs after GTM and its prepend pushes GTM down to position 1. Result: preconnects land at the top of , ahead of the GTM loader. 2. The Cookiebot cd.js script embedded directly in site/legal/cookies-policy.md rendered on every profile, so a staging visitor who hit /legal/cookies-policy/ would leak their IP to consent.cookiebot.com. Replaces the inline

community.vyos.net.git/site, branch development

chore: reconcile production->development divergence (content sync) (#63)

Address Copilot review: preconnect order + staging-gate cookies-policy script