The requirement

OPS-R86 — The train MUST tag the repository of each first-party plugin that builds an image at the core's version before it tags the core's release, MUST NOT tag one that builds none, and MUST NOT tag any at a pre-release's tag. Once the plugin's manifest names what that tag published, the train MUST move the plugin's pin and copy in the catalogue's bundle with one rolling pull request. The bundle MAY pin a first-party plugin that builds no image by revision and tree digest alone, with no release. The core's release tag MUST embed the bundle at a catalogue commit whose bundle pins every first-party plugin that builds an image at that version, and none of them by revision alone. A pre-release MAY embed a bundle that pins a first-party plugin that builds an image by revision alone, and MUST NOT record the bundle pin, or anything else, as an unmet goal: a pre-release with an unmet goal is refused (OPS-R66).

Where it is built

  • lemonfiber0 of 3 open pull requests

    How to claim it

    With lfdev, from a clone of the repository:

    lfdev claim OPS-R86

    Or in GitHub's editor, adding this row to the tracker:

    [[requirement]]
    id = "OPS-R86"
    state = "open"
    

    Edit status/OPS.toml on GitHub

    Open the pull request as a draft, titled:

    chore(claim): OPS-R86

    Its body ends with these lines, the sign-off in your own name:

    Claiming OPS-R86.
    
    Spec: OPS-R86
    
    Signed-off-by: Your Name <[email protected]>
  • lemonfiber-decline0 of 3 open pull requests

    How to claim it

    With lfdev, from a clone of the repository:

    lfdev claim OPS-R86

    Or in GitHub's editor, adding this row to the tracker:

    [[requirement]]
    id = "OPS-R86"
    state = "open"
    

    Edit status.toml on GitHub

    Open the pull request as a draft, titled:

    chore(claim): OPS-R86

    Its body ends with these lines, the sign-off in your own name:

    Claiming OPS-R86.
    
    Spec: OPS-R86
    
    Signed-off-by: Your Name <[email protected]>
  • lemonfiber-media-stack0 of 3 open pull requests

    How to claim it

    With lfdev, from a clone of the repository:

    lfdev claim OPS-R86

    Or in GitHub's editor, adding this row to the tracker:

    [[requirement]]
    id = "OPS-R86"
    state = "open"
    

    Edit status.toml on GitHub

    Open the pull request as a draft, titled:

    chore(claim): OPS-R86

    Its body ends with these lines, the sign-off in your own name:

    Claiming OPS-R86.
    
    Spec: OPS-R86
    
    Signed-off-by: Your Name <[email protected]>
  • lemonfiber-plugins0 of 3 open pull requests

    How to claim it

    With lfdev, from a clone of the repository:

    lfdev claim OPS-R86

    Or in GitHub's editor, adding this row to the tracker:

    [[requirement]]
    id = "OPS-R86"
    state = "open"
    

    Edit status.toml on GitHub

    Open the pull request as a draft, titled:

    chore(claim): OPS-R86

    Its body ends with these lines, the sign-off in your own name:

    Claiming OPS-R86.
    
    Spec: OPS-R86
    
    Signed-off-by: Your Name <[email protected]>
  • lemonfiber-web0 of 3 open pull requests

    How to claim it

    With lfdev, from a clone of the repository:

    lfdev claim OPS-R86

    Or in GitHub's editor, adding this row to the tracker:

    [[requirement]]
    id = "OPS-R86"
    state = "open"
    

    Edit status.toml on GitHub

    Open the pull request as a draft, titled:

    chore(claim): OPS-R86

    Its body ends with these lines, the sign-off in your own name:

    Claiming OPS-R86.
    
    Spec: OPS-R86
    
    Signed-off-by: Your Name <[email protected]>
  • brand0 of 3 open pull requests

    How to claim it

    With lfdev, from a clone of the repository:

    lfdev claim OPS-R86

    Or in GitHub's editor, adding this row to the tracker:

    [[requirement]]
    id = "OPS-R86"
    state = "open"
    

    Edit status.toml on GitHub

    Open the pull request as a draft, titled:

    chore(claim): OPS-R86

    Its body ends with these lines, the sign-off in your own name:

    Claiming OPS-R86.
    
    Spec: OPS-R86
    
    Signed-off-by: Your Name <[email protected]>
  • sdk-ts0 of 3 open pull requests

    How to claim it

    With lfdev, from a clone of the repository:

    lfdev claim OPS-R86

    Or in GitHub's editor, adding this row to the tracker:

    [[requirement]]
    id = "OPS-R86"
    state = "open"
    

    Edit status.toml on GitHub

    Open the pull request as a draft, titled:

    chore(claim): OPS-R86

    Its body ends with these lines, the sign-off in your own name:

    Claiming OPS-R86.
    
    Spec: OPS-R86
    
    Signed-off-by: Your Name <[email protected]>
  • sdk-php0 of 3 open pull requests

    How to claim it

    With lfdev, from a clone of the repository:

    lfdev claim OPS-R86

    Or in GitHub's editor, adding this row to the tracker:

    [[requirement]]
    id = "OPS-R86"
    state = "open"
    

    Edit status.toml on GitHub

    Open the pull request as a draft, titled:

    chore(claim): OPS-R86

    Its body ends with these lines, the sign-off in your own name:

    Claiming OPS-R86.
    
    Spec: OPS-R86
    
    Signed-off-by: Your Name <[email protected]>
  • lemonfiber-companion0 of 3 open pull requests

    How to claim it

    With lfdev, from a clone of the repository:

    lfdev claim OPS-R86

    Or in GitHub's editor, adding this row to the tracker:

    [[requirement]]
    id = "OPS-R86"
    state = "open"
    

    Create status/OPS.toml on GitHub, the row filled in

    Open the pull request as a draft, titled:

    chore(claim): OPS-R86

    Its body ends with these lines, the sign-off in your own name:

    Claiming OPS-R86.
    
    Spec: OPS-R86
    
    Signed-off-by: Your Name <[email protected]>
  • sdk-python0 of 3 open pull requests

    How to claim it

    With lfdev, from a clone of the repository:

    lfdev claim OPS-R86

    Or in GitHub's editor, adding this row to the tracker:

    [[requirement]]
    id = "OPS-R86"
    state = "open"
    

    Edit status.toml on GitHub

    Open the pull request as a draft, titled:

    chore(claim): OPS-R86

    Its body ends with these lines, the sign-off in your own name:

    Claiming OPS-R86.
    
    Spec: OPS-R86
    
    Signed-off-by: Your Name <[email protected]>
  • integration-home-assistant0 of 3 open pull requests

    How to claim it

    With lfdev, from a clone of the repository:

    lfdev claim OPS-R86

    Or in GitHub's editor, adding this row to the tracker:

    [[requirement]]
    id = "OPS-R86"
    state = "open"
    

    Edit status.toml on GitHub

    Open the pull request as a draft, titled:

    chore(claim): OPS-R86

    Its body ends with these lines, the sign-off in your own name:

    Claiming OPS-R86.
    
    Spec: OPS-R86
    
    Signed-off-by: Your Name <[email protected]>
  • integration-mcp0 of 3 open pull requests

    How to claim it

    With lfdev, from a clone of the repository:

    lfdev claim OPS-R86

    Or in GitHub's editor, adding this row to the tracker:

    [[requirement]]
    id = "OPS-R86"
    state = "open"
    

    Edit status.toml on GitHub

    Open the pull request as a draft, titled:

    chore(claim): OPS-R86

    Its body ends with these lines, the sign-off in your own name:

    Claiming OPS-R86.
    
    Spec: OPS-R86
    
    Signed-off-by: Your Name <[email protected]>