chore(main): release 2.21.0

[github-actions]

🤖 I have created a release beep boop

What's Changed

• feat: Moving from ipfs-http-client -> kubo-rpc-client by @whizzzkid in feat: Moving from ipfs-http-client -> kubo-rpc-client #1124
• fix: removed state change notifications by @whizzzkid in fix: removed state change notifications #1123
• feat: add E2E tests for chromium and firefox by @galargh in feat: add E2E tests for chromium and firefox #1121
• chore: CODEOWNER meandavejustice->whizzzkid by @SgtPooki in chore: CODEOWNER meandavejustice->whizzzkid #1135
• fix: 🐛 waiting for test to finish for longer by @whizzzkid in fix: 🐛 waiting for test to finish for longer #1136
• chore: add sourceMaps to dev-builds by @SgtPooki in chore: add sourceMaps to dev-builds #1134
• chore: update PRIVACY-POLICY.md by @SgtPooki in chore: update PRIVACY-POLICY.md #1137
• feat: add telemetry to companion by @SgtPooki in feat: add telemetry to companion #1117

New Contributors

• @galargh made their first contribution in feat: add E2E tests for chromium and firefox #1121

Full Changelog: v2.20.1...v2.21.0

---

This PR was generated with Release Please. See documentation.

[whizzzkid]

I am not sure why it's unable to recognize the previous release.

[whizzzkid]

Looks like tag v2.21.0 points to -> 50dcfb1 which reads:

This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

I dunno why that is, because, this https://github.com/ipfs/ipfs-companion/pull/1147/commits should've fixed it. Now we can look into moving the tag ahead of current commit.

The fix looks like: https://stackoverflow.com/a/25849917/1114922 but maybe not worth the hassle. I think the last release that happened, the PR was missed.

[whizzzkid]

@lidel this needs to be skipped?

[lidel]

Also, why don't we have a version entry in the package.json?

It is a legacy thing (from the time before v2) – NPM was not very useful back then.

@whizzzkid I think it will be easier for interop with release tools if you move the "source of truth" for version to package.json and then make sure the build applies value from package.json to add-on/manifest.common.json.

Ok to do that in the future PR.

[lidel]

@whizzzkid I merged #1125. The code was added to this PR as expected, but information about #1125 was not added to "What's Changed" in the first comment of this PR and the CHANGELOG was also not updated.

We should fix this before making a release.

[whizzzkid]

Closing this PR.