[CI]: Change release strategies

[itohatweb]

Before the release of v19 only run the release workflows on a tag create.

• NPM
• Docker Images

[MatthewSH]

Talking about releases, thoughts on leveraging release please for this? I've used it in every single one of my projects including monorepos and it's been a godsend.

For example, this is a private monorepo I have that uses it

It's not as pretty as some major release creation but it's pretty effective. It also creates tags for it and automatically maintains changelogs as well. The only downside is we'd have to follow conventional commits for it to work properly, so we'd maybe have to use something like an action to ensure PR titles are consistent and when we merge we set it to always use PR title.

Since I have experience with it, I'd be happy to set it up.

[MatthewSH]

So I decided to tinker a bit and I got release-please basic installed. It's not doing any release work as that's a different task all together but here is an example PR of the current main branch

[MatthewSH]

another alternative is to use something like cliff jumper and doing more manual things if we don't want to offload it all to release-please and want more control.

[Fleny113]

Considering the release of JSR do we plan to publish discordeno to jsr.io?