Is something still missing in my PR? <https://gith...
# github-workflows-kt
j
p
if you tested the wrappers work fine with these versions, then it's fine 🙂 I think I asked about it somewhere in the comments
at some moment I asked you to switch from e.g.
v2.1.0
to
v2
but then I thought it may not actually work, my bad. I just ask to double check it in runtime
I'm working on generating the wrappers, then such problems will disappear (https://github.com/krzema12/github-actions-kotlin-dsl/issues/71)
j
I will check that the wrappers work
👍 1
p
Do you have an example run of "RefreshVersions PR" workflow?
Yaml itself doesn't mean it will work :)
I see only "runOnGitHub" check
p
Ok, thanks! Approving
Thank you!
K 1
unfortunately it doesn't work: https://github.com/krzema12/test-repo/runs/5070645674?check_suite_focus=true, it says "Error: Unable to resolve action
peterjgrainger/action-create-branch@v2
, unable to find version `v2`"
I think that the new wrappers don't output exactly the same YAML as the versions are different. Other changes we see here are cosmetics
j
wouldn't it make sense to add in the constructor of
Action
a call to:
curl -H "Accept: application/vnd.github.v3+json" <https://api.github.com/repos/peterjgrainger/action-create-branch/releases>
that would ‱ throw an error if the tag doesn't exist ‱ outputs a warning if a newer version of the Action is available ‱ + adding an API to override the version, something like
Action.withVersion("2.1.6")
p
I'd like to handle version checking primarily in build time of the library, but what you say can be an alternative opt-in approach (especially with overriding the version, I thought about it). Could you create a feature request?
j
Checking new versions is not so important I did a ticket about the rest