Repository navigation
docs(site): reconcile README, downloads and bilingual landing to actual v1.6.42 stable - #742
Conversation
…nd direct installer
…atest, not old main VERSION
…atest-source authority
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4d69d3d4ce
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| <p class="hero-copy">Connect a relay by IP or open an SCL file. Explore its live IED model in the updated Browser, follow DataSets and Reports, monitor values, and verify guarded Control/Write during authorized testing. Keep the resulting FAT or SAT evidence tied to the right device.</p> | ||
| <div class="hero-actions"> | ||
| <a class="btn btn-primary" href="download.html">Download for Windows</a> | ||
| <a class="btn btn-primary" href="{{INSTALLER_URL}}" download>Download stable v{{STABLE_VERSION}}</a> |
There was a problem hiding this comment.
Changing the English CTA to “Download stable” and the Indonesian CTA to “Unduh stabil” breaks both existing homepage validation contracts: scripts/validate-product-source.py still requires “Download for Windows” and “Unduh untuk Windows”, as does scripts/validate-product-build.py. Running these validators reproduces both failures. In .github/workflows/pages.yml, the source-validation step runs this check and the “Enforce source validation” step exits on its failure, preventing the updated release website from deploying. Update both validators to match the intentional bilingual CTA change, or retain the required labels. This also violates the repository requirement to use existing engineering validation gates.
AGENTS.md reference: AGENTS.md:L227-L227
Useful? React with 👍 / 👎.
Why
GitHub
/releases/latestnow reports v1.6.42 Public Stable (tag source3db2ca98d144ab4b456e8dc1db9af18ad7a948f2), with 5 valid assets, whilemainREADME, website notes,landing/latest.jsonand independent updater record still advertise v1.6.41. This PR synchronizes documentation/website/updater only, without touching Windows app, engine pin, packaging or existing release assets.Scope
landing/latest.jsonand.release/published.json.docs/WINDOWS_RELEASES.mdand the existingsync-release-documentation.ymlto source latest published GitHub stable, not the olderVERSIONon main (which would roll site back).Release boundaries
Public Stable is operator-approved Windows application packaging. It is NOT physical R7/R10 engine qualification, lossless SOE proof, complete SCL parity or IEC 61850 certification. Existing source promotion PR #729 stays separately governed and unmerged; no bypass/repin of failed R7/Reference Guard qualification checks.
Expected checks
pages.ymlsource/rendered site/SEO, bilingual links, release evidence, metadata integrity. On merge the existingsync-release-evidence.ymlmirrors the updated stable ledger torelease-evidenceand dispatches Pages; the existing release-doc sync workflow also refreshes Pages. Verify live homepage, download center, release notes and updater metadata against GitHub/releases/latestand actual SHA-256 after deployment. Do not dispatch Windows release/rebuild.