chore: cascade nuget sweep (tier 4) + release retry guard - #66
Merged
Conversation
Tharga.Console 4.2.2, Tharga.Blazor 2.3.2, Tharga.Mcp 2.0.0, Tharga.MongoDB 2.15.0. Mcp 2.0.0 removes IMcpContext.IsDeveloper; nothing here read it - the providers only take IMcpContext as a parameter - so no code changed. Also retries the GitHub release step so a transient API failure cannot leave a package published on nuget.org with no matching tag.
|
Released as v1.1.0 — https://github.com/Tharga/Cache/releases/tag/1.1.0 |
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.
Final tier of the cascade sweep. Internal bumps to the versions published earlier in this sweep: Console 4.2.2, Blazor 2.3.2, Mcp 2.0.0, MongoDB 2.15.0.
Mcp 2.0.0 drops
IMcpContext.IsDeveloper; Cache only ever takesIMcpContextas a parameter, so no code changed.Also adds the release retry guard — the package reaches nuget.org before
gh release createruns, so a transient API failure strands a published version with no tag and the next build silently republishes it.Tests: 467 pass, 0 fail (Integration and TimeCritical excluded, same filters as CI).
Publishes as 1.1.0, carrying the AddCache race and FluentAssertions fixes already on this line.