Prep 0.2.0 release: document snippets, bump version, fix CI runners#32
Conversation
Snippets shipped to main in #30 but the docs, version, and a broken CI config were never updated. This gets main release-ready for v0.2.0. Docs: - README: Snippets CLI section (list snippets/snippet-paths/ snippet-locations, get snippet/snippet-match), MCP tools table (snippet on `list`, the `snippet_match` tool, no get/update), and the Snippet locator - CLAUDE.md: ERD, architecture tree, the four snippet endpoints, the Snippet model entry with its API quirks, and Future Work Version: 0.1.0 -> 0.2.0 (Cargo.toml + Cargo.lock) CI runner fix: dist 0.27 defaults to ubuntu-20.04 and windows-2019, both retired by GitHub, so every Release-workflow job queued until the 24h timeout and the PR `plan` check sat "pending" indefinitely. Pin supported images via [workspace.metadata.dist.github-custom-runners] (ubuntu-22.04 / macos-13 / macos-14 / windows-2022) and regenerate release.yml. `dist generate --check` is clean; `dist plan` now assigns only hosted runners. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Caution Review failedPull request was closed or merged during review WalkthroughThis PR documents snippet matching functionality across the FOSSA API client and updates release infrastructure. The changes add an ER diagram and API endpoint documentation for querying snippets and their matches, introduce CLI and MCP usage guidance for end users, bump the crate version to 0.2.0, configure cargo-dist to use standardized GitHub-hosted runners per platform, and update the release workflow to use Ubuntu 22.04 instead of Ubuntu 20.04 for primary build jobs. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
Snippet support already merged to
mainin #30, but the docs, the version number, and a broken CI runner config were never updated. This makesmainrelease-ready for v0.2.0 and unblocks the hanging PR check.Docs
list snippets/snippet-paths/snippet-locations --with-lines,get snippet/snippet-match); MCP Available Tools table (snippetonlist, thesnippet_matchtool, note that snippets are list/drill-in only); Snippet locator.Revision → Snippet → SnippetMatch), architecture tree, the four snippet endpoints, theSnippetmodel entry with its API quirks (stringid,matchPercentage0–100 vs 0–1, trailing-blank-EOF off-by-one), and Future Work.Version
0.1.0→0.2.0(Cargo.toml + Cargo.lock).CI runner fix
The Release workflow pinned
ubuntu-20.04(4 jobs) and, viadist plan,windows-2019— both retired by GitHub. Jobs requesting them queue until the 24h timeout, so the PRplancheck sat pending indefinitely (visible on #30 and #31, both ran24h → cancelled). Fix pins supported images through[workspace.metadata.dist.github-custom-runners](ubuntu-22.04/macos-13/macos-14/windows-2022) and regeneratesrelease.yml.Test plan
cargo buildsucceeds.dist generate --checkclean (workflow matches config).dist planassigns only GitHub-hosted runners (no ubuntu-20.04 / windows-2019).src/cli/mod.rs.plancheck exercises the fix (head-branch workflow), so it should go green instead of hanging.After merge
Tag
v0.2.0onmainto trigger the cargo-dist release (builds binaries + installers, publishes the GitHub Release).🤖 Generated with Claude Code