lhansford/bugsnag-report-build-action

Tagging strategy improvement

Opened this issue · 2 comments

peterdeme commented

Hello!

One minor thing I noticed is that using lhansford/bugsnag-report-build-action@v1 won't use the latest v1.x.x version, instead it uses v1.0.0.

The reason is that you need to retroactively tag the v1.0.0 version into the latest commit. Here is the full explanation: https://github.com/orgs/community/discussions/48058#discussioncomment-5055159

And this is how actions/checkout is doing it:

I noticed this because we're using @v1 postfix but we still got the Node16 warning.

lhansford commented

@peterdeme thanks for sharing this. We use commit hashes for versioning Github Actions in my job so I wasn't aware this was an issue!

I've manually added the v1 tag to the v1.3.0 release. When I have more spare time I'll also take a look at automating it a bit more.