refactor: Upgrade connectivity_plus

[mbfakourii]

Pull Request

• Report security issues confidentially.
• Any contribution is under this license.
• Link this pull request to an issue.

Issue

Closes: #972

Approach

Upgrade connectivity plus to 5.0.1

Tasks

• Add tests
• Add changes to documentation (guides, repository pages, code comments)

[parse-github-assistant]

Thanks for opening this pull request!

[codecov]

Codecov Report

All modified lines are covered by tests ✅

Comparison is base (9431086) 40.60% compared to head (2ea5cab) 40.60%.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #974   +/-   ##
=======================================
  Coverage   40.60%   40.60%           
=======================================
  Files          60       60           
  Lines        3401     3401           
=======================================
  Hits         1381     1381           
  Misses       2020     2020           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[mbfakourii]

@mtrezza

Can you give me access to execute the CI file?
I have to commit again to run CI! [1]

[mtrezza]

You can close and re-open the PR to re-run the CI. Why do you need to re-run the CI in the first place, do we have a flaky test?

[mbfakourii]

You can close and re-open the PR to re-run the CI. Why do you need to re-run the CI in the first place, do we have a flaky test?

In this action run, I encountered a codecov error and had to run CI again !

[mtrezza]

Looks good, this is only an internal package, so no breaking change?

The CI issue looks like a temporary service issue that self-resolved.

[mbfakourii]

Looks good, this is only an internal package, so no breaking change?

The CI issue looks like a temporary service issue that self-resolved.

No, there is no problem, I think it is ready for merge.

[mtrezza]

If this should be released immediately then the fix PR requires a changelog entry. Otherwise you can make it a refactor to release it with the next fix or feat PR.

[mbfakourii]

If this should be released immediately then the fix PR requires a changelog entry. Otherwise you can make it a refactor to release it with the next fix or feat PR.

I think it is a refactor and there is no need for versioning.