Skip to content

fix(faustwp): exclude updater code from wordpress.org build, add info.json#2423

Closed
josephfusco wants to merge 1 commit into
canaryfrom
fix/faustwp-internal-distro-hygiene
Closed

fix(faustwp): exclude updater code from wordpress.org build, add info.json#2423
josephfusco wants to merge 1 commit into
canaryfrom
fix/faustwp-internal-distro-hygiene

Conversation

@josephfusco

Copy link
Copy Markdown
Member

Excludes the updater PHP files and info.json from the wordpress.org distribution via .distignore, clarifies the conditional require comment, qualifies the 1.5.0 self-update changelog entry, adds an explicit verifier assertion for updater file absence, and wires info.json refresh (version, last_updated, tested, download_link, versions map, changelog section) into scripts/versionPlugin.js so the non-wordpress.org channel manifest stays in sync at every version bump.

….json

- Add includes/updates and info.json to .distignore so the wordpress.org
  build no longer ships the external update channel files.
- Reword the file_exists comment in faustwp.php to make the wordpress.org
  exclusion explicit.
- Qualify the 1.5.0 self-update changelog entry so historical entries
  surfacing in readme.txt clarify that they apply only to non-wordpress.org
  distributions.
- Add an explicit verify-published-plugin.sh assertion for updater file
  absence, with a targeted failure message.
- Check in plugins/faustwp/info.json at 1.8.9 and wire its refresh into
  scripts/versionPlugin.js so version, last_updated, tested, download_link,
  the versions map and the changelog section stay in sync at each version
  bump.
@changeset-bot

changeset-bot Bot commented Jun 16, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 0ec8285

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@github-actions

Copy link
Copy Markdown
Contributor

📦 Next.js Bundle Analysis for @faustwp/getting-started-example

This analysis was generated by the Next.js Bundle Analysis action. 🤖

This PR introduced no changes to the JavaScript bundle! 🙌

@josephfusco

Copy link
Copy Markdown
Member Author

Closing — initial audit was based on stale canary state and missed the existing composite action at .github/actions/release-plugin/action.yml, which already handles the two-build split and info.json refresh. The .distignore + info.json + versionPlugin.js changes here either duplicate that infra or actively break the main/internal zip. Reopening with a much smaller scope.

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.

1 participant