danielpalme/ReportGenerator-GitHub-Action

Using latest version

Closed this issue · 8 comments

eduherminio commented

I've unsuccessfully tried to setup my tasks to use 4.8.x versions, to avoid worrying about bumping the version number myself.
I couldn't find clear documentation about this, but as suggested here, I tried:

  • danielpalme/ReportGenerator-GitHub-Action@4.8
  • danielpalme/ReportGenerator-GitHub-Action@4

I guess it doesn't work because it tries to match git tags in the repository.

Are you aware of any way of setting it up not having to worry about bumping the patches versions?
Despite using @dependabot, there're a bunch of PRs to approve every time a new version is released 😅

danielpalme commented

I was not able to find any documentation regarding this issue.
I guess you have to specify the full version.

eduherminio commented

I've looked further into this topic recently and it appears to depend only on git tags and branch names.
All the actions I use under https://github.com/actions have a vN tag acting as vN.x.
I've seen some others (such as rlespinasse/github-slug-action) combining traditional releases with branch names.

Anyway, now with @dependabot it's not a big deal, just clicking a few buttons in multiple repos.

  • 👍1
eduherminio commented

Hi @danielpalme,

Any chance you can have another look at this issue one of these days and review the tagging strategy?
I found more info/formal recommendations about it here:

We recommend creating releases using semantically versioned tags – for example, v1.1.3 – and keeping major (v1) and minor (v1.1) tags current to the latest appropriate commit. For more information, see "About custom actions" and "About semantic versioning.

I'm asking because of this 😅the more repos I use the action on, the more time consuming it becomes to bump minor versions + especially noise

image

danielpalme commented

I just created a new tag named 5.

Maybe you can try to change your action to:

uses: danielpalme/ReportGenerator-GitHub-Action@5

Does this work for you?

eduherminio commented

That sounds perfect to me, thanks, but I understand it can be a pain to maintain on your side.
You can probably try to figure out an internal action that, on release, moves automatically that tag to point to the release's tag.

danielpalme commented

I aware of this, but I will definitely automate that.

  • ❤️1
eduherminio commented

@danielpalme Kind reminder v5 tag isn't being updated to the latest one, in case you're not aware.

danielpalme commented

Thanks for the reminder. I fixed it.

  • 👍1