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

Upgrade to faraday 2.0.1+ #78

Open
cjcolvar opened this issue Jan 12, 2022 · 0 comments
Open

Upgrade to faraday 2.0.1+ #78

cjcolvar opened this issue Jan 12, 2022 · 0 comments

Comments

@cjcolvar
Copy link
Member

Faraday 2.0 had a breaking change requiring the setting of a default adapter before it could be used. It looks like faraday 2.0.1 reverted that change so no action is needed on the part of applications in order to upgrade.

The landscape of our core components use of faraday appears to be:

  • active_fedora: ~> 0.12
  • ldp: no restrictions
  • questioning_authority: < 2
  • valkyrie: < 1

These gems should be tested with versions <1, 1.x, and 2.x and their restrictions relaxed to allow any of the compatible versions. It should be possible to support all of them based upon the work done in rsolr (rsolr/rsolr#231).

tpendragon added a commit to samvera/valkyrie that referenced this issue Jan 12, 2022
jeremyf pushed a commit to samvera/valkyrie that referenced this issue May 24, 2023
Backporting db34b1e onto the v2.2.0
tag's SHA.

Work towards samvera/maintenance#78
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Backlog
Development

No branches or pull requests

1 participant