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

Unpin dependencies in TOML file. #315

Merged
merged 1 commit into from
Dec 14, 2023
Merged

Conversation

tim-schilling
Copy link
Member

It's a bit hard to track why we have these dependencies pinned. We're avoiding testing with latest versions due to them which will make future upgrades more difficult. It's probably better to deal with any incompatible versions and document them thoroughly so we know what is all required.

Closes #313, #299, #305

It's a bit hard to track why we have these dependencies pinned.
We're avoiding testing with latest versions due to them which
will make future upgrades more difficult. It's probably better
to deal with any incompatible versions and document them
thoroughly so we know what is all required.
@tim-schilling
Copy link
Member Author

@sondrelg @JonasKs my plan is to release 1.12.0 dropping py3.7 support, adding py3.12 and django 5.0

Then this change and upgrade to 1.13.0

Then Django 4.0 and 4.1, and upgrade to 1.14.0

@tim-schilling tim-schilling merged commit bfb3e8f into master Dec 14, 2023
60 checks passed
@tim-schilling tim-schilling deleted the dependency-updates branch December 14, 2023 13:51
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.

None yet

1 participant