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

create manifests for v0.1.10 release #61

Merged
merged 1 commit into from
May 9, 2024
Merged

create manifests for v0.1.10 release #61

merged 1 commit into from
May 9, 2024

Conversation

dhij
Copy link
Contributor

@dhij dhij commented May 9, 2024

Ran the IMG_TAG=v0.1.10 make release-manifests command

@dhij dhij requested review from llDrLove and kperath May 9, 2024 12:02
Copy link

gitguardian bot commented May 9, 2024

⚠️ 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
9441144 Triggered Generic High Entropy Secret c608641 releases/do-operator-v0.1.10.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


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

Copy link
Contributor

@kperath kperath left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving - I think the next step is the one where you need to create the 0.1.0 tag

Copy link
Contributor

@llDrLove llDrLove left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@dhij dhij merged commit bd5e135 into main May 9, 2024
2 checks passed
@dhij dhij deleted the ihwang/0.1.10-release branch May 9, 2024 15:01
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.

3 participants