add a new workflow for publishing

[jimbarrett27]

not sure how to properly test this...

[naslundx]

Nice to see! 🎉 I wonder about the duplication in the publish script. Either...

1. We block all direct pushes to main (everything goes through a PR), that should mean that every piece of code has been tested - merging from dev to main should also be a PR. In that case we only "need" the publishing part in the publish workflow.

2. We reuse the PR workflow and run the job before the publish (if it succeeded). That's possible AFAIK: https://docs.github.com/en/actions/sharing-automations/reusing-workflows

[jimbarrett27]

Yeah, I was wondering the same, wasn't sure what the best practice was.

It would also be nice to block merges to main if the version hasn't been bumped, didn't find a good way to do that yet either

[naslundx]

It would also be nice to block merges to main if the version hasn't been bumped, didn't find a good way to do that yet either

Oh that's a good one. Worth creating an issue for, I can investigate it later.