Skip to content

CI: activate protected WordPress validation and release pipeline - #1

Merged
ProxiwebLabs merged 2 commits into
mainfrom
codex/zq-wordpress-ci
Sep 14, 2026
Merged

ProxiwebLabs merged 2 commits into
mainfrom
codex/zq-wordpress-ci

Conversation

@ProxiwebLabs

Copy link
Copy Markdown
Contributor

Scope

  • pin every third-party action to a reviewed immutable SHA
  • add fail-closed secret/sensitive-file and whitespace gates
  • validate PHP 7.4–8.3, WordPress and WooCommerce compatibility
  • build tracked-only release artifacts with checksums and a manifest
  • require tag/plugin/stable-tag version consistency
  • attach tag releases to the protected wordpress-release environment
  • refuse replacement of an existing release or immutable artifacts

Local evidence

  • workflow YAML parsing: PASS
  • plugin/build PHP syntax: PASS
  • PHPUnit: 4 tests, 16 assertions
  • deliberate tag/version mismatch exits 65
  • secret scan: 64 versionable files, PASS
  • tracked-only package rehearsal and manifest verification: PASS
  • git diff --check: PASS

Safety

This PR does not deploy WordPress or ZipQuantum production. Release remains tag-triggered and gated by the wordpress-release environment.

@ZipQuantumHQ ZipQuantumHQ left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CI matrix is green across security, quality, PHP syntax, WordPress, WooCommerce and forward-compatibility. Approval is for merge only; no release tag or production deployment is authorized.

@ProxiwebLabs
ProxiwebLabs merged commit f3e06cc into main Sep 14, 2026
44 checks passed
@ProxiwebLabs
ProxiwebLabs deleted the codex/zq-wordpress-ci branch September 14, 2026 12:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants