Update release instructions

[Siegrift]

See: #118 (comment)

The instructions are almost correct, but only a few people have access to push directly to main so there should be a workaround to create a PR. Note that merging these versioning PRs should be done using Rebase and Merge strategy to prevent commit hash changing and breaking the git tag (note: it always changes when you use squash and merge).

The release instructions should also mention a new docs release (provided its a major/minor change).

[dcroote]

This could also be fixed by migrating to pnpm and using CD via pnpm publish --provenance per pnpm/pnpm#6435. I'd actually prefer this route.

[Siegrift]

This could also be fixed by migrating to pnpm and using CD

I think that would be a nice to have given the additional work and the amount of releases we do.

merging these versioning PRs should be done using Rebase and Merge strategy to prevent commit hash changing and breaking the git tag

For visibility, I was wrong in the initial comment regarding rebase and merge strategy. In this followup comment you pointed out that that breaks the git tag as well.

I think we can just keep pushing directly to main branch and in a special case people can open a PR and re-tag manually or ask for push to main access.

[dcroote]

I think that would be a nice to have

Agreed, created #122 with the "enhancement" label

I think we can just keep pushing directly to main branch and in a special case people can open a PR and re-tag manually or ask for push to main access.

Agreed

[Siegrift]

Also mention to run yarn before building the package to make sure dependencies are fresh. See https://github.com/api3dao/airnode/pull/1914/files#r1410222824

[dcroote]

I think we can say this has been closed by #137 since the README is now updated with instructions using the GitHub Actions publishing with provenance flow.