Release 1.2.1

[solarw]

Proposed changes

Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request.

Fixes

If it fixes a bug or resolves a feature request, be sure to link to that issue.

Types of changes

What types of changes does your code introduce to agents-aea? Put an x in the boxes that apply

• [ ] Bugfix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

Put an x in the boxes that apply.

• [ ] I have read the CONTRIBUTING doc
• [ ] I am making a pull request against the develop branch (left side). Also you should start your branch off our develop.
• [ ] Lint and unit tests pass locally with my changes and CI passes too
• [ ] I have added tests that prove my fix is effective or that my feature works
• [ ] I have checked that code coverage does not decrease.
• [ ] I have added necessary documentation (if appropriate)
• [ ] Any dependent changes have been merged and published in downstream modules

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

DELETE INCLUSIVE THIS AND BELOW FOR STANDARD PR

Release summary

Version number: [e.g. 1.0.1]

Release details

Describe in short the main changes with the new release.

Checklist

Put an x in the boxes that apply.

• [ ] I have read the CONTRIBUTING doc
• [ ] I am making a pull request against the main branch (left side), from develop
• [ ] Lint and unit tests pass locally and in CI
• [ ] I have checked the fingerprint hashes are correct by running (scripts/generate_ipfs_hashes.py)
• [ ] I have regenerated the latest API docs
• [ ] I built the documentation and updated it with the latest changes
• [ ] I have added an item in HISTORY.md for this release
• [ ] I bumped the version number in the aea/__version__.py file.
• [ ] I bumped the version number in every Docker image of the repo and published it. Also, I built and published them with tag latest
  (check the READMEs of aea-develop and aea-user)
• [ ] I have pushed the latest packages to the registry.
• [ ] I have uploaded the latest aea to PyPI.
• [ ] I have uploaded the latest plugins to PyPI.

Further comments

Write here any other comment about the release, if any.

[codecov-commenter]

Codecov Report

Merging #2753 (fbf953e) into main (8a60889) will decrease coverage by 0.38%. The diff coverage is 81.57%.

@@            Coverage Diff             @@
##             main    #2753      +/-   ##
==========================================
- Coverage   98.46%   98.07%   -0.39%     
==========================================
  Files         522      540      +18     
  Lines       36300    37539    +1239     
==========================================
+ Hits        35742    36818    +1076     
- Misses        558      721     +163     

Flag	Coverage Δ
unittests	98.07% <81.57%> (-0.39%)	:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
aea/protocols/generator/common.py	100.00% <ø> (ø)
packages/fetchai/protocols/acn/__init__.py	100.00% <ø> (ø)
packages/fetchai/protocols/aggregation/__init__.py	100.00% <ø> (ø)
...s/fetchai/protocols/aggregation/aggregation_pb2.py	69.56% <ø> (ø)
...ackages/fetchai/protocols/contract_api/__init__.py	100.00% <ø> (ø)
...fetchai/protocols/contract_api/contract_api_pb2.py	57.14% <ø> (ø)
packages/fetchai/protocols/cosm_trade/__init__.py	100.00% <ø> (ø)
...ges/fetchai/protocols/cosm_trade/cosm_trade_pb2.py	62.85% <ø> (ø)
packages/fetchai/protocols/default/__init__.py	100.00% <ø> (ø)
packages/fetchai/protocols/fipa/__init__.py	100.00% <ø> (ø)
... and 142 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update 8a60889...fbf953e. Read the comment docs.

[5A11]

that'd be great to fill the PR descriptions with some helpful stuff for history/search/and people not following closely the project to get an idea of what's going on.

Absolutely right! We will enforce this from now on :)