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 docs for this action specify using @master. I've also noticed that the package.json version is stuck at 0.1.0 and is not being updated with new commits on master. Might we expect this repo to follow semver at some point in the future so it can be tagged accordingly with v1, v2, etc? That'd make me feel more comfortable that breaking changes would not be suddenly introduced in our workflows while not totally opting out of bug fixes and feature additions by using @[commit sha]. Thanks!
The text was updated successfully, but these errors were encountered:
The docs for this action specify using
@master
. I've also noticed that the package.json version is stuck at0.1.0
and is not being updated with new commits on master. Might we expect this repo to follow semver at some point in the future so it can be tagged accordingly with v1, v2, etc? That'd make me feel more comfortable that breaking changes would not be suddenly introduced in our workflows while not totally opting out of bug fixes and feature additions by using@[commit sha]
. Thanks!The text was updated successfully, but these errors were encountered: