Skip to content

ci: add post-release check workflow [ED-25263] - #49

Open
Svitlana-Dykun wants to merge 18 commits into
mainfrom
feat/post-release-check
Open

ci: add post-release check workflow [ED-25263]#49
Svitlana-Dykun wants to merge 18 commits into
mainfrom
feat/post-release-check

Conversation

@Svitlana-Dykun

@Svitlana-Dykun Svitlana-Dykun commented Aug 18, 2026

Copy link
Copy Markdown

Summary

  • Adds a dispatchable Post-Release Check workflow that verifies GitHub releases, changelog on main, wordpress.org SVN/Stable tag, and zip version headers for published Core (and optional Pro).
  • Upgrade-path smoke (same idea as Core plugin-upgrade-test.yml): install current wordpress.org Elementor, import a heading page, --force install the released zip, then Playwright for frontend + create/edit canvas.
  • PRs that touch this workflow/actions also run it against current wordpress.org Core so the pipeline is exercised before a real GA.

https://elementor.atlassian.net/browse/ED-25263

Test plan

  • Open this PR and confirm Post-Release Check runs (verify + upgrade smoke) against current wordpress.org Core.
  • After merge, dispatch the workflow with core_version=4.2.2 (Pro empty) and confirm the job summary checklist is green.
  • Optional: dispatch with a Pro version once MAINTAIN_TOKEN can read elementor/elementor-pro releases.

Made with Cursor

✨ PR Description

1. Problem & Context

Implements a post-release verification suite ED-25263 to automate the validation of published Core and Pro artifacts, ensuring version consistency and basic editor stability after a release.

2. What Changed (Where)

File / Module Change
.github/workflows/post-release-check.yml Main orchestration workflow for verification and smoke tests.
actions/post-release-verify Node.js action validating GitHub APIs, changelogs, and zip headers.
actions/post-release-smoke Playwright suite testing plugin upgrades and editor booting.
actions/setup-wp-env Patched apt-get to bypass Debian Release expiry failures.
packages/editor-github-actions-utils Added version parsing and changelog extraction utilities.

3. How It Works

The workflow resolves versions $\rightarrow$ post-release-verify checks GitHub releases and zip headers $\rightarrow$ post-release-smoke installs the released zip over a live .org site and runs Playwright editor tests.

4. Risks

  • Pro Access: Requires MAINTAIN_TOKEN to access private Pro repos; missing tokens will fail verification.
  • SVN Lag: wordpress.org tags can lag GitHub releases; mitigated by skip-wordpress-org input.

Generated by LinearB AI and added by gitStream.
AI-generated content may contain inaccuracies. Please verify before using.
💡 Tip: You can customize your AI Description using Guidelines Learn how

Automate published-artifact verification and an upgrade-path editor smoke so post-release checklist items are not manual.

Co-authored-by: Cursor <cursoragent@cursor.com>
@wiz-9a149474ff

wiz-9a149474ff Bot commented Aug 18, 2026

Copy link
Copy Markdown

Wiz Scan Summary

Scanner Findings
Vulnerability Finding Vulnerabilities 7 Medium 2 Low
Data Finding Sensitive Data -
Secret Finding Secrets -
IaC Misconfiguration IaC Misconfigurations -
SAST Finding SAST Findings 14 Medium
Software Management Finding Software Management Findings -
Total 21 Medium 2 Low

View scan details in Wiz

To detect these findings earlier in the dev lifecycle, try the Wiz Code extension for VS Code, JetBrains, or Visual Studio.

Comment thread actions/post-release-verify/summary.ts Fixed
Comment thread actions/post-release-verify/zip.ts Fixed
Uninstall before installing the released zip so WP-CLI does not force-update a live Elementor tree, commit lockfile-driven action bundles, and tighten zip/summary handling for CodeQL.

Co-authored-by: Cursor <cursoragent@cursor.com>
Checkout this repo when the workflow is reused, so Core/Pro do not run against their own tree. Fail the editor-edit smoke if EXISTING_PAGE_ID is missing.

Co-authored-by: Cursor <cursoragent@cursor.com>
Svitlana-Dykun and others added 14 commits September 1, 2026 12:05
Refuse Core downgrades, fail clearly when the token cannot read Pro, enforce required Core, and pin reusable checkout to the caller ref.

Co-authored-by: Cursor <cursoragent@cursor.com>
DTS build failed TS2532 on split/index access. Guard the prerelease split and version-part lookups so turbo build can complete.

Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Beta tags like 4.3.0-beta2 have no changelog on main.

Co-authored-by: Cursor <cursoragent@cursor.com>
PHP 8.0 wp-env images still run apt-get on Debian bullseye, which currently fails when bullseye-security InRelease is stale.

Co-authored-by: Cursor <cursoragent@cursor.com>
Debian bullseye-security currently 404s package debs after apt-get update. Bookworm-based WordPress PHP 8.2 images avoid that, and apt installs skip upgrades if an old image is still used.

Co-authored-by: Cursor <cursoragent@cursor.com>
Lighthouse and setup-elementor-env source did not change; restore their bundles from main.

Co-authored-by: Cursor <cursoragent@cursor.com>
…263]

PR runs checked live published Core, not the branch, and were a weak expensive gate.

Co-authored-by: Cursor <cursoragent@cursor.com>
Callers must pass the same ref as the uses: pin so YAML and ./actions cannot drift. Copy dispatch input help onto the reusable contract.

Co-authored-by: Cursor <cursoragent@cursor.com>
Avoid a Core-only upgrade green when Pro was in the call. Assert zip filenames after download.

Co-authored-by: Cursor <cursoragent@cursor.com>
Verify gates are exercised on dispatch and Core/Pro callers. Changelog and header parsers stay covered in editor-github-actions-utils.

Co-authored-by: Cursor <cursoragent@cursor.com>
CI rebuilds lighthouse and setup-elementor-env bundles even when their sources did not change.

Co-authored-by: Cursor <cursoragent@cursor.com>
@Svitlana-Dykun Svitlana-Dykun changed the title feat: add post-release check workflow [ED-25263] CI: Add post-release check workflow [ED-25263] Sep 9, 2026
The action bundle options were identical. Avoid another copy of tsup.config.ts on this PR.

Co-authored-by: Cursor <cursoragent@cursor.com>
@Svitlana-Dykun Svitlana-Dykun changed the title CI: Add post-release check workflow [ED-25263] ci: add post-release check workflow [ED-25263] Sep 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants