chore: Initial PR for creating pre-release tags for a plugin

[colinmurphy]

Description

This is the first iteration of the beta release process.

Note

This process should be updated once we have actual releases of plugins.

Process

1. When a PR is merged for a plugin with a changset, this triggers the pre-release workflow

This does the following

1. Install npm, pnpm, PHP
2. It will bump the package.json version of the plugin based off the changeset
3. Checks that a package.json exists with a valid name (needed for changesets)
4. It creates a pre-release tag based off the package name and version e.g. @hwp-previews/wordpress-plugin-0.0.1-beta
5. It will then create a zip of the plugin using composer archive
6. Finally this will be uploaded to the GitHub tag

Related Issue

#257

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]

🦋 Changeset detected

Latest commit: 69cdb6a

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

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

[github-actions]

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

[moonmeister]

General question, I believe changesets supports doing pre-release tags like "beta" or "next", would that be beneficial for us or because the versions are less than 1.0 is it pointless?

[colinmurphy]

General question, I believe changesets supports doing pre-release tags like "beta" or "next", would that be beneficial for us or because the versions are less than 1.0 is it pointless?

Thanks @moonmeister

I wasn't aware that they did have option so I will look into it ❤️ Thanks for the feedback.

[colinmurphy]

@moonmeister

This is ready for another review. I have simplified the process as per your feedback.

Process
When a PR is merged for a plugin with a changset, this triggers the pre-release workflow
This does the following:

1. Install npm, pnpm, PHP
2. It will bump the package.json version of the plugin based off the changeset
3. Checks that a package.json exists with a valid name (needed for changesets)
4. It creates a pre-release tag based off the package name and version e.g. @hwp-previews/wordpress-plugin-0.0.1-beta
5. It will then create a zip of the plugin using composer archive
6. Finally this will be uploaded to the GitHub tag

[moonmeister]

I'm trusting your implementation and just looking for major things

meant to request changes