chore(release): publish v2.1.0

[petermetz]

Signed-off-by: Peter Somogyvari [email protected]

Pull Request Requirements

• Rebased onto upstream/main branch and squashed into single commit to help maintainers review it more efficient and to avoid spaghetti git commit graphs that obfuscate which commit did exactly what change, when and, why.
• Have git sign off at the end of commit message to avoid being marked red. You can add -s flag when using git commit command. You may refer to this link for more information.
• Follow the Commit Linting specification. You may refer to this link for more information.

Character Limit

• Pull Request Title and Commit Subject must not exceed 72 characters (including spaces and special characters).
• Commit Message per line must not exceed 80 characters (including spaces and special characters).

A Must Read for Beginners
For rebasing and squashing, here's a must read guide for beginners.

[petermetz]

@hyperledger-cacti/cacti-maintainers bump

[sandeepnRES]

@petermetz Hey, is something wrong with mergefreeze? On the site it shows this PR is unfrozen, but mergrefreeze status isn't passed.

[jagpreetsinghsasan]

LGTM

[petermetz]

@petermetz Hey, is something wrong with mergefreeze? On the site it shows this PR is unfrozen, but mergrefreeze status isn't passed.

@sandeepnRES Good catch, thank you for noticing! I went and investigated and turns out for some reason mergefreeze was removed from the list of required checks (settings -> branch protection rules). I've added it back and now it works as it should. Phew, I'm glad we noticed that before accidentally merging another PR (because then I'd have to re-do the entire release PR from scratch)