Skip to content

Allow PHP Versions to Update #17

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

Merged
merged 7 commits into from
Apr 28, 2024
Merged

Conversation

westy92
Copy link
Contributor

@westy92 westy92 commented Apr 25, 2024

Fixes #16.

@g105b is there an easy way to test this?

@westy92 westy92 marked this pull request as ready for review April 25, 2024 23:42
@westy92
Copy link
Contributor Author

westy92 commented Apr 26, 2024

@westy92
Copy link
Contributor Author

westy92 commented Apr 26, 2024

Should we bump php_build_version="build2.1.1" to 2.1.2?

@g105b
Copy link
Member

g105b commented Apr 26, 2024

Looks good to me, thanks so much for this PR.

The only thing I can't think of how to test is what happens to the runner when it runs again and there's a new release of PHP. I don't think there's a straightforward way of testing this without waiting for a new release and crossing our fingers that the functionality works as expected.

Do you have any other projects that haven't been built in a while that this can be tested with, just for clarity?

Should we bump php_build_version="build2.1.1" to 2.1.2?

Yes please. This is the only mechanism I am aware of that can be used to cache the actual php_build process, so when a new workflow starts it doesn't have to build PHP each time. As long as this string changes, it will invalidate the cache.

@westy92
Copy link
Contributor Author

westy92 commented Apr 26, 2024

Thank you for the review! I bumped the version. Unfortunately the only project I have using this I already tested with.

@g105b
Copy link
Member

g105b commented Apr 26, 2024

I think your fix is identifying an issue that is worse to keep in the repo than it would be if it caused a potential minor failure in the future, so I think it makes sense to merge directly. I have a lot of repositories that use this action every day, so I'll notice any issues straight away. Do you agree? If so I'll merge tonight.

@westy92
Copy link
Contributor Author

westy92 commented Apr 26, 2024

Yes I agree!

@westy92
Copy link
Contributor Author

westy92 commented Apr 26, 2024

I updated the version to 2.2.1 since 2.2.0 has already been tagged and released but never updated here.
I opened two other PRs that you can see referenced above.

Thank you for reviewing this! Make sure to tag v2.2.1 and v2 after merging. :)

@g105b g105b merged commit 79797db into php-actions:master Apr 28, 2024
@g105b
Copy link
Member

g105b commented Apr 28, 2024

Cheers! I'll make the release now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants