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

Release #7043

Merged
merged 44 commits into from
Oct 27, 2023
Merged

Release #7043

merged 44 commits into from
Oct 27, 2023

Conversation

evereq
Copy link
Member

@evereq evereq commented Oct 27, 2023

PR

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.


rahul-rocket and others added 30 commits October 12, 2023 16:39
@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
3 out of 4 committers have signed the CLA.

✅ adkif
✅ rahul-rocket
✅ evereq
❌ dependabot[bot]
You have signed the CLA already but the status is still pending? Let us recheck it.

@evereq evereq merged commit 6ade27b into master Oct 27, 2023
5 checks passed
@gitguardian
Copy link

gitguardian bot commented Oct 27, 2023

⚠️ GitGuardian has uncovered 5 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 Secret Commit Filename
7421875 Google API Key 3b969e7 .render/render.demo.yaml View secret
7421875 Google API Key 23ddbae render.yaml View secret
7421875 Google API Key f04fd62 .render/render.demo.yaml View secret
7421875 Google API Key f04fd62 render.yaml View secret
7421875 Google API Key df74cac .render/render.demo.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 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


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

Our GitHub checks need improvements? Share your feedbacks!

@nx-cloud
Copy link

nx-cloud bot commented Oct 27, 2023

☁️ Nx Cloud Report

CI is running/has finished running commands for commit df74cac. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution


🟥 Failed Commands
nx serve api -c=production --prod

Sent with 💌 from NxCloud.

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.

4 participants