Prepare release v4.14.0 - Redo

[okamidash]

[gitguardian[bot]]

⚠️ GitGuardian has uncovered 3 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
17169875	Triggered	Docker Swarm Unlock Key	206b5ab2e451d95eadf4f665bb274e8b0c6a004e	vendor/github.com/docker/docker/api/swagger.yaml	View secret
17169876	Triggered	Docker Swarm Join Token	206b5ab2e451d95eadf4f665bb274e8b0c6a004e	vendor/github.com/docker/docker/api/swagger.yaml	View secret
17169877	Triggered	Username Password	206b5ab2e451d95eadf4f665bb274e8b0c6a004e	vendor/github.com/docker/docker/api/swagger.yaml	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.}