Release workflows

[mattwynne]

🤔 What's changed?

• Added release workflows copied over from cucumber-expressions (removed the python one as there's no python port of messages right now.)

⚡️ What's your motivation?

Part of cucumber/common#2029

🏷️ What kind of change is this?

• 🏦 Refactoring/debt/DX (improvement to code design, tooling, documentation etc. without changing behaviour)

♻️ Anything particular you want feedback on?

I might need some help with the remaining languages cc @WannesFransen1994 @ciaranmcnulty @ehuelsmann

📋 Checklist:

• I agree to respect and uphold the Cucumber Community Code of Conduct
• Create Release environment / branch
  • Add secrets
• Add support for:
  • elixir
    • Build first iteration of action-publish-hex action-publish-hex#1
    • Support hex (Elixir / Erlang) polyglot-release#80
  • perl
    • Build first iteration of action-publish-cpan action-publish-cpan#1
  • php
    • https://github.com/cucumber/action-publish-subrepo

---

This text was originally generated from a template, then edited by hand. You can modify the template here.

[mattwynne]

It seems like PHP/Composer just needs a git url/tag so very similar to Go.

We could either make a new action-publish-subrepo that we can use to publish the php (and go) folders to their own subrepos, or we could tell php/go users to use a path within the repo. They will end up cloning the whole polyglot repo but perhaps that's not such a big deal now it's not the whole monorepo.

Thoughts @ciaranmcnulty @vearutop?

[vearutop]

Yes, I think the size of this repo is ok, we can use it directly without subrepos.

We just need to change module name to github.com/cucumber/messages/go/v19 in https://github.com/cucumber/messages/blob/main/go/go.mod#L1.

[mattwynne]

OK I think we're there.

@vearutop @ciaranmcnulty I decided to build a thing for publishing to a subrepo anyway.

Can someone give this a look-over before we merge and try it out?

[davidjgoss]

LGTM (but can’t speak to other langs)

[ciaranmcnulty]

PHP thing looks ok to me, how would it be tested?

Do the target repository's webhooks fire when this is done from a workflow?

[mattwynne]

PHP thing looks ok to me, how would it be tested?

See the CONTRIBUTING.md for https://github.com/cucumber/action-publish-subrepo

tl'dr there's some unit tests for the code shell script that work with local git repos, and then a fairly convoluted acceptance testing setup that actually runs the action in the github.com/cucumber/action-publish-subrepo-test-monorepo repo, and proves that ii publishes the right stuff into github.com/cucumber/action-publish-subrepo-test-monorepo-a-subfolder

Do the target repository's webhooks fire when this is done from a workflow?

That target repo will receive a git push --force so I'd assume the push event will fire as normal.