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

Fix #586: require newer excon, use valid parameter keys interface #588

Merged
merged 6 commits into from
Jul 8, 2024

Conversation

ls-todd-lunter
Copy link
Contributor

Problem

As noted in #586, newer versions of Excon will freeze the valid request keys array. At require time, this will raise an error.

Solution

In version v0.63/v0.64, there was introduced a method on the base middleware that we can extend to satisfy the requirement necessary for the hijack middleware.

We can bump the minimum required excon version, and make use of that method, no longer modifying the constant.

@ls-todd-lunter ls-todd-lunter merged commit b78bd81 into master Jul 8, 2024
14 checks passed
@ls-todd-lunter ls-todd-lunter deleted the fix-excon-frozenerror branch July 8, 2024 19:29
bastelfreak added a commit to bastelfreak/beaker-docker that referenced this pull request Jul 8, 2024
2.2 and older allowed latest excon releases. excon v0.111.0 introduced a
frozen string that was incompatible with docker-api 2.2 and older. This
was fixed in upserve/docker-api#588. Bumping our
dependency to docker-api 2.3 or newer ensures that we don't pull in
broken versions by accident.
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

Successfully merging this pull request may close these issues.

1 participant