Skip to content

Workflow failures #159

Closed
Closed

Description

@michaelwasserman

@anssiko it seems like the workflow might be failing from the window-placement to window-management shortname migration? https://github.com/w3c/window-management/actions/runs/28897343506

AI suggests:

Request W3C Manual Transition (Recommended Long-Term Fix)
To officially transition to the new shortname, you must ask the W3C Webmaster to manually publish the First Public Working Draft (FPWD) (or a manual transition draft) using the new window-management shortname.

Once the W3C Webmaster successfully publishes the draft manually, https://www.w3.org/TR/window-management/ will exist on the W3C servers.
After that, all subsequent pushes to main will automatically succeed via the automated auto-publish.yml workflow.

Separately, we should

Clean Up Action Deprecations
While not the cause of the publish failure, your GitHub Actions runner also emitted warnings about Node.js deprecations. To future-proof your workflow, update the action versions in .github/workflows/auto-publish.yml:

Upgrade actions/checkout@v2 to actions/checkout@v4
Upgrade actions/setup-python@v2/v4 to actions/setup-python@v5

Activity

  1. tidoust commented on Jul 9, 2026

    @tidoust
    Member

    AI suggests:

    Interesting analysis ;)

    But the reason why publication fails is that Joshua Bell is listed as editor but is not (or no longer?) a participant in the Second Screen Working Group. Spec editors must be in the group per the W3C Process. The publication rules (a.k.a. "pubrules") checker did not enforce that until some time ago, it now does. It is possible that the Window Management spec got last published before the checker started to enforce the rule.

    The solution is either to move Joshua to a "Former editor" list or for him to join the Working Group if that's a possibility. That should be enough to resume publication. The document is already published as window-management in particular.

  2. michaelwasserman commented on Jul 14, 2026

    @michaelwasserman
    MemberAuthor

    Thanks for correcting my misinformation, @tidoust, and apologies for using more tokens than brain cells.

    #160 fixed that participation issue in CI run 173: https://github.com/w3c/window-management/actions/workflows/auto-publish.yml

    #161 and #162 update to https://github.com/actions/checkout#checkout-v6 but Node20 warnings might persist until https://github.com/w3c/spec-prod is updated.

    Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-python@v5, pnpm/action-setup@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
    
  3. changed the title [-]Workflow failures from short name migration[/-] [+]Workflow failures[/+] on Jul 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions