Skip to content

v1.3.3 — Serve API limit consistency + git stop word

Choose a tag to compare

View all tags
@javimosch javimosch released this 28 Jul 12:56
· 26 commits to master since this release
v1.3.3
221b6cb

v1.3.3 — Serve API limit consistency + git stop word

Bug Fixes

Serve API limit=0 returns all results:
/api/search?limit=0 now returns all results (was returning 0). The V2 handler was missing the limit > 0 check before truncating results, so results[:0] produced an empty array. Now consistent with CLI behavior where limit=0 means no limit.

Serve API limit=-1 returns all results:
Negative limits are now treated the same as 0 (no limit), consistent with CLI behavior.

"git" added to stop words:
"GitHub" camelCase-splits to "git"+"hub", and "git" was too common (many skills mention git in their name/description), causing queries like "Deploy Go CLI to GitHub" to match git-best-practices instead of more relevant skills. "git best practices" and "git backup encrypted" queries still return correct results (matched by "best", "practices", "backup" keywords).

Smoke Tests Passed

  • 19 regression queries — all pass
  • 8 serve API limit edge cases (0, -1, abc, 1000, 1, no limit) — all consistent
  • 5 corrupted/missing graph file tests — all handled gracefully
  • 6 import edge cases (invalid JSON, empty, nonexistent, array, missing content) — all return JSON errors
  • 6 session tests (create, list, edit, delete, profile) — all pass
  • 6 French/special char tests — accent stripping works for cognates
  • 3 concurrent CLI tests (10 concurrent, 200ms) — fast
  • Dogfooding: 3/3 correct skill matches (Cloudflare DNS, Go CLI CI/CD, monitoring)

Download

Single static binary — no dependencies, no runtime, no Docker.

Assets 3
Loading