slawekjaranowski commented on issue #210: URL: https://github.com/apache/maven-gh-actions-shared/issues/210#issuecomment-3536324897
> > I would like to not change default branch ... when we need introduce next version which will to brake compatibility we need next vx branch. > > it seems I was not clear: I'm just talking of Git default that would point to "current release" = v4 for now, so people are not fooled like me when looking at https://github.com/apache/maven-gh-actions-shared/ = displaying default branch > > in the future, if a v5 is necessary, during its preparation it won't be the default one, but when stable enough, it will become default > > keeping `main` branch as default branch when it not used for real maintenance is just confusing: not developer friendly = one of the reasons experience for me has been painful for past years when GHA is more and more used so we need to consider - move a documentation to vx - check release drafter-templates and move it to vx, we have configurations in projects like, https://github.com/apache/maven-parent/blob/master/.github/release-drafter.yml#L20C1-L21C1 ``` _extends: maven-gh-actions-shared ``` - we use actions like: https://github.com/apache/maven-parent/blob/master/.github/workflows/maven-verify.yml ``` uses: apache/maven-gh-actions-shared/.github/workflows/maven-verify.yml@v4 ``` I'm not sure what impact it can have on such configurations/usages ... which is used in all Maven projects -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
