-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Update guzzle major version from 5 to 7 #39387
Comments
I updated the list above with the affected apps and PRs to make it work. Most of the pipelines won't succeed until the core PR is merged. That should be pretty much it. But we can only know for sure if we take the step and merge this upgrade. So, do we want to proceed? @phil-davis @micbar @pmaier1 any objections? |
No objection from me. IMO it will be good to get this stuff up-to-date. |
Merge after 10.9, decided in planning. Edit: 10.10 was released, and we have merged after 10.10, for release in core 10.11 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 10 days if no further activity occurs. Thank you for your contributions. |
waiting on merge of #39368 to core, and then merging the various app PRs. |
Also see #40103 - a new patch release of v6 and v7 came out yesterday, giving this a kick along. |
Assigned myself. The main core PR #39368 has been merged. I will follow-up the oC10 app PRs and get all CI passing for apps. And make a release/test plan with what I think needs to be done in the coming "x" weeks to manually QA various combinations of core and apps to confirm that they work with Guzzle 7. @jnweiger FYI |
@phil-davis I've started the smoke test plan in https://github.com/owncloud/enterprise/issues/5247#issuecomment-1160077407 |
2022-06-28: PHP dependencies are up-to-date in all apps. Nightly CI passes in all apps. IMO we are at the point where we could:
|
Thanks. That is a good state to start building packages.
|
@jnweiger I created release issues for each of the apps that we know have had code changes for Guzzle7, and put them in the Releases project. The process of making RC1 tarballs could start next week. I don't think that there is any other code waiting to merge, but maybe check the open PRs in each app to see if there is anything that should be followed-up. |
@kiranadh1452 has done manual verification that the following apps still work without any obvious regressions when using the current core master (what will be 10.11.0 release) and the current code in the app repos (which will be released concurrently with core 10.11.0). So the formal QA of the release of each of these apps should be smooth. owncloud/files_external_ftp#99 owncloud/files_external_gdrive#77 https://github.com/owncloud/files_onedrive/issues/145 owncloud/files_external_dropbox#137 Reported Issue : |
updates are complete, All possible QA was done. The unticked items do not have a tet setup. |
core dependabot PR #39368 has been merged. That bumps to 7.4.4
PR #40154 adds a bump to 7.4.5 on 2022-06-21
This is a major version update of the "guzzle" library. It provides a framework in PHP for doing outgoing client requests. It is used in things like federated sharing, where one oC10 server needs to send requests to another oC10 federated server. We have various acceptance tests for federated sharing, so automated CI will cover the common federated sharing scenarios.
Some oC10 apps mention guzzle in their composer files. We will need to coordinate update those in sync with core.
They are:
Apps that use the client, but most likely still work:
Other things considered:
Apps to pre-release:
The following apps have had their code updated so that it detects if Guzzle5 or Guzzle7 libraries are available in core, and makes the appropriate Guzzle calls. This has been done for apps that are "backend" plugins for core, that, for example, manage "core" storage of users. It is much easier to upgrade when these apps support both Guzzle5 and Guzzle7. The new version of the app can be installed while you are running core 10.9 or 10.10, and it works fine. Then you upgrade core to 10.11, and you don't have to think about how to upgrade the app "at the same time".
We can and should do QA and release new versions of these apps ASAP (well before releasing core 10.11).
The text was updated successfully, but these errors were encountered: