Skip to content

Phase 2: Version Detection & Release Notes Generation #628

Closed as not planned
Closed as not planned

Description

@ashleyshaw

Overview

Implement intelligent version detection from changelog and enhanced release notes generation. This phase automates semantic versioning decisions and creates comprehensive release documentation.

Deliverables

Modules to Create

  1. versionDetector.js - Auto-detect semantic version bumps (major/minor/patch)
  2. releaseNotesFormatter.js - Generate formatted release notes with highlights
  3. duplicateDetector.js - Identify and flag similar/duplicate entries
  4. validate-changelog-completeness.js - Pre-release validation
  5. version-bump-cli.js - CLI for version detection
  6. release-notes-cli.js - CLI for release notes generation

Features

  • Analyze [Unreleased] section for breaking/feature/fix patterns
  • Auto-detect version bumps (breaking=major, feat=minor, fix=patch)
  • Generate release highlights (top 5 changes)
  • Flag breaking changes with warnings
  • Attribute contributions to PR authors
  • Detect duplicate/similar entries
  • Support multiple output formats (markdown, JSON)
  • Pre-release completeness validation

Integration

  • Update release.agent.js to use auto-detected versions
  • Replace formatReleaseNotes() with enhanced implementation
  • Add validation checkpoints before release

Testing

  • Unit tests for each module (>85% coverage)
  • Edge cases: no highlights, no contributors, no breaking changes
  • Integration with release workflow

Success Criteria

  • Version bumping fully automated
  • Release notes include all required sections
  • Completeness validation blocks incomplete releases
  • Duplicate detection operational
  • All CLIs functional
  • Test coverage >85%

Related Issues

Depends On

Activity

  1. linear-code commented on May 31, 2026

    @linear-code
  2. added this to the milestone on Jun 1, 2026
  3. ashleyshaw commented on Jun 1, 2026

    @ashleyshaw
    MemberAuthor

    Release-scope evaluation completed for v0.5.0 readiness.

    Rationale for closing as not planned in this milestone:

    • Advanced version detection/release notes generation enhancements are not required to safely tag v0.5.0.
    • Current release flow now has sufficient gating and validation coverage.

    Recommendation: track under a future release-automation enhancement milestone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Fields

    Priority

    None yet

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions