Repository navigation
Deprecate /release and /versioning #38
Description
I'd like to deprecate the /release and /versioning actions in favor of release-please.
it can handle pretty much everything we need i think, e.g. auto semver, tagging, etc.
we're already using it for ci-actions repo itself: https://github.com/DataLabHell/ci-actions/blob/main/.github/workflows/_release-please.yml
Activity
dan-n94 commentedon Sep 23, 2026
release-please only make sense for github releases no?
when building docker containers I do not need github releases at all and still somehow need to version to tag images?
chjdev commentedon Sep 23, 2026
not exclusionary :) e.g. it can create the tag and the tag triggers the docker build
usually then with an autogenerated change notes on the tag release
if you want to ship artifacts you need to do some extra steps, see e.g. devclaude repo
dan-n94 commentedon Sep 24, 2026
ok, but than I must create releases, otherwise it cannot track the versions for the container or any other build artifact.
I am fine with this approach, really like the release please.
What do you exactly mean by deprecating? Do you just mean to remove the action in the repo or also the corresponding tags (if second one as well, several current pipelines need to be migrated first)
chjdev commentedon Sep 24, 2026
as discussed: deprecation just means no further development, no active deletion of the old tags planned
since we're using conventional commits everywhere already release-please acts as a nice thin one stop shop for these workflows. it bumps the versions automatically and then triggers a main/tag merge -> on which e.g. a docker image tag stage can listen
devclaude and ci-actions already use it succesfully, vermittlung is in the process of being ported with some more involved python setup incl. uv workspaces to see if release-please approach breaks.
if it works as expected, we discussed to just port the current users directly instead of a prolonged full deprecation cycle