caching/v1.0.1
·
26 commits
to main
since this release
🐛 Bug Fix Release
This patch release fixes an important bug where cache presets were not respecting their configured expiry times.
What's Fixed
Cache Preset Expiry Times
AddMediumTermCache<T>()
now correctly uses 10 minutes (was incorrectly using 5 minutes)AddShortTermCache<T>()
now correctly uses 1 minute as documentedAddLongTermCache<T>()
now correctly uses 1 hour as documented- All other cache presets (
AddHighPerformanceCache
,AddConfigurationCache
, etc.) now use their documented expiry times
Root Cause
The GetExpiry
function had a hardcoded 5-minute fallback that was overriding the preset configurations. This has been fixed to properly reference the configured DefaultExpiry
value.
Important Notes
- ✅ Non-breaking change – this fix corrects behavior to match documentation
- ✅ Cache-Control headers still take precedence over preset values
- ✅ All existing functionality continues to work as expected
Full Changelog: caching/v1.0.0...caching/v1.0.1