26T1-DEV-RL-001 | Move to Oxlint#211
Conversation
CI: Frontend
All checks passed. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: dd7f285539
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| branches: [main] | ||
| paths: | ||
| - 'backend-api/**' | ||
| pull_request: | ||
| branches: [main] |
There was a problem hiding this comment.
This workflow now only runs on main (push and pull_request), so backend checks no longer execute for PRs that target staging or dev. The previous workflow covered those branches, and removing them means integration failures can bypass CI until the final merge into main, which weakens the release gate for the backend module.
Useful? React with 👍 / 👎.
| paths: | ||
| - 'frontend/**' | ||
| - 'backend-api/**' | ||
| - 'engine/**' |
There was a problem hiding this comment.
The workflow claims to scan dependency manifests across the repo, but its paths filter only watches frontend/**, backend-api/**, and engine/**. Dependency changes in other tracked locations (for example security/**, root package-lock.json, or tools/**) will not run this scan on PR/push events, delaying vulnerability detection until the weekly cron.
Useful? React with 👍 / 👎.
2 participants
Summary
Add Oxlint and update CI to use it, instead of Superlint, ESLint and other linting in the project.
Type of Change
Affected Components
/backend-api/frontend/engine(collectors / policies)/security/infrastructure/.github/workflows/docsMotivation
Link to Planner
Testing Done
Security Considerations
No security considerations.
Breaking Changes
Rollback Plan
Checklist