Issue #69: V5 release updates

[alexmerlin]

No description provided.

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
15736006	Triggered	Bearer Token	8943cd2	docs/book/v5/extra/header.md	View secret
15736006	Triggered	Bearer Token	8943cd2	docs/book/v5/extra/header.md	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[alexmerlin]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.
🔎 Detected hardcoded secret in your pull request

GitGuardian id GitGuardian status Secret Commit Filename
15736006 Triggered Bearer Token 8943cd2 docs/book/v5/extra/header.md View secret
🛠 Guidelines to remediate hardcoded secrets

🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

The exposed secret is purely demonstrative, it does not provide access to a real resource - the warning can be ignored.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.42%. Comparing base (b0e9f3b) to head (40d9945).
⚠️ Report is 25 commits behind head on 4.1.

Additional details and impacted files

@@             Coverage Diff              @@
##                4.1      #70      +/-   ##
============================================
- Coverage     98.46%   98.42%   -0.05%     
  Complexity      117      117              
============================================
  Files            20       20              
  Lines           326      317       -9     
============================================
- Hits            321      312       -9     
  Misses            5        5              

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[arhimede]

@alexmerlin
please update the readme on the 4.1 branch
to reflect the versions and combinations
https://github.com/dotkernel/dot-errorhandler