Bump version to 0.2.27.dev

[rasbt]

Bumps the version so it will be easier for users to differentiate between the latest stable release and the current dev version via the main branch when reporting LitData issues.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78%. Comparing base (c9aaf24) to head (5114841).
Report is 1 commits behind head on main.

Additional details and impacted files

@@         Coverage Diff         @@
##           main   #378   +/-   ##
===================================
  Coverage    78%    78%           
===================================
  Files        34     34           
  Lines      5008   5008           
===================================
  Hits       3928   3928           
  Misses     1080   1080           

[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.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
5685611	Triggered	Generic High Entropy Secret	ecb0e17	tests/streaming/test_resolver.py	View secret
5685611	Triggered	Generic High Entropy Secret	ecb0e17	tests/streaming/test_resolver.py	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 secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
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.}