chore(deps): bump WordPress/action-wp-playground-pr-preview/.github/workflows/preview-publish.yml from 3 to 4

[dependabot]

Bumps WordPress/action-wp-playground-pr-preview/.github/workflows/preview-publish.yml from 3 to 4.

Release notes

Sourced from WordPress/action-wp-playground-pr-preview/.github/workflows/preview-publish.yml's releases.

v4.0.0

v4 keeps the direct action and reusable build/publish setup, with stricter artifact handling and clearer template behavior.

Upgrade

For a direct action, change:

- uses: WordPress/action-wp-playground-pr-preview@v3

to:

- uses: WordPress/action-wp-playground-pr-preview@v4

For built previews, update both reusable workflow references:

uses: WordPress/action-wp-playground-pr-preview/.github/workflows/preview-build.yml@v4

uses: WordPress/action-wp-playground-pr-preview/.github/workflows/preview-publish.yml@v4

Keep the publish caller on your default branch. Existing inputs and build commands still apply.

Behavior changes

• PR and repository template values render as literal text. Put PR_* and REPO_* placeholders outside Markdown code spans or fences. For example, change **Branch:** `{{PR_HEAD_REF}}` to **Branch:** {{PR_HEAD_REF}}.
• Comment mode reuses only comments written by the account behind github-token. Changing that account creates a new comment. Failed account lookups stop the update.
• Artifact bundles must contain ordinary files and directories, not links or special files. The legacy helper extracts only the requested artifact-filename into a temporary directory, rather than unpacking the whole bundle into the caller's workspace.
• Legacy callers must provide a source run and PR that agree on repository, branch, and current head commit. Use the source run's head_sha, positive unpadded IDs, and a PR number obtained from GitHub's event or API. Stale or mismatched runs fail before changing release assets. The token needs actions: read and pull-requests: read in the source repository and contents: write in the release repository.
• The reusable publisher uses one PR-number spelling for uploads and cleanup: 007 becomes 7. Existing assets are not renamed.

Documentation

The README covers token placement, current Blueprint examples, ZIP layouts, v3 migration, and legacy source-run lookup. Example repository names retain v3 so existing links keep working.

See the upgrade guide. Upgrading to v4 requires updating your workflow references.

Changes: #94, #95.

v3.0.1: v4 upgrade notice

This v3 patch adds an upgrade warning with a link to the v4 migration guide.

• The direct action, reusable build and publish workflows, and legacy artifact helper emit the warning.
• The warning does not fail a job. Existing v3 preview behavior is unchanged.

... (truncated)

Commits

• 1b15093 Document v4 migration and pin the merged button action (#95)
• f299cc6 Validate preview bundles and render PR metadata as literal text (#94)
• 5e92f5e Polish README onboarding flow (#82)
• ef084f0 Clarify README recipe placement (#81)
• 68b03ba Improve README flow for new readers (#80)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)