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

Bump django from 4.1.7 to 4.2.9 #704

Merged
merged 3 commits into from
Feb 8, 2024
Merged

Bump django from 4.1.7 to 4.2.9 #704

merged 3 commits into from
Feb 8, 2024

Conversation

elisakiv
Copy link
Contributor

Bumps django from 4.1.7 to 4.2.0.

@elisakiv elisakiv marked this pull request as draft January 18, 2024 18:57
Copy link

codecov bot commented Jan 25, 2024

Codecov Report

Attention: 4 lines in your changes are missing coverage. Please review.

Comparison is base (63a171f) 88.16% compared to head (80366e1) 88.15%.
Report is 6 commits behind head on dev.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##              dev     #704      +/-   ##
==========================================
- Coverage   88.16%   88.15%   -0.02%     
==========================================
  Files         152      152              
  Lines        6187     6188       +1     
==========================================
  Hits         5455     5455              
- Misses        732      733       +1     
Files Coverage Δ
src/web/static.py 68.75% <0.00%> (-1.47%) ⬇️

@elisakiv elisakiv changed the title Bump django from 4.1.7 to 4.2.0 Bump django from 4.1.7 to 4.2.9 Feb 1, 2024
@elisakiv elisakiv marked this pull request as ready for review February 1, 2024 18:01
@elisakiv elisakiv merged commit 894fc01 into dev Feb 8, 2024
11 of 12 checks passed
@ddabble ddabble deleted the django-4.2.0 branch February 8, 2024 18:05
@Gunvor4 Gunvor4 mentioned this pull request May 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants