Release tags management

[EwenQuim]

Hi ! I'm currently investigating how we can improve our release process.

Currently, we face 2 problems.

1. I'm the only one making release and I do it by hand

Basically, I git tag -a v0.x.y and push the tag and it create a release thanks to Go package system.
But :

• it can take some time
• I'm the only one doing so
• I can make mistakes

2. We're using a monorepo

Currently we're releasing several modules in one repo.

• main fuego package: git tag v0.x.y
• extra/adaptor packages: git tag extra/fuegogin/v0.x.y

I sometimes forget to tag extra packages, and it's hard to maintain tags related to each other. What does extra/fuegogin/v0.4.0 means to fuego main package?

Solutions?

Should we have a system to push tags altogether? It means that when I push a new fuego v0.x.y+1, I'll also push a extra/fuegogin/v0.x.y+1.

• react and react-dom do so, for example.
• If it is a gin-only packages, we can push a single extra/fuegogin/v0.x.y.patch-1 for example
• Easy to track and publish changes, and enables automation for this package.

Using GoReleaser might help?

[ccoVeille]

There is also release-please, I think it could be used with GoReleaser if I'm not wrong.

[EwenQuim]

Mmmh I didn't knew about release-please. Thanks for the info!

[ccoVeille]

Good points, but here I would say it's only about using tools, so any would be OK as long as there is someone who knows how to use them.

The configuration journey might be rollercoaster

[EwenQuim]

I do personally prefer that all the extra packages match our root fuego version

Happy to see that we share the same vision. I'll be setting up the tooling then.

[totallyzen]

hey folks, I got some experience with this, happy to offer a jumpstart on the matter (not guaranteed to be complete, but it demonstrates the basics) 🙂

release-please and goreleaser are indeed a really good combo!

I'm not familiar with your current build procedure, but I can show you how to keep a bunch of versions in sync in several files, etc. if you wish to have a single version. I do agree it can be stated as "these have been integration tested together, use them together" 🙏

Cheers!
B

[dylanhitt]

@totallyzen feel free to open a PR showing any kind of work.

Thank you

[totallyzen]

Sorry it took so long to get going. 🙇
#506

It's far from mergeable, but it's a decent start of a dicussion to examine your needs. 🙂
I'm just about to add some author annotations as well to explain what you see in front of you.

Cheers!

[EwenQuim]

@totallyzen I'll test it on a private repo to make sure I don't break anything on the main fuego repo lol