You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The standard convention that most GitHub actions use is to create and keep updating an additional git tag that points to the most recent release in that major version, using simply the major version of that release as the tag value. This allows consumers of the action to simply reference it like this:
- name: Use an actionuses: cloudsmith-io/cloudsmith-cli-action@v1with:
...
The benefit is they can receive updates to this action over time without needing to explicitly update their action manifests. As long as the action's releases follow symver semantics, and that breaking changes result in a new major version (ex. @v2) then this should be okay.
Could a step be added to the release pipeline of cloudsmith-io/cloudsmith-cli-action be added that force pushes a tag with the major version?
The text was updated successfully, but these errors were encountered:
The standard convention that most GitHub actions use is to create and keep updating an additional git tag that points to the most recent release in that major version, using simply the major version of that release as the tag value. This allows consumers of the action to simply reference it like this:
rather than the full symver:
The benefit is they can receive updates to this action over time without needing to explicitly update their action manifests. As long as the action's releases follow symver semantics, and that breaking changes result in a new major version (ex. @v2) then this should be okay.
Could a step be added to the release pipeline of
cloudsmith-io/cloudsmith-cli-action
be added that force pushes a tag with the major version?The text was updated successfully, but these errors were encountered: