Skip to content

clib upgrade default behavior #230

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
Merged
merged 2 commits into from
Jan 10, 2021
Merged

clib upgrade default behavior #230

merged 2 commits into from
Jan 10, 2021

Conversation

@Isty001
Copy link
Member

@Isty001 Isty001 commented Jan 10, 2021

This PR resolves #212

stephenmathieson
stephenmathieson reviewed Jan 10, 2021
View reviewed changes
stephenmathieson
stephenmathieson approved these changes Jan 10, 2021
View reviewed changes
Copy link
Member

@stephenmathieson stephenmathieson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would be nice if we had some tests for this, but won't hold this PR up for that (since they don't exist already).

@Isty001
Copy link
Member Author

Isty001 commented Jan 10, 2021

Would be nice if we had some tests for this

Agree with that, it's on my todo to document and, test the less known features.

@Isty001 Isty001 merged commit 0fc8b97 into master Jan 10, 2021
@stephenmathieson stephenmathieson deleted the upgrade-default branch January 10, 2021 17:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@stephenmathieson stephenmathieson stephenmathieson approved these changes

@jwerle jwerle jwerle approved these changes

Assignees

No one assigned

Labels

enhancement

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

clib upgrade should install the latest tag

4 participants

@Isty001 @stephenmathieson @jwerle