-
-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Encourage GitHub actions authors that we support to provide major version(s) for their action #289
Labels
enhancement
New feature or request
Comments
jmfayard
added
bug
Something isn't working
enhancement
New feature or request
and removed
bug
Something isn't working
labels
Jun 17, 2022
jmfayard
changed the title
Some actions don't have a major version - asking people to provide one
Encourage GitHub actions authors that we support to provide major version(s) for their action
Jun 17, 2022
This was referenced Jun 17, 2022
Closed
Closed
Closed
Closed
Closed
Closed
Merged
Won't be needed once #556 is delivered. |
From now on, only actions with major version tags have wrappers bundled with this lib. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
GitHub Actions Kotlin DSL provide an alternative to write GitHub Actions not in YAML but in a type-safe programming language: Kotlin.
To this end we provide type-safe wrappers for currently 72 (and counting) wrapper actions. Those type-safe wrappers are generated from its
action.yml
which we update when it goes to a new major version, for exampleactions/cache@v2
toactions/cache@v3
Unfortunately when an action don't have a major version, which is what GitHub recommands, we are forced to update manually for every minor version, like from
appleboy/scp-action/v0.1.2
toappleboy/scp-action/v0.1.3
Would you consider creating a major version for your action?
You can find here the recommendations from GitHub:
https://github.com/actions/toolkit/blob/main/docs/action-versioning.md (see "Recommendations" in particular)
Note: in practice this is done by pushing a tag
v1
to your latest1.x.y
releasegit tag -fa v1 -m "Update v1 tag" git push origin v1 --force
The text was updated successfully, but these errors were encountered: