pjandro/OmniRoute
1
0
Fork 0
mirror of https://github.com/diegosouzapw/OmniRoute.git synced 2026-07-26 09:52:11 +03:00
Code Issues Packages Projects Releases Wiki Activity

chore(agents): remove obsolete workflow playbooks

Browse Source 
Delete the fix-ci and Node 22 CLI entrypoint workflow documents
from .agents/workflows to clean up outdated internal guidance on the
release branch.
This commit is contained in:
diegosouzapw
2026-04-23 08:48:15 -03:00
parent a42ef13b61
commit 05005acabd
2 changed files with 0 additions and 209 deletions
Download Patch File Download Diff File Expand all files Collapse all files

182
.agents/workflows/fix-ci.md
View File

@@ -1,182 +0,0 @@
# Fix CI Workflow
Look up the latest GitHub Actions CI run for the current release branch, diagnose all failures, fix them locally, push, and wait for the new CI run to go green before notifying the user.
---
## Phase 1: Identify the Failing CI Run
### 1. Determine the current release version and branch
// turbo
```bash
cd /home/diegosouzapw/dev/proxys/9router
VERSION=$(node -p "require('./package.json').version")
BRANCH=$(git branch --show-current)
echo "Version: $VERSION"
echo "Branch: $BRANCH"
```
### 2. Find the latest CI run for the release PR
// turbo
```bash
cd /home/diegosouzapw/dev/proxys/9router
# Find the PR number for the release branch
PR_NUMBER=$(gh pr list --repo diegosouzapw/OmniRoute --head "$BRANCH" --json number --jq '.[0].number')
echo "PR: #$PR_NUMBER"
# Get the latest CI run
RUN_ID=$(gh run list --repo diegosouzapw/OmniRoute --branch "$BRANCH" --workflow ci.yml --limit 1 --json databaseId --jq '.[0].databaseId')
echo "Latest CI Run: $RUN_ID"
echo "URL: https://github.com/diegosouzapw/OmniRoute/actions/runs/$RUN_ID"
```
---
## Phase 2: Diagnose Failures
### 3. List all failing jobs
// turbo
```bash
cd /home/diegosouzapw/dev/proxys/9router
RUN_ID=$(gh run list --repo diegosouzapw/OmniRoute --branch "$(git branch --show-current)" --workflow ci.yml --limit 1 --json databaseId --jq '.[0].databaseId')
gh run view "$RUN_ID" --repo diegosouzapw/OmniRoute --json jobs --jq '.jobs[] | select(.conclusion == "failure") | {name: .name, conclusion: .conclusion, steps: [.steps[] | select(.conclusion == "failure") | .name]}'
```
### 4. Download and analyze failure logs
// turbo
```bash
cd /home/diegosouzapw/dev/proxys/9router
RUN_ID=$(gh run list --repo diegosouzapw/OmniRoute --branch "$(git branch --show-current)" --workflow ci.yml --limit 1 --json databaseId --jq '.[0].databaseId')
gh run view "$RUN_ID" --repo diegosouzapw/OmniRoute --log-failed 2>&1 | grep -aE "not ok|FAIL|Error:|error:|AssertionError|expected|actual" | grep -v "node_modules\|runner\|git version" | head -50
```
### 5. Classify each failure
For each failing job, determine the root cause category:
| Category | Pattern | Fix Strategy |
| ------------------ | ---------------------------------- | ------------------------------------------ |
| **docs-sync** | OpenAPI/CHANGELOG version mismatch | Run `/version-bump` step 7-8 |
| **Test assertion** | `not ok` + `AssertionError` | Update test expectations to match new code |
| **E2E flaky** | Auth-related 401/403/307 | Make tests tolerate auth states |
| **Coverage gate** | `below threshold` | Add more tests or adjust threshold |
| **Lint** | ESLint errors | Fix code or update rules |
| **Build** | Compilation errors | Fix TypeScript issues |
---
## Phase 3: Apply Fixes
### 6. Fix each failure
For each classified failure:
1. **Read the failing test file** to understand the assertion
2. **Read the production source** to understand the new behavior
3. **Update the test** to match the current behavior
4. **Run the test locally** to verify the fix
// turbo
```bash
cd /home/diegosouzapw/dev/proxys/9router
# Run the specific failing test file(s) to confirm fixes
# Example: node --import tsx/esm --test tests/unit/FAILING_FILE.test.mjs
```
### 7. Run the full local test suite
// turbo
```bash
cd /home/diegosouzapw/dev/proxys/9router
npm test
```
### 8. Run docs-sync check
// turbo
```bash
cd /home/diegosouzapw/dev/proxys/9router
npm run check:docs-sync
```
---
## Phase 4: Push and Monitor
### 9. Commit and push fixes
// turbo-all
```bash
cd /home/diegosouzapw/dev/proxys/9router
git add -A
git commit -m "fix(tests): align CI tests with release changes"
git push origin "$(git branch --show-current)"
```
### 10. Wait for CI to trigger and find the new run
// turbo
```bash
cd /home/diegosouzapw/dev/proxys/9router
sleep 15
BRANCH=$(git branch --show-current)
NEW_RUN_ID=$(gh run list --repo diegosouzapw/OmniRoute --branch "$BRANCH" --workflow ci.yml --limit 1 --json databaseId --jq '.[0].databaseId')
echo "New CI Run: $NEW_RUN_ID"
echo "URL: https://github.com/diegosouzapw/OmniRoute/actions/runs/$NEW_RUN_ID"
```
### 11. Monitor the CI run
// turbo
```bash
cd /home/diegosouzapw/dev/proxys/9router
BRANCH=$(git branch --show-current)
NEW_RUN_ID=$(gh run list --repo diegosouzapw/OmniRoute --branch "$BRANCH" --workflow ci.yml --limit 1 --json databaseId --jq '.[0].databaseId')
gh run watch "$NEW_RUN_ID" --repo diegosouzapw/OmniRoute --exit-status
```
If `gh run watch` exits with 0, the CI is green. If it exits with non-zero, go back to Phase 2 and repeat.
### 12. 🛑 STOP — Notify User
Present a summary to the user:
- **Previous CI run**: URL, list of failures
- **Root causes**: What broke and why
- **Fixes applied**: What tests were changed
- **New CI run**: URL, all-green status
- **PR status**: Ready for review/merge
---
## Common CI Failure Patterns
| Failure | Root Cause | Fix |
| ------------------------------------------ | -------------------------------------- | ----------------------------- |
| `docs-sync FAIL - OpenAPI version differs` | Version not synced after bump | `sed -i` openapi.yaml |
| `docs-sync FAIL - CHANGELOG first section` | Missing `## [Unreleased]` header | Add unreleased section |
| `not ok - cleanupExpiredLogs` | Return shape changed (new fields) | Update `assert.deepEqual` |
| `not ok - email masking` | Email now masked in call logs | Assert masked pattern instead |
| `E2E /api/providers` returns non-200 | Auth enabled in CI, endpoint protected | Accept 401/403 as valid |
| `coverage below 60%` | New untested code | Add unit tests |
## Notes
- This workflow is **iterative**: if the first fix attempt doesn't clear all failures, repeat Phases 2-4.
- Always run tests **locally** before pushing to avoid wasting CI minutes.
- The CI is triggered automatically on push to branches with open PRs to `main`.
- Use `gh run watch` to monitor in real-time instead of polling.

27
.agents/workflows/fix-cli-node22-ts-entrypoint.md
View File

@@ -1,27 +0,0 @@
# Workflow: Fix CLI Node 22 TS Entrypoint Issue
## Issue Description
In OmniRoute >= 3.6.6, the `package.json` declares the main CLI binary as `bin/omniroute.ts`. While Node 22 introduced experimental support for executing TypeScript files natively via the `--experimental-strip-types` flag (and `--experimental-transform-types`), Node.js explicitly disables this feature for any files loaded from inside a `node_modules` directory.
When users install `omniroute` globally (or locally) via npm, the CLI shim points to `bin/omniroute.ts` inside `node_modules`. Running `omniroute` on Node 22 results in:
`Error [ERR_UNSUPPORTED_NODE_MODULES_TYPE_STRIPPING]: Stripping types is currently unsupported for files under node_modules`
This makes the CLI completely unusable out-of-the-box on Node 22, despite the `engines` field claiming support for `>=22.22.2`.
## Proposed Solution
The CLI entrypoint distributed in the NPM package must be a JavaScript file, not a TypeScript file.
1. Restore `bin/omniroute.mjs` as the actual CLI entrypoint, or implement a build step during `npm run build:cli` that compiles `bin/omniroute.ts` to `bin/omniroute.mjs` before publishing.
2. Update `package.json` to point the `bin` field back to the compiled `.js`/`.mjs` file:
```json
"bin": {
"omniroute": "bin/omniroute.mjs"
}
```
3. Ensure `scripts/prepublish.ts` handles the compilation or validation of the binary entrypoint correctly so this regression doesn't happen again.
## Task
Please implement this fix, ensure the tests pass, and create a Pull Request against the main branch.