Currently, publishing a new package version is triggered by tagging the desired commit. We would like to reverse this a bit, and instead have all pushes to main trigger the release & publish pipeline, and then if a package does end up getting published in the process, Jenkins will automatically apply a tag to the commit. The automatically generated tags will have the format <package_name>_<version>. This clears up current ambiguity about the package that tag names are referring to.
Currently, publishing a new package version is triggered by tagging the desired commit. We would like to reverse this a bit, and instead have all pushes to
maintrigger the release & publish pipeline, and then if a package does end up getting published in the process, Jenkins will automatically apply a tag to the commit. The automatically generated tags will have the format<package_name>_<version>. This clears up current ambiguity about the package that tag names are referring to.