-
Notifications
You must be signed in to change notification settings - Fork 16
staging PR (03-11-2025) #2212
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
staging PR (03-11-2025) #2212
Conversation
Fix: Added test cases for Entries helper
Fix: Added Tests for Stack module
Fix: Added Test cases for environments module
feat: add test cases base-class and asssets for export module
Fix: Added Tests for Locales module
chore: add test cases for envs, extensions, locales,stacks, taxonomies and webhooks
chore: add test cases for global-fields, custom roles, workflows, content-types
Fix/merge conflicts and back merge from staging to development
…pdated Workflow cases
Tests: Added Unit Test cases for Extensions Webhooks Taxonomies and Updated Workflow cases
Tests: Added unit test cases for personalize, variant-entries and index
chore: add test cases for utils
DX - 3669 - Added Unit Test cases for Module importer
Devex | Hotfix Release | 29 Oct 2025
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 21937205 | Triggered | Generic Password | c2b979a | pnpm-lock.yaml | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- 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.
Fix/back merge
|
closing this PR as there's only test cases updates |
No description provided.