chore(deps): consume Tharga.MongoDB 2.15.1 - #67
Merged
Conversation
|
Released as v1.1.1 — https://github.com/Tharga/Cache/releases/tag/1.1.1 |
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.
Tharga.Cache.MongoDB pinned Tharga.MongoDB 2.15.0 while 2.15.1 is published — the only stale Tharga.* reference in this repo (Console 4.2.2, Blazor 2.3.2 and Mcp 2.0.0 are all current). Flagged by the Package Status report.
What 2.15.1 carries, relative to 2.15.0:
The configuration-binding fix is the one worth having here, since Tharga.Cache.MongoDB configures its store through that same section.
Verified locally against the CI trait exclusions (Integration and TimeCritical), both before and after the bump: 459 tests in Tharga.Cache.Tests plus the File, MongoDB and Redis suites, identical results either side — build clean, zero failures. The baseline was taken deliberately because backlog items 9 and 13 record this suite as timing-flaky, so an unqualified 'tests pass' would not have shown the bump was innocent.