Integrate VersionMark for tool version tracking in Build Notes PDF#72
Merged
Malcolmnixon merged 7 commits intomainfrom Feb 15, 2026
Merged
Integrate VersionMark for tool version tracking in Build Notes PDF#72Malcolmnixon merged 7 commits intomainfrom
Malcolmnixon merged 7 commits intomainfrom
Conversation
- Add .versionmark.yaml configuration file defining all tools to capture - Add DemaConsulting.VersionMark v0.1.0 to .config/dotnet-tools.json - Add version capture steps to all workflow jobs: - quality-checks: captures dotnet, git, versionmark - build: captures dotnet, git, dotnet-sonarscanner, versionmark - integration-test: captures dotnet, git, versionmark - build-docs: captures all tools used in documentation generation - Add version publishing step in build-docs job to generate versions.md - Add docs/buildnotes/versions.md to buildnotes definition.yaml - Update .gitignore to exclude versionmark-*.json capture files - Add 'versionmark' to .cspell.json dictionary This enables tracking and publishing of tool versions used in each CI/CD job to the Build Notes PDF documentation, providing complete build environment transparency.
- Remove line continuation in build job versionmark capture (line 148) - Split build-docs versionmark capture into multiple lines to meet 120 char limit - Split versionmark publish command into multiple lines for better readability - Maintain consistent formatting across all versionmark commands in the workflow
- Change 'run: >' to simple 'run:' for single-line dotnet tool restore commands - Improves consistency with other single-command steps in the workflow - Addresses code review feedback on YAML style inconsistencies
- Document that .NET SDK versions include up to 4 components - Explain why versionmark captures its own version (complete tool transparency) - Addresses code review feedback on regex patterns and self-capture rationale
Copilot
AI
changed the title
[WIP] Update repo consistency agent for VersionMark captures
Integrate VersionMark for tool version tracking in Build Notes PDF
Feb 15, 2026
Malcolmnixon
approved these changes
Feb 15, 2026
Malcolmnixon
requested changes
Feb 15, 2026
Co-authored-by: Malcolmnixon <1863707+Malcolmnixon@users.noreply.github.com>
Co-authored-by: Malcolmnixon <1863707+Malcolmnixon@users.noreply.github.com>
Malcolmnixon
approved these changes
Feb 15, 2026
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
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.
Pull Request
Description
Integrates VersionMark tool for comprehensive version tracking of all build tools across CI/CD pipeline. Tool versions are now captured during workflow execution and published to
docs/buildnotes/versions.md, which is automatically included in the Build Notes PDF.Key Changes:
.versionmark.yaml): Defines capture patterns for .NET SDK, Git, Node.js, npm, and all DemaConsulting dotnet tools. BuildMark usesdotnet tool list --globalsince it's installed globally in the build-docs job where it's used as a documentation generation tool..github/workflows/build.yaml): Added version capture steps toquality-checks,build, andintegration-testjobs;build-docsjob now consolidates captures and publishes unified version report. Integration-test captures only the tools used (dotnet, git, versionmark), not BuildMark itself as it's the product being tested.docs/buildnotes/definition.yaml): Addedversions.mdas input to include tool versions in PDF.config/dotnet-tools.json): Added DemaConsulting.VersionMark v0.1.0Version captures use job-specific identifiers (e.g.,
build-win,build-ubuntu,int-win-8) to distinguish multi-platform build environments and test matrices.Type of Change
Related Issues
Pre-Submission Checklist
Before submitting this pull request, ensure you have completed the following:
Build and Test
dotnet build --configuration Releasedotnet test --configuration ReleaseCode Quality
dotnet format --verify-no-changesQuality Checks
Please run the following checks before submitting:
cspell "**/*.{md,cs}"markdownlint "**/*.md"yamllint '**/*.{yml,yaml}'Testing
Documentation
Additional Notes
Changes align BuildMark with latest TemplateDotNetTool template patterns. CodeQL security scan passed with zero alerts. Generated version files (
versionmark-*.json,docs/buildnotes/versions.md) are excluded via.gitignore.BuildMark version capture configuration correctly uses
--globalflag since BuildMark is installed globally (not as a local tool) when used in the build-docs job for generating documentation. Integration tests capture only the tools used in testing (dotnet, git, versionmark), not BuildMark itself as it's the product being validated, not a build tool.✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.