Skip to content

v1.3.3

Choose a tag to compare

@github-actions github-actions released this 12 Nov 12:11
a7b9cf7

Fixed

  • codive upgrade no longer fails on slower networks or hides why it failed. A single 10-second timeout covered the whole download, so the 6.5 MB release archive could time out, and every failure was reported as "asset not found" with advice to run go install. The version check (15 s) and the download (5 min) now have separate timeouts, transient errors and 5xx responses are retried 3 times, the real cause (for example HTTP 404 or a timeout) is printed, and the command exits non-zero on failure. The fallback hint now points to the installer (irm https://recscse.github.io/codive/install.ps1 | iex or curl -fsSL https://recscse.github.io/codive/install.sh | sh) and the releases page, so users no longer need Go installed. If you are on v1.2.0, run the installer once to get this fix.

Changed

  • Releases are automatic. Merging to main with a new Version in main.go runs the tests on Linux, macOS and Windows, builds all five platform archives with SHA-256 files, publishes the GitHub release with these notes plus the generated list of merged changes, and then downloads the published archives on each OS to check the checksum and that the binary runs. A version without a changelog section stops the release, and a test catches it on the PR.
  • CI now runs on every push, not just on main.

Added

  • codive bench measures intent search on the repository's own history. Each recent commit becomes a question: the subject (minus prefixes such as fix(mcp):) is the query, and the definitions the commit changed, if they still exist, are the right answers. Docs, chore, merge and broad-refactor commits are skipped. The report shows how often the right function and the right file rank 1st, in the top 3 and in the top 10, next to a grep-style baseline that ranks files by how often the query's words appear. It logs nothing, so it never feeds the ranker. Measured with the starting weights:
    • go-chi/chi, 306 questions: the right function ranked first 35% of the time and in the top 3 53%. The right file ranked first 51% of the time, against 17% for the grep-style baseline.
    • spf13/cobra, 210 questions: the right function ranked first 17% of the time and in the top 3 37%. The right file ranked first 43% of the time, against 28% for the baseline.
  • codive ranker history trains the intent ranker on git history, so ranking can improve on day one instead of waiting for 20 real uses. Test functions don't count as right answers: commits change a test alongside the code, but an agent asking where something happens wants the code. Without this rule, training made ranking worse. The trained model is kept only if it ranks held-out commits better. Held-out MRR went from 0.57 to 0.66 on chi and from 0.43 to 0.63 on cobra. After training, codive bench scores the same commits it learned from; use CODIVE_LEARNING=off codive bench to see the starting weights.

What's Changed

  • Measure intent search on git history; train the ranker from it by @recscse in #7
  • Feat/intent bench by @recscse in #8

Full Changelog: v1.3.2...v1.3.3