moby / moby/swarmkit

Latest tagged SwarmKit release is very old

Open
#3,017 0 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
3.7k
Forks
676
Avg merge
4d 9h
Merged PRs (30d)
6

Description

The latest (and only) semver-tagged release of the swarmkit repo is currently v1.12.0, tagged on Jul 28, 2016; according to GitHub, there have been 2225 commits since that tag was added.

The Go module system uses semver tags to identify stable releases of modules, so at the moment go get -d github.com/docker/swarmkit resolves to v1.12.0 and https://pkg.go.dev/github.com/docker/swarmkit?tab=versions shows it as the latest (and only!) stable version.

Given that packages in other Docker modules (such as github.com/docker/cli) don't seem to build at all with that version, I'm guessing that it is no longer supported or recommended.

Is it perhaps time to tag a newer release? Barring that, could you add a go.mod file and retract the very old one?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the repository's existing semver tags and module metadata; the issue identifies the missing go.mod and the v1.12.0 release as the relevant starting points. Clarify whether a newer release should be tagged or the old version retracted, then verify the resulting version information through Go module resolution and pkg.go.dev.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
release
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.