Mirantis / Mirantis/cri-dockerd
build artifacts for all tags
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.4k
- Forks
- 356
- Avg merge
- 4d 4h
- Merged PRs (30d)
- 3
Description
hello I am minikube maintainer, and I would like to know what is the reason that the latetest tag https://github.com/Mirantis/cri-dockerd/releases/tag/v0.4.1
does not have the binaries ?
we currently have to maintain a copy of the artifacts
https://github.com/kubernetes/minikube/issues/21128
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the v0.4.1 release linked in the issue and compare its available assets with the artifact copy maintained by minikube in issue 21128. Then trace the repository's release process to determine why binaries are absent; done means the expected artifacts are available for all tags or the limitation is clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go, kubernetes
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100