Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Arlon CLI new version check #61

Closed
cre8minus1 opened this issue Jun 2, 2022 · 3 comments · Fixed by #304
Closed

Arlon CLI new version check #61

cre8minus1 opened this issue Jun 2, 2022 · 3 comments · Fixed by #304
Assignees
Labels
enhancement New feature or request in_code_review PRs which are in the process of code review size:S sprint9 UX
Milestone

Comments

@cre8minus1
Copy link
Member

cre8minus1 commented Jun 2, 2022

The Arlon CLI needs to check for new versions and notify users to upgrade.
This could also be automatic, however this will require all changes to not be breaking changes.

At a minimum users should be able to run arlon version and see their current version

  • Upgrade to be handled separately with arlon update to upgrade. Arlon CLI self-update #254
    The version command should return the current version and if a new version is available.

Aha! Link: https://pf9.aha.io/features/ARLON-155

@cre8minus1 cre8minus1 added the enhancement New feature or request label Jun 2, 2022
@cre8minus1 cre8minus1 added this to 0.9.0 Jun 2, 2022
@cre8minus1 cre8minus1 moved this to Todo in 0.9.0 Jun 2, 2022
@cre8minus1 cre8minus1 moved this from Todo to In Progress in 0.9.0 Jun 2, 2022
@cre8minus1 cre8minus1 moved this from In Progress to Todo in 0.9.0 Jun 2, 2022
@cre8minus1 cre8minus1 removed the status in 0.9.0 Jun 2, 2022
@cre8minus1 cre8minus1 removed this from 0.9.0 Jun 2, 2022
@cre8minus1 cre8minus1 added this to the 0.9.0 milestone Jun 3, 2022
@cre8minus1 cre8minus1 added this to 0.9.0 Jun 3, 2022
@cre8minus1 cre8minus1 moved this to Todo in 0.9.0 Jun 10, 2022
@bcle bcle added the size:L label Jul 1, 2022
@bcle bcle removed this from 0.9.0 Jul 6, 2022
@bcle bcle added this to 0.10.0 Jul 6, 2022
@bcle bcle modified the milestones: 0.9.0, 0.10.0 Jul 6, 2022
@Rohitrajak1807
Copy link
Member

This could also be automatic, however this will require all changes to not be breaking changes.

This requirement will need some thought.

@cruizen cruizen self-assigned this Sep 29, 2022
@cruizen cruizen changed the title Arlon CLI self-update & new version check Arlon CLI new version check Oct 4, 2022
@cruizen cruizen added size:M size:S and removed Needs Review For all new issues that are unplanned, have no milestone or project. size:L size:M labels Oct 4, 2022
@cruizen cruizen moved this to Todo in 0.10.0 Oct 17, 2022
@cruizen cruizen added sprint9 and removed sprint8 labels Nov 14, 2022
@cruizen
Copy link
Member

cruizen commented Nov 14, 2022

Deferring to sprint 9

@cruizen cruizen removed their assignment Nov 14, 2022
@cruizen
Copy link
Member

cruizen commented Nov 14, 2022

If a user is on v0.3.5, the output of arlon version will be like : Arlon v0.3.5 \n Arlon is outdated. A new version v0.3.7 is available. Please update Arlon ....
If a user is on v0.9.1, the output of arlon version will be like : Arlon v0.9.1 \n Arlon is outdated. A new version v0.9.12 is available. Please update Arlon ....

We will need to maintain the latest update version for each Arlon minor version.
arlon update can in future ask the user if they want to update to a new major version - and warn if required if that's a breaking change.

For the solution: We can maintain the latest available version for a release in a public location like GitHub release artifacts list.

@Rohitrajak1807 Rohitrajak1807 moved this from Todo to In Progress in 0.10.0 Nov 14, 2022
Repository owner moved this from In Progress to Done in 0.10.0 Nov 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request in_code_review PRs which are in the process of code review size:S sprint9 UX
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

5 participants