chore(main): release 2.1.0

[rjaegers]

🤖 I have created a release beep boop

2.1.0 (2023-11-09)

Features

• Add data operations to GattClient (#132) (a1eaaf5)
• Add GATT Client (discovery attributes) (#131) (121c351)
• Add integration tests (#208) (07086ec)
• Add services/st_util/StUartProgammer (#185) (8faceb4)
• Add stm32g0 hal drivers (#118) (35dff48)
• Ble central pairing bonding feature (#163) (530b3bc)
• Configurable clock phase and polarity for sync spi (#200) (cbf6d68)
• Gap and gatt refactored/improved due to embedded-infra changes (#136) (e6c276b)
• Improvements according to application note AN5289 (#135) (bd95621)
• Low power event dispatcher (#156) (a0d1855)
• Merge upstream changes (#126) (1546f51)
• Refactor and expand StUartProgrammer (#202) (5c8c213)
• Removed additional EXCLUDE_FROM_ALL property in favour of using emil_build_for() (8e3766d)
• Update st ble stack (#165) (a6b8827)
• Update the st ble stack to version 1.17 (a6b8827)

Bug Fixes

• Adc on stm32wb (#162) (ee16f2a)
• Add ble middleware binaries (#130) (201687e)
• Add confirmation for gatt indication (#159) (02a98f0)
• Communication over ethernet smi (#129) (9935da5)
• Do not assert if GattCompleteEvent fails (#167) (063daa4)
• Duplicate and misdirected function calls due to listening for events on multiple levels in the inheritance tree of classes using GapSt. (6f8b7f7)
• Event handling of GapSt and its derived classes. (#143) (6f8b7f7)
• Hal_st/stm32fxxx/EthernetSmiStm: ETH_MACMIIAR_CR_Msk is the mask of MACMII->AR, not the inverse (9935da5)
• Incorrect connection handle in state transitions (#147) (2f99452)
• Set privacy mode for bonded devices (#146) (88d30f2)
• Standalone stm32 build and debug (#193) (71bf177)
• Systick conflict with invalidIrq (#161) (8ee04e1)

---

This PR was generated with Release Please. See documentation.

[github-actions]

🦙 MegaLinter status: ⚠️ WARNING

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ ACTION	actionlint	5		0	0.07s
⚠️ MARKDOWN	markdownlint	20	14	4	1.75s
⚠️ MARKDOWN	markdown-link-check	20		14	55.76s
✅ MARKDOWN	markdown-table-formatter	20	14	0	0.31s
✅ REPOSITORY	checkov	yes		no	22.14s
✅ REPOSITORY	dustilock	yes		no	0.08s
✅ REPOSITORY	gitleaks	yes		no	73.69s
✅ REPOSITORY	git_diff	yes		no	0.21s
✅ REPOSITORY	grype	yes		no	19.24s
✅ REPOSITORY	kics	yes		no	40.82s
✅ REPOSITORY	secretlint	yes		no	39.89s
✅ REPOSITORY	syft	yes		no	1.0s
✅ REPOSITORY	trivy	yes		no	4.95s
✅ REPOSITORY	trivy-sbom	yes		no	1.48s
✅ REPOSITORY	trufflehog	yes		no	36.72s
⚠️ SPELL	lychee	86		1	0.12s
✅ XML	xmllint	17	0	0	0.12s
✅ YAML	prettier	7	1	0	0.74s
✅ YAML	v8r	7		0	5.47s
✅ YAML	yamllint	7		0	0.69s

See detailed report in MegaLinter reports

MegaLinter is graciously provided by

[oguzcanoguz]

@rjaegers
Is this PR automatically created or did you trigger it?
If it is automatic, I wonder based on what it is scheduled.
And lastly, what do we need to review for such a release PR?

[rjaegers]

@oguzcanoguz This PR is automatically created by the release-please action (https://github.com/googleapis/release-please). It is scheduled to run for every merge to the main branch. Depending on the conventional commit messages it then determines if it a) has to run and b) has to update the version number. By-default it won't run for types as: ci, build, docs, but it will run for types as: feat, fix.

The action will make sure to keep the PR that is has opened up-to-date by force-pushing newer versions. We only need to review it once we actually want to create the release. Then you merge the PR to main and the release will be created automatically.

I hope this provides you with enough context to understand the process.

[oguzcanoguz]

@rjaegers Thanks, that helps. To better understand, next question is when do we decide to make a release.
Initially I thought every merge with a feat or fix would automatically bump the version. Apparently not and it is in our control.

[rjaegers]

🤖 Release is at https://github.com/philips-software/amp-hal-st/releases/tag/v2.1.0 🌻