- From: Chris Lilley via GitHub <noreply@w3.org>
- Date: Tue, 03 Mar 2026 23:16:03 +0000
- To: public-css-archive@w3.org
svgeesus has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-2026] Autopublish? == As noted [in these minutes](https://www.w3.org/2025/08/21-css-minutes.html#fc30) CSSWG agreed to autopublish certain specifications that the editors agreed were suitable. (There is an opt-out if pushing a complex series of edits and you need to pause a given spec for a while). I have been testing this out and it works well for an initial set of specs: - CSS Color 4 - CSS Color 5 - CSS Color HDR - CSS Fonts 4 - CSS Fonts 5 The minuted resolution covers NOTE, WD, and CRD (ie not things that require manual publication). So, how about adding CSS 2026 to the list so that it is always up to date? @tabatkins @fantasai @frivoal @SebastianZ I am writing documentation in our wiki about how to add a new spec to the autopublish list; for now although the [control file](https://github.com/w3c/csswg-drafts/blob/main/.github/generate-auto-publish-workflows.py) is editable by anyone in the CS WG there also needs to be an [Echidna token](https://github.com/w3c/echidna/wiki/Token-creation) stored as a GitHub secret, which requires GitHub admin to add ie Staff Contact or Chair. So if we agree, I will set it up. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13593 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 3 March 2026 23:16:04 UTC