Change history — oslo.cache — branch stable/2026.2
Branch
stable/2026.2@fc96999a99e4— range99a749393da4..fc96999a99e4(automatic: since the branch leftmaster), 3 non-merge commits — target: none — analysed on 2026-10-28
Raw facts: _inventory/history_stable-2026.2.md and _inventory/history_stable-2026.2.json.
| # | Commit | Date | Category | Change | Impact |
|---|---|---|---|---|---|
| 1 | b5a1d8a06471 | 2026-08-24 | fix (typing only) | return type annotation of __new__ corrected in both pools | none at run time |
| 2 | 893ee6d425d1 | 2026-09-03 | maintenance | .gitreview points to stable/2026.2 | none |
| 3 | fc96999a99e4 | 2026-09-03 | maintenance | tox uses the stable/2026.2 upper-constraints | none |
1. Fix mypy errors (b5a1d8a06471, cherry-pick of a14d55b2212f)
- Before:
__new__of_MemcacheClientand_BMemcacheClientwas annotated as returningtype[...], which mypy reports as wrong. - After: it is annotated as returning an instance (
oslo_cache/_memcache_pool.py:66-67,oslo_cache/_bmemcache_pool.py:56-57). - Behaviour: unchanged. The method only exists when eventlet has monkey-patched
thread, and it still returnsobject.__new__(cls). - Review: https://review.opendev.org/q/I5809e3e0523c53bd916d6f1eeb93b62110af0460
Carry-over plan
Nothing to carry over for behaviour. Commit 1 is only needed by a fork that runs mypy on these files.
Source: reverse-spec-oslo.cache/06-change-history_stable-2026.2.md. The _rewrite/ and _inventory/ files are not published on the site.