Skip to content

Release 0.1.15: the report shows a relative solution path - #11

Merged
Karzone merged 1 commit into
mainfrom
claude/beautiful-archimedes-dbzisv
Oct 11, 2026
Merged

Karzone merged 1 commit into
mainfrom
claude/beautiful-archimedes-dbzisv

Conversation

@Karzone

@Karzone Karzone commented Oct 11, 2026

Copy link
Copy Markdown
Owner

Summary

Bumps <Version> in src/Directory.Build.props from 0.1.14 to 0.1.15, to ship #10: testatlas report shows the solution path relative to the directory it runs from, instead of the machine-specific absolute path.

Once this is on main, publishing the GitHub Release v0.1.15 runs publish.yml, which pushes TestAtlas.Cli and TestAtlas.Mcp 0.1.15 to NuGet and the MCP Registry. Glama auto-builds from the release.

Related issue

None.

Type of change

  • Bug fix
  • New feature / analyzer
  • Documentation
  • Build / CI / tooling
  • Other

Checklist

  • dotnet build passes (Release)
  • dotnet test passes (265/265)
  • Added or updated tests for the change (version bump only)
  • Updated docs / README if behavior or usage changed (docs/DISTRIBUTION.md gets updated once 0.1.15 is live)
  • Change keeps TestAtlas zero-config, offline, and deterministic

Notes for reviewers

🤖 Generated with Claude Code

https://claude.ai/code/session_013F6VMUcDtZmJX3ZibLuzXg


Generated by Claude Code

testatlas report printed the solution's absolute path in its header, so
a committed report carried the machine it was built on. A solution under
the working directory now shows relative to it; one outside it keeps the
recorded path.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013F6VMUcDtZmJX3ZibLuzXg
@Karzone
Karzone merged commit f853458 into main Oct 11, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants