feat(ci): add release github workflow

[andreiltd]

Closes: #95

Release-As: 0.2.0

[andreiltd]

For reference

• release on my fork: https://github.com/andreiltd/StarlingMonkey/releases/tag/v0.2.0
• release PR created by workflow: chore(main): release 0.2.0 andreiltd/StarlingMonkey#22

[vados-cosmonic]

LGTM 🚀

Left some nits but in general release-please is a great choice

[tschneidereit]

Thank you for doing this! As mentioned inline, I would prefer keeping the name starling.wasm, but other than that I think we should land this and iterate from there.

[andreiltd]

We should probably start using https://www.conventionalcommits.org/en/v1.0.0/ from now on :)

[andreiltd]

Hey @tschneidereit would you prefer landing this before or after ff140 update?

Edit: BTW I'm happy with either, I just thought it would be useful to have a tag/release before this substantial change, to have a last release with weval clearly labeled.

[tschneidereit]

@andreiltd I agree that landing this before makes sense, so feel free to do that at any point.

[andreiltd]

D'oh! This failed on main on creating a pull request despite the permissions for a job are explicitly granted:

    permissions:
      contents: write
      issues: write
      pull-requests: write

@vados-cosmonic do you know if this also requires allowing jobs to create a pull request in the repository settings? How jco and componentize-js are configured?

[vados-cosmonic]

I think what you're missing there is repository configuration! I think in your case it it may be this:

https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#managing-github-actions-permissions-for-your-repository

An image of what that section looks like (under https://github.com/<org>/<repo>/settings/actions):

We use a bot user in Jco, but I actually don't think Release Please requires that -- See their instructions and this sentence in particular:

If your repository is in an organization, you may need to permit github actions to create an approve PRs.

If that's already set for StarlingMonkey, then maybe you might need a bot user/explicitly permissioned token!