I would not do that for Maven plugins in a POM, so I would not do that either for GitHub actions.
Mailing list volume is a different topic. Gary On Sun, Aug 16, 2020, 05:55 Mark Thomas <ma...@apache.org> wrote: > Hi, > > I am seeing an awful lot of list traffic generated for patch updates to > github actions e.g. updating from v1.4.0 to v1.4.1 > > Having read [1], my understanding is that we can specify v1 and that > will always point to the latest 1.x.x release. > > Would it not be better to specify v1 for these actions as that way: > - we use the latest version automatically (until 2.x.x is released) > - we avoid all the noise on the mailing list > > Mark > > > > [1] https://docs.github.com/en/actions/creating-actions/about-actions > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >