[obenland]

The preview button step here is already pinned to v4.0.0; the expose-artifact-on-public-url helper above it was left on a v3 commit. This pins both to the same release (1b15093).

Why

v4.0.0 is the current major of WordPress/action-wp-playground-pr-preview. The v3 tag was re-released as v3.0.1 with an upgrade warning that now prints on every run, so anything still on v3 (or older) logs a deprecation notice until it moves.

v4 behaviour changes, checked against this workflow

• Template variables render as literal text. PR_* / REPO_* placeholders must sit outside Markdown code spans and fences. This workflow uses the default templates, so nothing to change.

• Comment mode matches on the author behind github-token. Not applicable — this workflow posts in append-to-description mode.

• Artifact bundles must contain ordinary files and directories. The legacy helper now extracts only the requested artifact-filename into a temp directory instead of unpacking the whole bundle into the workspace.

• PR-number spelling is normalised for uploads and cleanup in the reusable publisher (007 → 7). Previously uploaded assets are not renamed.

• Legacy source-run checks apply here. This workflow passes artifact-source-run-id, so v4 additionally requires the source run to be a pull_request run whose head repository, branch and head SHA match the pull request, and commit-sha to equal the run's head_sha. The existing Resolve trusted PR metadata step already derives both from workflow_run.head_sha, so these hold. The lookups need actions: read and pull-requests: read in the source repo; the job's pull-requests: write covers the latter, and the same run-artifact listing already succeeds in the github-script step above.

Testing

workflow_run resolves this workflow from develop, so the v4 helper runs once this lands. The diff is a single ref.

🤖 Generated with Claude Code

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: obenland <obenland@git.wordpress.org>
Co-authored-by: dkotter <dkotter@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[github-actions]

✅ WordPress Plugin Check Report

✅ Status: Passed

📊 Report

All checks passed! No errors or warnings found.

---

🤖 Generated by WordPress Plugin Check Action • Learn more about Plugin Check

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 80.72%. Comparing base (fb41c70) to head (6994240).

Additional details and impacted files

@@            Coverage Diff             @@
##             develop    #1043   +/-   ##
==========================================
  Coverage      80.72%   80.72%           
  Complexity      2998     2998           
==========================================
  Files            124      124           
  Lines          11978    11978           
==========================================
  Hits            9669     9669           
  Misses          2309     2309           

Flag	Coverage Δ
unit	80.72% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.