Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

upd readme #133

Merged
merged 18 commits into from
Jan 5, 2025
Merged

upd readme #133

merged 18 commits into from
Jan 5, 2025

Conversation

AndreiDrang
Copy link
Owner

No description provided.

AndreiDrang and others added 16 commits December 19, 2024 20:01
Bumps [pydantic](https://github.com/pydantic/pydantic) from 2.10.3 to 2.10.4.
- [Release notes](https://github.com/pydantic/pydantic/releases)
- [Changelog](https://github.com/pydantic/pydantic/blob/main/HISTORY.md)
- [Commits](pydantic/pydantic@v2.10.3...v2.10.4)

---
updated-dependencies:
- dependency-name: pydantic
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
Updates the requirements on [msgspec](https://github.com/jcrist/msgspec) to permit the latest version.
- [Release notes](https://github.com/jcrist/msgspec/releases)
- [Commits](jcrist/msgspec@0.18.0...0.19.0)

---
updated-dependencies:
- dependency-name: msgspec
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
….18-and-lt-0.20

Update msgspec requirement from ==0.18.* to >=0.18,<0.20
Copy link

gitguardian bot commented Jan 5, 2025

⚠️ 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
9190932 Triggered Generic High Entropy Secret 734e915 src/python3_capsolver/aws_waf.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


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

@AndreiDrang AndreiDrang merged commit c7fba25 into release Jan 5, 2025
12 of 15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant