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

Upgrade l10 l11 #798

Closed
wants to merge 24 commits into from
Closed

Upgrade l10 l11 #798

wants to merge 24 commits into from

Conversation

charlesstrange2
Copy link
Contributor

The body of the work to move from l10-l11

There's a lot of migration and test-based farce to do with the fact they dropped DBAL as an abstraction layer
DBAL was clearly doing magic error handling so SQLite and MySQL required more precise management / different functions in migrations.

you'll want to look at this one first
#797

Copy link

gitguardian bot commented Jan 10, 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
9563242 Triggered Generic Password 7a1d17c .env.ghactions 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.

@charlesstrange2 charlesstrange2 deleted the upgrade-L10-L11 branch January 14, 2025 09:55
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