Skip to content

Conversation

@jjonescz
Copy link
Member

@jjonescz jjonescz commented Jul 8, 2025

Follow up on #1287.

Without this PR, the spectre-console submodule is based on main (which is a prerelease) and the version number was outdated (wasn't removed with the rest of the submodule so I missed updating it when reverting the removal).

In this PR, I've checked out version 0.50.0 in the submodule and used the corresponding version number when building the package.

@jjonescz jjonescz marked this pull request as ready for review July 8, 2025 17:12
@jjonescz jjonescz requested a review from a team as a code owner July 8, 2025 17:12
<BuildCommandArgs>$(BuildCommandArgs) /v:$(LogVerbosity)</BuildCommandArgs>
<BuildCommandArgs>$(BuildCommandArgs) $(RedirectRepoOutputToLog)</BuildCommandArgs>
<BuildCommandArgs>$(BuildCommandArgs) /p:Version=$(SpectreConsoleReleaseVersion)</BuildCommandArgs>
<BuildCommandArgs>$(BuildCommandArgs) /p:Version=0.50.0</BuildCommandArgs>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm fine with moving the version out of Versions.props. But can you preserve the original SpectreConsoleReleaseVersion and define it up towards the top of this file so that it can be easily found?

@mthalman mthalman enabled auto-merge (squash) July 8, 2025 18:21
@mthalman mthalman merged commit 0f9a32f into dotnet:main Jul 8, 2025
4 checks passed
@jjonescz jjonescz deleted the spectre-release branch July 8, 2025 18:24
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