Manage the lifecycle of dependencies using annotations
- Dominant language
- Go
- Stars
- 50
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
New registry format supports annotating dependencies (and whole registry as well). We can use this feature to provide better prompts about updates. I don't know yet how this annotations should look, but I have few ideas for how they could be used:
- Prevent installing obsolete or experimental versions (unless forced?)
- Point to release notes when prompting about new major versions
- Display warnings about using deprecated or obsolete version of a command
- Display info about new URL for the registry
- Point to another command which replaces current one
I'm not sure if we want all of these to be implemented, let me know what do you think.
Contributor guide
Research direction
Start by reviewing the registry format and how the CLI currently handles dependency installation and update prompts. Clarify which annotation behaviors are in scope before locating the relevant entry points. Done should include an agreed annotation design and the selected lifecycle prompts, with coverage for the supported cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100