Support version syntax (@v1)

[desrosj]

Description

It seems something was missed to make the action available through a specific version syntax (@v1, @v1.0.1, etc.).

For now, it's been reverted back to trunk. As an initial release, this will also help push out any bug fixes more quickly. But long term, repositories should not be running bleeding edge.

Version

v1

Workflow file

No response

Link

https://github.com/desrosj/wordpress-develop/actions/runs/7746224196/job/21123961020?pr=148

[ataylorme]

From the GitHub Action workflow syntax doc

You can specify a branch, ref, or SHA in a public GitHub repository.

My recommendation is to:

1. Create GitHub tags for each new version
2. Maintain a branch for each major version (e.g. v1).

This will allow users to have the choice of referencing a specific tagged version (e.g. @1.x.x) or referencing the major version branch (e.g. @v1).

[swissspidy]

Oh I didn't realize @v1 could just be a branch reference! 💡 Seems easier than having a rolling tag.

[desrosj]

Oh I didn't realize @v1 could just be a branch reference! 💡 Seems easier than having a rolling tag.

Same! Thanks @ataylorme. Let's create the v1 branch after we get some more of these issues cleaned up. We're using trunk to test the bleeding edge in Gutenberg/wordpress-develop currently anyway.