Skip to content

Conversation

@colinmurphy
Copy link
Member

@colinmurphy colinmurphy commented Jul 2, 2025

Description

What does this do

  1. Fixed a typo in the plugin npm script package name (Copilot PR chore: Run version script when creating a release branch #311 )
  2. Added a check and ran this script before committing the release branch (Copilot chore: Run version script when creating a release branch #311)
  3. Added a valid package.json file for composer installs as plugin/package.json
  4. Tested npm run version and updated the previews plugin (from 0.0.4 to the current version 0.0.5)
  5. Tested adding this version to the new plugins/package.json .github/scripts/update_composer_package.sh "0.0.5" "https://github.com/wpengine/hwptoolkit/releases/download/%40wpengine%2Fhwp-previews-wordpress-plugin-0.0.5/hwp-previews.zip" "wpengine/previews" "A WordPress plugin for headless previews."
  6. Updated release branch workflow to run this script
  7. Renamed get-plugin-slug.sh to get_plugin_slug.sh

[!NOTE}
I will create a follow on PR (assuming this works) with docs for plugins (how to create them, add code quality, composer etc), How to install a plugin with composer.

Related Issue

#303

Dependant PRs

Type of Change

  • ✅ Bug fix (non-breaking change which fixes an issue)
  • ✨ New feature (non-breaking change which adds functionality)
  • 💥 Breaking change (fix or feature that would cause existing functionality to change)
  • 🧹 Code refactoring (no functional changes)
  • 📄 Example update (no functional changes)
  • 📝 Documentation update
  • 🔍 Performance improvement
  • 🧪 Test update

How Has This Been Tested?

Screenshots

Checklist

  • I have read the CONTRIBUTING document
  • My code follows the project's coding standards
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation (if applicable)
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works (if applicable)
  • Any dependent changes have been highlighted, merged or published

@changeset-bot
Copy link

changeset-bot bot commented Jul 2, 2025

🦋 Changeset detected

Latest commit: 19b64ba

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@wpengine/hwp-previews-wordpress-plugin Patch

Not sure what this means? Click here to learn what changesets are.

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

chore: Run version script when creating a release branch
@github-actions
Copy link

github-actions bot commented Jul 2, 2025

ℹ️ Download the latest hwp-previews plugin zip from this PR
(See the 'Artifacts' section at the bottom)

@colinmurphy colinmurphy self-assigned this Jul 2, 2025
@colinmurphy colinmurphy marked this pull request as ready for review July 2, 2025 10:10
@colinmurphy colinmurphy requested a review from a team as a code owner July 2, 2025 10:10
@colinmurphy colinmurphy enabled auto-merge July 2, 2025 10:10
@colinmurphy colinmurphy changed the title chore: DRAFT Adding composer package setup to workflow chore: Adding composer package setup to workflow Jul 2, 2025
@colinmurphy colinmurphy added this pull request to the merge queue Jul 2, 2025
Merged via the queue into main with commit cde71cf Jul 2, 2025
20 checks passed
@colinmurphy colinmurphy deleted the feat-add-composer-packages-for-plugins branch July 2, 2025 10:14
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.

3 participants