Skip to content

Roadmap health #209

Open
Open

Description

@github-actions

This issue is rewritten every night by the roadmap sweep. It is the weekly call's triage agenda. Fix what it lists in GitHub, and the next sweep clears the line.

Written 2026-10-21T04:27:17Z, run 39544109882, rules 2026-10-04.2.

Ready to publish

Every issue is done and its work is on main. A project lead closes the milestone.

None.

Closed with open work

Closed milestones that still hold remaining issues.

None.

Closed with open work and nothing done

Closed milestones with no done issues but remaining ones. They show as withdrawn. Reopen any closed by mistake.

None.

Target passed

Open milestones past their committed date or quarter.

None.

Untriaged in a milestone

Open issues in a milestone with no acceptance decision.

None.

Milestoned against a triage decision

The event job declined these because of a standing triage label.

Unverified closes

Closed as completed, but the data does not show delivery. Each line gives its milestone, its reason code, and the one remedy for that code.

In focus without a milestone

Open in-focus issues not yet placed on the roadmap.

Accepted without a milestone

Open accepted issues not yet placed on the roadmap.

None.

Accepted by milestone this week

Issues the bot accepted in the last eight days, with who set the milestone.

None.

Unknown close reasons

Closed with a reason this version does not know.

None.

Off-quarter dates

Milestones whose due date is not the last day of a quarter.

None.

Missing description lines

Open milestones without a valid Type line, which the OWASP report needs.

None.

Promotion

Work on integration that main lacks. A project lead opens and merges the promotion.

Promotion pending since 2026-10-18.
No promotion pull request is open. A project lead opens one:

gh pr create --repo GenAI-Security-Project/agent-control-standard --base main --head integration --title 'Promote integration to main' --body '1 commit(s) ahead. Merging publishes the site and every schema $id URI. Merge with a merge commit, not a squash: squashing flattens the specification history that makes a schema change reviewable later.'

Bypasses

Merges into integration or main in the last seven days with no approving review, and direct pushes. Admins can bypass the rulesets, so this is where a bypass shows.

Merged without an approving review in the last seven days: 5.

Switches

The current value of each roadmap variable, flagged when it is neither true nor false.

  • ROADMAP_REFRESH_ENABLED is true
  • ROADMAP_RENDER_ENABLED is true
  • ROADMAP_SYNC_ENABLED is true

Activity

  1. locked as resolved and limited conversation to collaborators on Oct 5, 2026
  2. pinned this issue on Oct 5, 2026
  3. github-actions commented on Oct 5, 2026

    @github-actions
    Author

    @rocklambros @afogel @bar-capsule The roadmap monitor started failing. Failing checks: an alarm test. The monitor's run log names each problem.

  4. unlocked this conversation on Oct 5, 2026
  5. locked as resolved and limited conversation to collaborators on Oct 5, 2026
  6. unlocked this conversation on Oct 5, 2026
  7. github-actions commented on Oct 5, 2026

    @github-actions
    Author

    The roadmap monitor passes again.

  8. locked as resolved and limited conversation to collaborators on Oct 5, 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

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions