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

Updates to Phive-managed tools #425

Closed
dkarlovi opened this issue May 4, 2022 · 4 comments
Closed

Updates to Phive-managed tools #425

dkarlovi opened this issue May 4, 2022 · 4 comments

Comments

@dkarlovi
Copy link
Contributor

dkarlovi commented May 4, 2022

Not sure how exactly this works, but what's the workflow to update Phive based tools?

For example, most recent Infection is 0.26.8.

Infection in the most recent Docker image jakzal/phpqa:1.69.3-php8.1-alpine is 0.21.5. How do those tools get updated?

@dkarlovi
Copy link
Contributor Author

dkarlovi commented May 4, 2022

Note, I've found this:

"phive-install": {
"alias": "infection@^0.21",
"bin": "%target-dir%/infection",
"sig": "C5095986493B4AA0"
}

in the meantime, but not sure how exactly it's meant to be updated? Where does the signature and the versions come from?

@jakzal
Copy link
Owner

jakzal commented May 5, 2022

Phive should always install the latest. Not sure if we need a restriction here. ^ means something else in pre 1.x versions.

@dkarlovi
Copy link
Contributor Author

dkarlovi commented May 5, 2022

Maybe a blurb how to do the update for Phive sourced tools might allow some updates to happen.

I agree we should probably allow Phive to install latest by default.

@jakzal
Copy link
Owner

jakzal commented May 23, 2022

I have removed most (all? ;) ) of constraints from tools installed with phive now #428

@jakzal jakzal closed this as completed May 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants