I've set up auto releasing based on a pull request...
# nextflow-pluginsa
Adam Talbot
11/10/2025, 12:33 PMI've set up auto releasing based on a pull request: https://github.com/adamrtalbot/nf-slack/actions/runs/19231552301/job/54971045988
1. Open a release PR including the version bump
2. Approve + merge
3. Github Action workflow releases it
I want to make it automated so I can just click the release button but this will do for now!
š¤© 3
š 1
m
Maxime Garcia
11/10/2025, 1:19 PMshared a GIF
p
Phil Ewels
11/11/2025, 4:41 PMNice, I was thinking of doing one of these / hoping that someone else might š
Phil Ewels
11/11/2025, 4:42 PMWow, a new release on push to
maina
Adam Talbot
11/11/2025, 5:13 PMIt runs but stops if the release hasn't been updated. So you need to bump the version get a new release, but if the version is the same it stops early
p
Phil Ewels
11/11/2025, 10:46 PMah nice šš»
Phil Ewels
11/11/2025, 10:46 PMWhy not use a github release as a trigger?
a
Adam Talbot
11/12/2025, 9:56 AMthat's what I did at first, but it actually doesn't make sense.
Adam Talbot
11/12/2025, 9:56 AMYou have to:
ā¢ Update the version number
ā¢ Update the changelog
ā¢ Hope no-one introduces another change!
ā¢ Create a release
Adam Talbot
11/12/2025, 9:56 AMWhich is counter productive and adds 3 steps.
Adam Talbot
11/12/2025, 9:57 AMThis way, we just create a "release" PR and it generates the release as an artefact
Adam Talbot
11/12/2025, 9:58 AMIn an ideal world, I would:
1. Create draft release on Github
2. Automatically update the version number and changelog
3. Push to registry
4. Make draft as a proper release
But because of permissions and branch protection this gets very awkward very quickly
Adam Talbot
11/12/2025, 9:59 AMYou could possibly do:
1. Create draft release on Github
2. Open a PR to automatically update the version number and changelog
3. Automatically merge PR if checks pass
4. Push to registry
5. Make draft as a proper release
Come to think of it that's not a bad idea š¤ but you would need to give the Github Bot permission to approve and merge PRs which feels risky
Adam Talbot
11/13/2025, 7:20 PMDocs now get released with release as well https://github.com/adamrtalbot/nf-slack/pull/15
meow love 1
p
Phil Ewels
11/14/2025, 7:45 AMMy workflow in basically every project I have is:
1. I bump the version (and check that tests are passing if I am feeling good)
2. I create a release on GitHub
3. GitHub actions publishes to PyPI/npm/wherever
Phil Ewels
11/14/2025, 7:45 AMDo you need it to be more complex than that?
a
Adam Talbot
11/17/2025, 11:06 AMeurgh, step 2 is manual.
Adam Talbot
11/17/2025, 11:06 AMClicking like some sort of barbarian
Adam Talbot
11/17/2025, 11:07 AMThe only difference here is the step 2 is automated
p
Phil Ewels
11/18/2025, 12:10 AMYour step 1+2 are both manual! š
a
Adam Talbot
11/18/2025, 3:20 PMnah only 1 is manual, 2 is automatic