Notify when newer versions are available
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
Research direction
The issue does not name any files, tests, or entry points. Start by locating the CLI startup flow and how its current version is defined or reported, then identify the project's release source. Done means the CLI checks for a newer version and notifies users according to an agreed update interval or version threshold, with behavior covered by tests.
Written by the indexing model from the issue text.
Description
The CLI should check for and notify the user when a newer version is available, as these usually have bug fixes and new features. Sometimes, breaking changes to APIs require that the user update the CLI.
If "update fatigue" is a concern, one could limit the notifications to certain intervals (e.g. once a day) or when the difference in major/minor/patch versions exceeds a certain threshold.
- Dominant language
- Go
- Stars
- 2
- Forks
- 5
- Avg merge
- 3h 49m
- Merged PRs (30d)
- 34
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from nais/cli
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 56/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 57/100
Maintainers usually reply within 1 day
-
mcp: mock schema is invalid GraphQL, so schema_* tests pass on a parse errorPossibly taken @Starefossen claimed this 2 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
mcp: schema_list_queries returns an array as structuredContent, and its outputSchema is invalidPossibly taken @Starefossen claimed this 2 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 68/100
Maintainers usually reply within 1 day
Similar issues
-
automation doc-healer documentation
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Anthropic /v1/messages: only the last thinking block of an assistant message is keptPossibly taken @Shayan12456 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ollama/ollama#19415 · 1 comment ·
Maintainers usually reply within 1 day
-
area:recipes event:contribfest format:human-first source:agent status:needs-triage type:recipe
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
cadence-workflow/cadence-ai-samples#140 ·
Maintainers usually reply within 1 day
-
customer issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
dolthub/doltgresql#3716 ·
Maintainers usually reply within 1 day
-
ux
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
evcc-io/evcc#35605 · 1 comment ·
Maintainers usually reply within 1 day