Skip to content

[v1.5.0 GA] hygiene: tag github.com/containerd/x modules before GA #5345

@thaJeztah

Description

@thaJeztah

During the v1.5.0 pre-release cycles, we updated some components to current
"master" / "main" branches. Some of those components already did releases.

While it's "ok" to temporarily depend on unreleased versions of dependencies
(in pre-releases), we should return to tagged versions of these modules before
v1.5.0 GA. For modules we maintain, we can tag new releases, for other modules,
we need to reach out to their respective maintainers to inform if a new release
is pending (or to consider doing a new release).

Currently, the following modules are using a non-tagged version (but have tagged
releases available), and modules changes in master that are not yet included in
this repository's go.mod;

module diff since last release changes in master/main action
github.com/Microsoft/go-winio #5350 diff ✅ v0.4.17 was tagged and updated
github.com/containerd/imgcrypt #5349 diff ✅ v1.1.1 was tagged and updated
github.com/containerd/ttrpc (not yet vendored) diff ✅ (keeping at v1.0.2 for now)
github.com/opencontainers/runtime-spec diff diff update to latest? proposal for tagging new release; opencontainers/runtime-spec#1052
github.com/containerd/go-cni #5355 diff ✅ tag v1.0.2 and update
github.com/containerd/typeurl #5213 diff ✅ tag v1.0.2 and update

Pending pull requests that update dependencies:

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions