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 requirements.txt to cover Django 3.2 #182

Merged
merged 1 commit into from
Apr 23, 2021
Merged

Conversation

amureki
Copy link
Collaborator

@amureki amureki commented Apr 20, 2021

I missed that one while updating the codebase in #176

Not sure if we can simplify this to reduce possible clashes in the future...

@amureki amureki self-assigned this Apr 20, 2021
@amureki amureki mentioned this pull request Apr 20, 2021
@amureki
Copy link
Collaborator Author

amureki commented Apr 20, 2021

Mentioned in #181 (not sure if it is closed due to the codebase working in its current state or something else).

@berinhard I'd be glad to have a PyPI token in secrets, so I could release a bugfix version 1.3.1. 🙏

@amureki amureki requested a review from a team April 20, 2021 11:26
Copy link
Contributor

@anapaulagomes anapaulagomes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🕺

Copy link
Member

@berinhard berinhard left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@berinhard berinhard merged commit 8041b18 into main Apr 23, 2021
@berinhard berinhard deleted the django_requirements branch April 23, 2021 15:24
@berinhard
Copy link
Member

@amureki I've configured the secrets and added both you and @anapaulagomes as owners in pypi as well. Feel free to make a new release =}

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.

3 participants