Progressive CMS 1.0 Public Beta

Progressive CMS 1.0 Public Beta (1.0.0-rc.30)

Prerelease: this is not stable 1.0.0.

RC30 hardens release packaging and upgrades:

• The ZIP packer writes predictable file and directory permissions across build umasks.
• Before activation, the installer normalizes permissions and checks that the runtime service user can read the complete release tree.
• The Web update path verifies that the activated release matches the active current target and expected version. If activation or verification fails before migrations run, it asks the privileged installer to restore the previous release using a receipt and compare-and-swap check. The existing backup gate remains in place.
• CI verifies the pinned first-party extension supply and the immutable native-source archive.

There are no new Core database migrations in RC30; the migration head remains 0005_interaction_privacy.

Install and upgrade

Download the installable ZIP and verify the attached SHA-256 sidecar before use. GitHub's generated source archives are not installable releases. Back up an existing installation and review the versioned installation guide, requirements, compatibility notes, and documentation index. Publishing this release does not update existing sites.

If cms doctor reports reindex_required: true for an existing Search index, an operator with search.reindex can run cms search reindex --environment <env> --yes and check cms doctor again.

Artifact integrity

Install ZIP: progressive-cms-v1.0.0-rc.30-20261022T001255Z-d4cfe80.zip
SHA-256: 04a5cb098d631c2c6c5520aa191c53699932853a9e1d45a6428283a24ad21a06

The corresponding native source archive for the bundled sharp/libvips components is progressive-cms-native-sources-sharp-libvips-1.3.4.zip, 202,153,976 bytes, SHA-256 c221aaed0658ee2afbe26803b6b02a2aa7a0b8199054cdf5a1c68e0d90547fb1.

RC30 test-target note

On the pre-existing RC30 test installation, live/ready health, Admin assets, migrations, and Worker heartbeat passed. cms doctor reported DEGRADED because the existing Search index was at version 0 instead of 2. Reindex was not run, so Search remains unverified on that target.