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.

Sign up for GitHub

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

Jump to bottom

Upgrade -r should always return value, even when no upgrade available #153

Closed
ferventcoder opened this issue Mar 6, 2015 · 0 comments
Closed

Upgrade -r should always return value, even when no upgrade available #153

ferventcoder opened this issue Mar 6, 2015 · 0 comments
Assignees
@ferventcoder
Labels
5 - Released Improvement
Milestone
0.9.9.2

Comments

@ferventcoder
Copy link
Member

This is necessary for package managers to be able to detect latest version or not.
@ferventcoder ferventcoder self-assigned this Mar 6, 2015
@ferventcoder ferventcoder added this to the 0.9.9.2 milestone Mar 6, 2015
@ferventcoder ferventcoder changed the title Upgrade --noop -r should always return value, even when no upgrade available Upgrade -r should always return value, even when no upgrade available Mar 6, 2015
ferventcoder added a commit that referenced this issue Mar 6, 2015
@ferventcoder
(GH-153) Upgrade -r should always return a value
76dfd59 
When running `upgrade --noop -r`, a value should always return the
lastest version found, even if that is the version installed over the
version available.
ferventcoder added a commit that referenced this issue Mar 6, 2015
@ferventcoder
Merge branch 'stable'
9f2f6d3 
* stable:
  (GH-153) Upgrade -r should always return a value
  (GH-141) Handle option w/surrounding apostrophes
  (maint) Correcting typos
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ferventcoder ferventcoder

Labels
5 - Released Improvement
Projects
None yet
Milestone
0.9.9.2
Development

No branches or pull requests
2 participants
@ferventcoder @gep13