Add rb version - #7
Merged
Merged
Conversation
An upgraded rb.exe was otherwise only distinguishable by its file timestamp. The line follows cargo's shape, rbmanager 0.1.0 (9a1b2c3 2026-07-28), with the version coming from the release tag and the commit and date stamped in at build time, so two builds of the same tag stay tellable apart. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The publish case is the one that carries weight. The version is read from assembly attributes, and NativeAOT is where that lookup could come back empty while the CoreCLR build stays fine. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
1 participant
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.
Upgrading rb.exe left no way to tell which build is installed short of reading the file timestamp.
rb versionreports it, in cargo's shape.The version alone does not separate two builds of the same tag, so the commit and date come along. The version is read from the assembly rather than kept as a literal, because
release.ymlstamps it from the tag with-p:Version=<tag>. The commit and date are stamped by an MSBuild target inrbmanager.csproj, riding along asSourceRevisionIdand anAssemblyMetadataentry. A build with no git checkout drops the parenthetical and prints the version alone. The publish suite pins all of this against the NativeAOT binary, which is the one place the attribute lookup could come back empty.Only
rb versionis added, no--versionor-valiases.