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

feat: search-v2 follow ups #97

Merged
merged 9 commits into from
Jul 25, 2024
Merged

feat: search-v2 follow ups #97

merged 9 commits into from
Jul 25, 2024

Conversation

joshuagraber
Copy link
Collaborator

Includes:

#90
#91
#93
#94
#95

joshuagraber and others added 7 commits June 10, 2024 17:41
resolves #89 

BREAKING CHANGE
Not actually breaking changes, but `2.7.0` should have been a major release (force-pushing mucked things up) so we add it here to bump.
this commit will also trigger a major release: 2.7.0 should have been 3.0.0

BREAKING CHANGE: trigger major release
Copy link

gitguardian bot commented Jul 25, 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
9480360 Triggered Generic Password aeaefc3 src/components/Form/form.spec.ts 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.

@joshuagraber joshuagraber merged commit e6138ad into main Jul 25, 2024
6 of 7 checks passed
Copy link

🎉 This PR is included in version 3.0.0-beta.8 🎉

The release is available on:

Your semantic-release bot 📦🚀

Copy link

🎉 This PR is included in version 3.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants