Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nixos/doc/releases: Do not tag the release #124364

Closed
wants to merge 1 commit into from

Commits on May 25, 2021

  1. nixos/doc/releases: Do not tag the release

    I have seen a customer use the release tag as a pinned version
    and the same can happen in flake input urls or similar input
    configs, like `niv --branch`.
    This results in a out of date version of the _all_ system
    packages, putting users at risk of security vulnerabilities
    and other issues that are addressed during the lifetime of a
    Nixpkgs/NixOS release.
    
    So clearly the tag poses a risk, but does it have a benefit?
    I don't think so. It does not name the branch-off point, so we
    don't need it for git operations. It does not represent the
    best or canonical version of the release either, as further
    fixes always occur after the release date. If it were the case,
    we'd tag all channel updates, but we don't, so for the same
    reasons, we should not tag the release.
    roberth committed May 25, 2021
    Configuration menu
    Copy the full SHA
    663eac8 View commit details
    Browse the repository at this point in the history