sysutils/containerd2.4.2_1

various: Bump Go ports for Go 1.26.10 / 1.27.3

sysutils/containerd: Update to 2.4.2

various: Bump Go ports

various: Drop Go 1.26+ version pin

This is a nop since 1.26 is the oldest supported version.

sysutils/containerd: Update to 2.4.1

sysutils/containerd: Update to 2.4.0

sysutils/containerd: Update to 2.3.5

many: Bump go ports for 1.26.8 and 1.27.1

sysutils/containerd: Update to 2.3.4

various: Bump go ports for go-1.25.14 / 1.26.7

various: Bump go ports for go-1.25.13 / 1.26.6

sysutils/containerd: Update to 2.3.3

various: Bump go ports for go-1.25.12 / 1.26.5

sysutils/containerd: Update to 2.3.2

various: Bump go ports for go-1.25.11 / go-1.26.4

sysutils/containerd: Update to 2.3.1

sysutils/containerd: Fix build after recent changes in Uses/go.mk

various: Bump ports for Go 1.26.3

sysutils/containerd: Update to 2.3.0

sysutils/containerd: Update to 2.2.3

various: Bump go ports for go-1.25.9 / 1.26.2

sysutils/containerd: Update to 2.2.2

various: Bump ports for Go 1.25.8

various: Bump ports for Go default 1.24->1.25

various: Bump Go ports for 1.24.13

various: Bump Go ports for 1.24.12

sysutils/containerd: Update to 2.2.1

sysutils/containerd: Update to 2.2.0

sysutils/containerd: Update to 2.1.5

many: Unpin Go ports

* Ports that were pinned to a deprecated version of Go (1.23 or older)
  have been unpinned.

* Ports that were pinned to a still-supported version of Go (1.24 or
  newer) have been converted to requesting that as their minimum Go
  version.

* Ports that had been forcibly deprecated for pinning an expired Go
  version have been undeprecated.

many: Unsupported Go dep; deprecate and schedule for removal

There are about 75 ports that depend on old, unsupported Go
versions. I've scheduled those Go versions for deletions on
2025/01/01, and so these ports are scheduled for removal on
that same day.

HOWEVER....

Likely NONE or VERY VERY FEW of these ports will actually need
to be deleted! This stems from a misunderstanding:

When go.mod says "go 1.23", it means that it requires AT LEAST
go-1.23. Locking a port to a specific go version should almost
never happen; it is reserved for when a package absolutely
cannot build with any newer version, and it almost means that
the port will only last 1 year (Go releases new minors twice a
year).

Where a port has
USES=go:1.23
maintainers should attempt build with just
USES=go

If that works, please either commit it or submit it in a PR.

Same goes go
USES=go:1.23,modules
to attempt
USES=go,modules

go123 ports: Bump for 1.23.12

sysutils/containerd: Update to 2.1.4

sysutils/containerd: Update to 2.1.3

sysutils/containerd: Update to 2.1.1

sysutils/containerd: Update to 2.1.0

sysutils/containerd: Update to 2.0.5

go: Bump ports for go124 update

sysutils/containerd: Update to 2.0.4

Bump all go ports for yesterday's releases

sysutils/containerd: Update to 2.0.2

all: Bump after lang/go122 update

PR:		284181
MFH:		2025Q1

sysutils/containerd: Update to 2.0.1

sysutils/containerd: Update to 2.0.0

sysutils/containerd: Update to 1.7.23

sysutils/containerd: Update to 1.7.22

Event:		DevSummit/202409

sysutils/containerd: Update to 1.7.21

all: Bump after lang/go121 update

sysutils/containerd: Update to 1.7.20

sysutils/containerd: Update to 1.7.19