Release v2026.10.3-deploy.3b8f46d56fdfHomepage

Homepage v2026.10.3-deploy.3b8f46d56fdf

This release updates CodeSplash Homepage's Chrome Web Store release process, not the new tab experience itself. The team can now verify that the public Chrome package matches an exact source commit before recording a successful shipment, with a validation-only mode to check publication status safely first.

October 3, 2026

Highlights

01

Added a verified Chrome publication workflow tied to an exact source SHA

02

Manual checks now default to validation-only, so release managers can confirm the public package before reporting shipment

03

Shipment reporting stays pending if the Chrome Web Store is still serving a different package

04

Publication checks compare application files and the manifest, not just the version number

05

Added test coverage and CI checks for the new store-publication reporting flow

Changelog

What changed in v2026.10.3-deploy.3b8f46d56fdf

Features

  • Added a GitHub workflow to verify that the live Chrome Web Store package matches a specific source commit before reporting a successful deployment
  • Added a validation-only mode for Chrome publication checks so submitted builds can be verified without sending a shipment event
  • Added documentation for the verified publication workflow, including local validation commands and guidance for reporting an already-submitted source after it becomes public

Improvements

  • Improved release traceability by recording exact-source Chrome publication through successful GitHub deployments
  • Reused existing successful deployment receipts and documented recovery for failed status writes on the same deployment
  • Expanded CI coverage to run JavaScript checks, existing tests, and new Python unit tests for store-publication behavior

Fixes

  • Prevented premature shipment reporting by keeping releases in a pending state when the Chrome Web Store has not published the selected source yet
  • Reduced false-positive release reporting by requiring package-level verification instead of treating a matching version number as sufficient proof

Screenshots