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

Slugify namespace #106

Merged
merged 3 commits into from
Feb 5, 2020
Merged

Slugify namespace #106

merged 3 commits into from
Feb 5, 2020

Conversation

nuwang
Copy link
Member

@nuwang nuwang commented Feb 5, 2020

No description provided.

@coveralls
Copy link

coveralls commented Feb 5, 2020

Coverage Status

Coverage increased (+0.03%) to 90.505% when pulling c6b1f29 on slugify_namespace into bc9dcfe on master.

@@ -1,13 +1,16 @@
# Generated by Django 2.0 on 2019-06-21 18:05
# Generated by Django 2.2.6 on 2020-02-05 11:57
Copy link
Contributor

Choose a reason for hiding this comment

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

Should update Django to >=2.2.9 to avoid the known security vulnerability.

Copy link
Member Author

Choose a reason for hiding this comment

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

I regenerated the migrations with latest but the version didn't affect the migrations.

@afgane afgane merged commit c74b036 into master Feb 5, 2020
@afgane afgane deleted the slugify_namespace branch February 5, 2020 17:43
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

3 participants