{"id":"6a2abbff8056c09c133007c7","title":"2026 06 11 Issue 185","path":"how-to/committee/release-notes/2026-06-11-issue-185","contentMarkdown":"# 11-Jun-2026 — bump actions/cache to v5 to clear Node 20 deprecation warning [ref #185](https://github.com/nbarrett/ngx-ramblers/issues/185)\n\n## [build 687](https://github.com/nbarrett/ngx-ramblers/actions/runs/27350313589) — [commit 71221d7](https://github.com/nbarrett/ngx-ramblers/commit/71221d768dc50487e38701b98877580f39ecf290)\n\n_____\n\n- #185 moved checkout and setup-node to v6 in March, but the node_modules\ncaching steps added later by the #201 perf work used actions/cache@v4,\nwhich still targets Node 20 and reintroduced the deprecation warning\n- bump all 12 actions/cache references across the docker-image and\nintegration-worker workflows to v5 (Node 24 runtime); inputs are\nunchanged so existing cache keys keep working","contentHtml":"<h1>11-Jun-2026 — bump actions/cache to v5 to clear Node 20 deprecation warning <a href=\"https://github.com/nbarrett/ngx-ramblers/issues/185\">ref #185</a></h1>\n<h2><a href=\"https://github.com/nbarrett/ngx-ramblers/actions/runs/27350313589\">build 687</a> — <a href=\"https://github.com/nbarrett/ngx-ramblers/commit/71221d768dc50487e38701b98877580f39ecf290\">commit 71221d7</a></h2>\n<hr>\n<ul>\n<li>#185 moved checkout and setup-node to v6 in March, but the node_modules</li>\n</ul>\n<p>caching steps added later by the #201 perf work used actions/cache@v4,\nwhich still targets Node 20 and reintroduced the deprecation warning</p>\n<ul>\n<li>bump all 12 actions/cache references across the docker-image and\nintegration-worker workflows to v5 (Node 24 runtime); inputs are\nunchanged so existing cache keys keep working</li>\n</ul>\n"}