Skip to content

The amendment invariant check #5

Description

@Maximilian-Nesslauer

A release file can never become more permissive after publish, only less.
Enforced per file, mechanically.

Allowed:

  • setting yanked = true, with an optional yanked_reason
  • adding or lowering game_max and game_max_revision, or raising game_min and game_min_revision
  • tightening a dependency or loader bound: adding or lowering a max, or adding or raising a min, on an existing entry
  • adding a dependency entry that was missing, including a conflict

Never: widening or removing a bound, removing an entry, or touching identity, the version, the download or the install data.

An amendment touches release files of exactly one listing, one or several, so a mod found to break at a given game build gets game_max added to every affected past release in one pull request rather than N.

Who may amend: the verified owner of the listing, through the same ownership check as KSAModding/content-index#4, or a steward.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:infraCI, workflows, automationarea:publishinglisting and release flows

    Type

    No type

    Projects

    Status
    Inbox

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions