{"id":"69d8ab1671c3da0f30b9cf9f","title":"2026 04 10 Build 581","path":"how-to/committee/release-notes/2026-04-10-build-581","contentMarkdown":"# 10-Apr-2026 — Release-notes: exclude hex colours and prevent cross-release pollution [#223](https://github.com/nbarrett/ngx-ramblers/issues/223)\n\n## [build 581](https://github.com/nbarrett/ngx-ramblers/actions/runs/24232040496) — [commit d55ff4a](https://github.com/nbarrett/ngx-ramblers/commit/d55ff4a7d829914c74bf5caca2eb8a7d9e643a31)\n\n_____\n\n- Limit standalone issue references to 1-5 digits so 6-digit hex colours\nlike #222222 and #404141 are not parsed as GitHub issue numbers.\n- In --latest mode (used by the deploy pipeline), filter commits to only\nthose from the most recent commit's date so older commits without a tag\nboundary cannot leak into a new release group via the issue fallback\ncascade. This was causing 2026-04-10 release notes to incorrectly absorb\ncontent from the 2026-04-06 #223 release.\n\n","contentHtml":"10-Apr-2026 — Release-notes: exclude hex colours and prevent cross-release pollution #223
\n\n
\n\n- Limit standalone issue references to 1-5 digits so 6-digit hex colours\nlike #222222 and #404141 are not parsed as GitHub issue numbers.
\n- In --latest mode (used by the deploy pipeline), filter commits to only\nthose from the most recent commit's date so older commits without a tag\nboundary cannot leak into a new release group via the issue fallback\ncascade. This was causing 2026-04-10 release notes to incorrectly absorb\ncontent from the 2026-04-06 #223 release.
\n
\n"}