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

chore: undowngrade dependencies #272

Closed
wants to merge 1 commit into from

Conversation

hairmare
Copy link
Contributor

I ran a poetry update on add the dependencies that are currently being downgraded in CI:

  - Downgrading pycparser (2.22 -> 2.21)
  - Downgrading cffi (1.16.0 -> 1.15.1)
  - Downgrading chardet (5.2.0 -> 5.1.0)
  - Downgrading cryptography (42.0.8 -> 42.0.4)
  - Downgrading texttable (1.7.0 -> 1.6.7)
  - Downgrading babel (2.15.0 -> 2.12.1)
  - Downgrading certifi (2024.6.2 -> 2023.7.22)
  - Downgrading charset-normalizer (3.3.2 -> 3.1.0)
  - Downgrading django (4.2.13 -> 4.2.11)
  - Downgrading setuptools (70.0.0 -> 68.0.0)
  - Downgrading typing-extensions (4.12.2 -> 4.6.3)
  - Downgrading urllib3 (2.2.1 -> 2.0.7)
  - Downgrading josepy (1.14.0 -> 1.13.0)
  - Downgrading py-moneyed (3.0 -> 2.0)
  - Downgrading requests (2.32.3 -> 2.32.2)
  - Downgrading tornado (6.4.1 -> 6.4)
  - Downgrading django-money (3.5.2 -> 3.4.1)
  - Downgrading sentry-sdk (2.5.1 -> 2.3.1)

Before this change the pipeline always tried to downgrade things like cffi and setuptools that it should not downgrade.

Let's see it awk '/Downgrading/ {print $3}' poetry-output.txt | xargs -n1 poetry update makes healthy again.

I'm not sure about all of the changes, but clearly the downgrade listed above don't seem to be what we need.

@hairmare hairmare force-pushed the chore/no-more-downgrading branch from 262a8b9 to 015842e Compare June 17, 2024 06:17
@hairmare
Copy link
Contributor Author

still affected by #25

@hairmare hairmare closed this Jun 17, 2024
@hairmare hairmare deleted the chore/no-more-downgrading branch June 17, 2024 06:26
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