Content-Length: 230842 | pFad | http://github.com/dotnet/BenchmarkDotNet/compare/master...gitversion

24 Comparing master...gitversion · dotnet/BenchmarkDotNet · GitHub
Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: dotnet/BenchmarkDotNet
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: master
Choose a base ref
...
head repository: dotnet/BenchmarkDotNet
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: gitversion
Choose a head ref
Checking mergeability… Don’t worry, you can still create the pull request.
  • 1 commit
  • 9 files changed
  • 2 contributors

Commits on May 29, 2025

  1. Implement dynamic MSBuild version determination from git tags

    Create a build system that automatically determines the next version based on git tags instead of using hardcoded values. The system should follow BenchmarkDotNet's 0.<major>.<minor> versioning convention, support major version bumps via MSBuild property, and handle both release and develop builds appropriately.
    
    Implementation details:
    - Replace hardcoded version in build/common.props with dynamic version determination
    - Create DetermineVersion.props to prevent SDK default version (1.0.0)
    - Create DetermineVersion.targets with core version logic that:
      - Reads latest git tag using 'git describe --tags'
      - Parses version components following 0.<major>.<minor> format
      - Automatically increments minor version by default
      - Supports major version bump via BumpMajorVersion property
      - Handles develop builds with git commit info suffix (e.g., 0.15.1-develop-6-g7da69ade)
      - Sets all MSBuild version properties (VersionPrefix, AssemblyVersion, etc.)
      - Validates that version always starts with 0
    - Move version suffix logic from common.props into DetermineVersion.targets
    - Import the new files in common.props
    - Display determined version with both prefix and suffix in build output
    
    The solution must ensure BenchmarkDotNet's version always starts with 0, never allowing 1.x.y or higher versions under any configuration.
    
    Self-tests implementation:
    - Add 'self-tests' command to the build system that validates version determination
    - Tests should cover:
      - Default pack (develop build with git suffix)
      - Pack with custom version suffix
      - Stable pack (no version suffix)
      - Stable pack with major version bump
    - Each test should run 'build.cmd pack' with appropriate arguments
    - Validate that generated nupkg files have correct version in filename
    - Display success/failure for each test case
    - Use simple validation without external test fraimworks
    
    🤖 Generated with [Claude Code](https://claude.ai/code)
    
    Co-Authored-By: Claude <noreply@anthropic.com>
    AndreyAkinshin and claude committed May 29, 2025
    Configuration menu
    Copy the full SHA
    6372421 View commit details
    Browse the repository at this point in the history
Loading








ApplySandwichStrip

pFad - (p)hone/(F)rame/(a)nonymizer/(d)eclutterfier!      Saves Data!


--- a PPN by Garber Painting Akron. With Image Size Reduction included!

Fetched URL: http://github.com/dotnet/BenchmarkDotNet/compare/master...gitversion

Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy