Unify product version at 1.4.0, add ruff gate, drop stale GitHub workflow
CI / automation-js (vitest + real Chromium) (pull_request) Successful in 1m15s
CI / Lint + tests (pull_request) Successful in 10m42s

- One version (1.4.0) across extension/manifest.json, automation/pyproject.toml,
  automation-js/package.json (+lockfile); README documents the bump-together policy
- Delete .github/workflows/ci.yml (behind the Gitea copy; CI runs on Gitea Actions)
- CURSOR_PROMPT.md: replace personal paths with <path-to-context-extractor>
- Add ruff (E4,E7,E9,F,I, line-length 120) to automation/ dev extras, Makefile lint,
  and the Gitea CI Lint + tests job as a hard gate
This commit is contained in:
2026-07-26 15:47:37 -04:00
parent 8dec923061
commit d26d1aaa4e
10 changed files with 30 additions and 89 deletions
+9 -1
View File
@@ -46,6 +46,14 @@ place to fix a markdown-formatting bug, and the Python/JS test suites both
run against the same fixture page (`automation/tests/fixtures/sample.html`)
so a regression can't silently diverge between the two.
## Versioning
The extension (`extension/manifest.json`), the Python package
(`automation/pyproject.toml`), and the Node package
(`automation-js/package.json`) share **one product version** and are bumped
together — they ship the same `core/*.js`, so a version like `1.4.0` means
the same extraction behavior in all three.
## Use from another Cursor project
Copy the block in [`CURSOR_PROMPT.md`](CURSOR_PROMPT.md) into that project's chat
@@ -55,7 +63,7 @@ Copy the block in [`CURSOR_PROMPT.md`](CURSOR_PROMPT.md) into that project's cha
```bash
make install # once
make ci # lint + pytest + package smoke (same checks as GitHub Actions)
make ci # lint + pytest + vitest + package smoke (same checks as Gitea Actions)
```
Or manually: