digital-gravy/Publish Changelog to WordPress

Publishes a GitHub Release body to a WordPress Custom Post Type as the post content plus an ACF WYSIWYG field. Idempotent on slug.

Trust Signals

name	description	required	default
release_tag	Release tag to publish. Use "latest" to resolve the most recent published release.	no	latest
wp_url	WordPress site URL (no trailing slash). Example: https://example.com	yes	—
wp_username	WordPress username used for Basic auth with an Application Password.	yes	—
wp_app_password	WordPress Application Password for the user above. Treat as a secret.	yes	—
cpt_slug	REST slug of the Custom Post Type to write to (e.g. "changelog"). Must be exposed in REST.	no	changelog
acf_field	ACF field name to receive the rendered changelog items (the bullet list). Must be in a field group with "Show in REST API" enabled and a Location rule that matches the target CPT.	no	changelog_list
post_status	Post status applied on create/update: "publish" or "draft".	no	publish
dry_run	When "true", skip the WordPress write and only render the preview into the workflow step summary.	no	false
body_file	Optional path to a local markdown file. When set, the action uses this file instead of fetching the GitHub Release body. Useful for smoke testing.	no	""
github_token	Token used to read the release body and call the GitHub /markdown render endpoint. Defaults to the workflow GITHUB_TOKEN.	no	${{ github.token }}

name	description
post_id	ID of the WordPress post that was created or updated. Empty when dry-run or when the release was skipped (e.g. dev prerelease).
action_taken	One of "created", "updated", or "skipped".