Merge main into develop

[ami-ci]

Automatically syncing these 2 branches failed by the CI server. Merge this pull request manually instead.

[codecov[bot]]

Codecov Report

Merging #110 (ab3cd18) into develop (79ebdec) will decrease coverage by 52.99%. The diff coverage is 10.00%.

:exclamation: Current head ab3cd18 differs from pull request most recent head a286e4a. Consider uploading reports for the commit a286e4a to get more accurate results

@@              Coverage Diff               @@
##             develop     #110       +/-   ##
==============================================
- Coverage      64.72%   11.73%   -53.00%     
+ Complexity       129        7      -122     
==============================================
  Files             63        8       -55     
  Lines           1222      179     -1043     
  Branches         132       22      -110     
==============================================
- Hits             791       21      -770     
+ Misses           366      155      -211     
+ Partials          65        3       -62     

Impacted Files	Coverage Δ
...messagingpush/CustomerIOPushNotificationHandler.kt	0.00% <0.00%> (ø)
...o/customer/messagingpush/CustomerIOPushReceiver.kt	2.85% <0.00%> (ø)
...ava/io/customer/base/extenstions/DateExtensions.kt	90.90% <50.00%> (-9.10%)	:arrow_down:
sdk/src/main/java/io/customer/sdk/CustomerIO.kt
...stomer/sdk/CustomerIOActivityLifecycleCallbacks.kt
.../src/main/java/io/customer/sdk/CustomerIOConfig.kt
...ain/java/io/customer/sdk/di/CustomerIOComponent.kt
sdk/src/main/java/io/customer/sdk/di/DiGraph.kt
sdk/src/main/java/io/customer/sdk/queue/Queue.kt
...rc/main/java/io/customer/sdk/queue/QueueStorage.kt
... and 47 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 79ebdec...a286e4a. Read the comment docs.

[ami-ci]

:tada: This PR is included in version 2.1.0-alpha.1 :tada:

The release is available on GitHub release

Your semantic-release bot :package::rocket:

[ami-oss-ci]

Pull request title looks good 👍!

If this pull request gets merged, it will not cause a new release of the software. Example: If this project's latest release version is 1.0.0. If this pull request gets merged in, the next release of this project will be 1.0.0. This pull request is not a breaking change.

All merged pull requests will eventually get deployed. But some types of pull requests will trigger a deployment (such as features and bug fixes) while some pull requests will wait to get deployed until a later time.

To merge this pull request, add the label Ready to merge to this pull request and I'll merge it for you.

This project uses a special format for pull requests titles. Expand this section to learn more (expand by clicking the ᐅ symbol on the left side of this sentence)...

This project uses a special format for pull requests titles. Don't worry, it's easy! This pull request title should be in this format: ``` : short description of change being made ``` **If your pull request [introduces breaking changes](https://web.archive.org/web/20220725195319/https://nordicapis.com/what-are-breaking-changes-and-how-do-you-avoid-them/)** to the code, use this format: ``` !: short description of breaking change ``` where `` is one of the following: - `feat:` - A feature is being added or modified by this pull request. Use this if you made any changes to any of the features of the project. - `fix:` - A bug is being fixed by this pull request. Use this if you made any fixes to bugs in the project. - `docs:` - This pull request is making documentation changes, only. - `refactor:` - A change was made that doesn't fix a bug or add a feature. - `test:` - Adds missing tests or fixes broken tests. - `style:` - Changes that do not effect the code (whitespace, linting, formatting, semi-colons, etc) - `perf:` - Changes improve performance of the code. - `build:` - Changes to the build system (maven, npm, gulp, etc) - `ci:` - Changes to the CI build system (Travis, GitHub Actions, Circle, etc) - `chore:` - Other changes to project that don't modify source code or test files. - `revert:` - Reverts a previous commit that was made. ### Examples: ``` feat: edit profile photo refactor!: remove deprecated v1 endpoints build: update npm dependencies style: run formatter ``` Need more examples? Want to learn more about this format? [Check out the official docs](https://www.conventionalcommits.org/). **Note:** If your pull request does multiple things such as adding a feature _and_ makes changes to the CI server _and_ fixes some bugs then you might want to consider splitting this pull request up into multiple smaller pull requests.

[ami-ci]

:tada: This PR is included in version 2.1.0-beta.1 :tada:

The release is available on GitHub release

Your semantic-release bot :package::rocket:

[ami-ci]

:tada: This PR is included in version 2.1.0 :tada:

The release is available on GitHub release

Your semantic-release bot :package::rocket: