release: bump version to 0.1.2

- Fix GitHub Actions release workflow binary name
- Add automatic changelog integration
- Update all crate versions to 0.1.2

Author: d-oit

.github/workflows/release.yml

@@ -27,8 +27,50 @@ jobs:
         else
           echo "prerelease=false" >> $GITHUB_ENV
         fi
+    - name: Extract changelog entry
+      id: changelog
+      run: |
+        VERSION="${{ github.ref_name }}"
+        # Remove 'v' prefix if present
+        VERSION_NUM="${VERSION#v}"
+        
+        # Extract the section for this version from CHANGELOG.md
+        if [ -f "CHANGELOG.md" ]; then
+          # Get content between this version and the next version/end of file
+          CHANGELOG_ENTRY=$(awk -v version="$VERSION_NUM" '
+            /^## \[/ {
+              if (found) exit
+              if ($0 ~ "\\[" version "\\]") found=1
+              next
+            }
+            found && !/^$/ { content = content $0 "\n" }
+            END { print content }
+          ' CHANGELOG.md)
+          
+          # Save to file and environment
+          if [ -n "$CHANGELOG_ENTRY" ]; then
+            echo "$CHANGELOG_ENTRY" > release_notes.md
+            echo "HAS_CHANGELOG=true" >> $GITHUB_ENV
+          else
+            echo "HAS_CHANGELOG=false" >> $GITHUB_ENV
+          fi
+        else
+          echo "HAS_CHANGELOG=false" >> $GITHUB_ENV
+        fi
+
     - name: Create Release
-      run: gh release create ${{ github.ref_name }} --title "Release ${{ github.ref_name }}" --generate-notes ${{ env.prerelease == 'true' && '--prerelease' || '' }}
+      run: |
+        if [ "${{ env.HAS_CHANGELOG }}" = "true" ] && [ -s release_notes.md ]; then
+          gh release create ${{ github.ref_name }} \
+            --title "Release ${{ github.ref_name }}" \
+            --notes-file release_notes.md \
+            ${{ env.prerelease == 'true' && '--prerelease' || '' }}
+        else
+          gh release create ${{ github.ref_name }} \
+            --title "Release ${{ github.ref_name }}" \
+            --generate-notes \
+            ${{ env.prerelease == 'true' && '--prerelease' || '' }}
+        fi
       env:
         GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
 
@@ -77,7 +119,7 @@ jobs:
     - name: Create archive
       shell: bash
       run: |
-        binary_name="code-guardian-cli${{ matrix.suffix }}"
+        binary_name="code_guardian_cli${{ matrix.suffix }}"
         if [ "${{ matrix.os }}" = "windows-latest" ]; then
           archive_name="code-guardian-${{ matrix.target }}.zip"
           cp "target/${{ matrix.target }}/release/${binary_name}" .

.opencode/agent/testing-agent.md

@@ -4,7 +4,7 @@ description: >-
 
   <example>
     Context: The user needs to improve test coverage.
-    user: "How can I achieve 80% test coverage for the core module?"
+    user: "How can I achieve82% test coverage for the core module?"
     assistant: "I'm going to use the Task tool to launch the testing-agent to write and optimize tests."
     <commentary>
     Since the user is requesting testing help, use the testing-agent.
@@ -17,7 +17,7 @@ mode: subagent
 The Testing Agent is a specialized AI agent for testing in code-guardian, ensuring code quality through unit/integration tests and coverage.
 
 ## Purpose
-To write tests, achieve 80%+ coverage, set up infrastructure, and fix bugs.
+To write tests, achieve82%+ coverage, set up infrastructure, and fix bugs.
 
 ## Inputs/Outputs
 - **Inputs**: Code to test, coverage goals.
@@ -30,7 +30,7 @@ To write tests, achieve 80%+ coverage, set up infrastructure, and fix bugs.
 
 ## Usage Examples
 ### Example 1: Improving Coverage
-- Input: "Achieve 80% coverage for core module."
+- Input: "Achieve82% coverage for core module."
 - Process: Write tests, run tarpaulin.
 - Output: Test suite with coverage report.
 

.opencode/command/cargo-test.md

@@ -2,5 +2,5 @@
 description: Run tests with coverage
 agent: testing-agent
 ---
-Execute `cargo test` and analyze results. Focus on failures, suggest improvements, and aim for 80%+ coverage.
+Execute `cargo test` and analyze results. Focus on failures, suggest improvements, and aim for82%+ coverage.
 Test output: !`cargo test`

AGENTS.md

@@ -14,7 +14,7 @@
 - **Types**: Use strong typing; prefer `&str` over `String` for parameters; use `Result<T, E>` for fallible operations
 - **Error Handling**: Use `thiserror` for custom errors, `anyhow` for generic errors; prefer `?` operator
 - **Documentation**: Document public APIs with `///` comments; use `cargo doc` to generate docs
-- **Testing**: Write unit tests with `#[test]`; use `#[cfg(test)]` modules; aim for 80%+ coverage
+- **Testing**: Write unit tests with `#[test]`; use `#[cfg(test)]` modules; aim for82%+ coverage
 - **Concurrency**: Use `rayon` for parallelism; prefer channels over shared state
 - **Serialization**: Use `serde` with derive macros; prefer JSON/YAML over binary formats
 
@@ -58,7 +58,7 @@
 - Review code across agents for integration
 
 ## Quality Control
-- 80%+ test coverage
+-82%+ test coverage
 - Pass CI/CD before merge
 - Adhere to modular architecture
 

CHANGELOG.md

@@ -5,6 +5,23 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.1.2] - 2025-01-09
+
+### Fixed
+- GitHub Actions release workflow binary name mismatch (code-guardian-cli vs code_guardian_cli)
+- Duplicate anyhow import in monitoring module
+- Syntax error in CLI main.rs tracing initialization
+
+### Added
+- Automatic changelog integration in release workflow
+- Enhanced release descriptions from CHANGELOG.md
+- Comprehensive workflow issue analysis and documentation
+
+### Changed
+- Release workflow now extracts and uses proper changelog content
+- Improved error handling in release process
+- Updated existing v0.1.1 release with proper description
+
 ## [0.1.1] - 2025-10-09
 
 ### Added

CONTRIBUTING.md

@@ -44,7 +44,7 @@ This project follows a code of conduct to ensure a welcoming environment for all
 ### Testing
 - Write unit tests for all new code using `#[test]`
 - Use `#[cfg(test)]` modules for test-specific code
-- Aim for 80%+ test coverage
+- Aim for82%+ test coverage
 - Run tests with `cargo test`
 
 ### Performance

README.md

@@ -274,7 +274,7 @@ See [CONTRIBUTING.md](CONTRIBUTING.md) for detailed contribution guidelines.
 Quick checklist:
 1. Follow the guidelines in `AGENTS.md`
 2. Keep modules under 500 lines of code
-3. Maintain 80%+ test coverage
+3. Maintain82%+ test coverage
 4. Use conventional commit messages
 
 ## License

crates/cli/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "code_guardian_cli"
-version = "0.1.1"
+version = "0.1.2"
 edition = "2021"
 
 [dependencies]

crates/cli/src/main.rs

@@ -381,7 +381,7 @@ enum GitAction {
 #[tokio::main]
 async fn main() -> Result<()> {
     // Initialize tracing
-    tracing_subscriber::fmt::init();
+    tracing_subscriber::fmt()
         .with_env_filter(tracing_subscriber::EnvFilter::from_default_env())
         .init();
 

crates/core/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "code-guardian-core"
-version = "0.1.1"
+version = "0.1.2"
 edition = "2021"
 
 [dependencies]