Skip to content

[css-2026] Autopublish? #13593

@svgeesus

Description

@svgeesus

As noted in these minutes 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 is editable by anyone in the CS WG there also needs to be an Echidna token 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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Administrative TrackerFor external review / publication tracking issues.css-2026The new, improved CSS snapshot

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions