docs: align versioning for v0.1.0 initial public release#4
Closed
hidetzu wants to merge 8 commits into
Closed
Conversation
Set up spec-driven development foundation: - specs/ (usecases, requirements, technical spec, roadmap) - GitHub issue/PR templates and CI workflow - CLAUDE.md with steering workflow rules - README.md with project overview Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
- Project scaffold with cobra CLI and Makefile - Git diff parsing (git diff --numstat) - Signal detection: large_change, high_insertions, high_deletions - Scorer with additive weights and 0-100 clipping - JSON and text formatters - Unit tests for all internal packages (16 tests) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Implement Step1: minimal working version
…r-file risk (#2) - Git log integration for hotspot detection (90 days, 5+ changes) - S-4: hotspot signal (file-scoped) - S-5: no_test_change signal (aggregate, multi-language test patterns) - S-6: core_module signal (config, payment, database, etc.) - S-7: security_module signal (auth, crypto, token, etc.) - Analyzer dedup: security_module takes priority over core_module - Per-file risk scoring (file-scoped signal weights / 40.0) - JSON/text output includes files[] with per-file risk and signals - Exit code: 0 (low), 1 (medium+), 2 (error) - Update spec.md to match actual git.Log signature - 50 unit tests across all packages Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…ternal tool input (#3) - Add .riskcheck.yaml config file support with YAML loading - Constructor injection for all signal config overrides (thresholds, weights, paths, test patterns) - riskcheck init command to generate config file - S-8: high_complexity signal via --complexity-file (external JSON) - S-9: low_coverage signal via --coverage-file (external JSON) - CLI flags: --config, --complexity-file, --coverage-file - Print errors to stderr before exit - Update specs, README with full feature documentation - 70+ unit tests across all packages Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
- specs/roadmap.md: bundle Step1-3 into v0.1.0; add Ideas Under Consideration section (Lua-based custom rules) - CLAUDE.md: update Current Focus to v0.1.0 release prep - README.md: align Roadmap section with the new versioning
hidetzu
force-pushed
the
docs/v0.1.0-release-prep
branch
from
5761670 to
3776b41
Compare
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Step1-3 were all implemented inside the private repository. Since the public release will start at
v0.1.0bundling Step1+2+3, this PR aligns the related documentation with that policy.Related Issue
N/A
Related Spec
specs/roadmap.mdRoadmap Step
Not applicable (documentation cleanup for v0.1.0 release preparation).
Changes
specs/roadmap.md: Restructure Release Strategy tov0.1.0 = Step1+2+3/v0.2.0+ = Step4 (TBD)/v1.0.0.specs/roadmap.md: Add an "Ideas Under Consideration" section and record the Lua-based custom rules idea as an undecided proposal.README.md: Update the Roadmap section to match the new versioning.Test Plan
v0.1.0 = Step1+2+3