github.com/demonoid81/containerd@v1.3.4/releases/v1.0.0-beta.toml (about)

     1  # commit to be tagged for new release
     2  commit = "HEAD"
     3  
     4  project_name = "containerd"
     5  github_repo = "containerd/containerd"
     6  
     7  # previous release
     8  previous = "v1.0.0-beta.2"
     9  
    10  pre_release = true
    11  
    12  preface = """\
    13  After rounding out the feature set in beta.2, we have taken a number of stability fixes.
    14  
    15  This release contains mostly bug fixes, code cleanup and improvements to useability of
    16  the client and ctr tool."""
    17  
    18  # notable prs to include in the release notes, 1234 is the pr number
    19  [notes]
    20  
    21    [notes.ctr]
    22    title= "`ctr` makeover"
    23    description = """\
    24  `ctr` is getting a ~makeover~! The end goal is for commands to be consistent and scoped.
    25  Most notably:
    26  - `push`, `pull` are now `images` subcommands: `ctr images push`, `ctr images pull`
    27  - `fetch`, `fetch-object`, and `push-object` are `content` subcommands
    28  - `rootfs unpack` is now `snapshot unpack`
    29  - `apply` no longer exists. RIP"""
    30  
    31    [notes.gc]
    32    title= "Garbage collector improvements"
    33    description = """\
    34  The garbage collector continues to improve with this release, including bug
    35  fixes on the client causing races and a new lease feature for making retention
    36  from the client easier.
    37  
    38  The lease API was added to make it easier for clients to prevent content and
    39  snapshots from being garbage collected while they are being actively worked on
    40  (such as from pull, import, or checkpoint). The API includes functions for
    41  creating, deleting, and listing leases. The lease gets attached to the context
    42  and the backend metadata store sees it and associates newly created content
    43  and snapshots with that lease.
    44  
    45  Leases are currently acquired and released automatically through the client.
    46  From the user perspective, fewer `gc.root` labels should be seen on client
    47  during pull/import operations or left over after a failed operation."""
    48  
    49  
    50  
    51  [breaking]