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: LSDV-5178: Update django version to fix CVE-2023-31047 #4245

Merged
merged 1 commit into from
May 29, 2023

Conversation

niklub
Copy link
Collaborator

@niklub niklub commented May 25, 2023

PR fulfills these requirements

  • Commit message(s) and PR title follows the format [fix|feat|ci|chore|doc]: TICKET-ID: Short description of change made ex. fix: DEV-XXXX: Removed inconsistent code usage causing intermittent errors
  • Tests for the changes have been added/updated (for bug fixes/features)
  • Docs have been added/updated (for bug fixes/features)
  • Best efforts were made to ensure docs/code are concise and coherent (checked for spelling/grammatical errors, commented out code, debug logs etc.)
  • Self-reviewed and ran all changes on a local instance (for bug fixes/features)

Change has impacts in these area(s)

(check all that apply)

  • Product design
  • Backend (Database)
  • Backend (API)
  • Frontend

Describe the reason for change

(link to issue, supportive screenshots etc.)

What does this fix?

(if this is a bug fix)

What is the new behavior?

(if this is a breaking or feature change)

What is the current behavior?

(if this is a breaking or feature change)

What libraries were added/updated?

(list all with version changes)

Does this change affect performance?

(if so describe the impacts positive or negative)

Does this change affect security?

(if so describe the impacts positive or negative)

What alternative approaches were there?

(briefly list any if applicable)

What feature flags were used to cover this change?

(briefly list any if applicable)

Does this PR introduce a breaking change?

(check only one)

  • Yes, and covered entirely by feature flag(s)
  • Yes, and covered partially by feature flag(s)
  • No
  • Not sure (briefly explain the situation below)

What level of testing was included in the change?

(check all that apply)

  • e2e
  • integration
  • unit

Which logical domain(s) does this change affect?

(for bug fixes/features, be as precise as possible. ex. Authentication, Annotation History, Review Stream etc.)

@netlify
Copy link

netlify bot commented May 25, 2023

Deploy Preview for heartex-docs canceled.

Name Link
🔨 Latest commit 2ff7de9
🔍 Latest deploy log https://app.netlify.com/sites/heartex-docs/deploys/646fa69d7989210007a67f22

@netlify
Copy link

netlify bot commented May 25, 2023

Deploy Preview for label-studio-docs-new-theme canceled.

Name Link
🔨 Latest commit 2ff7de9
🔍 Latest deploy log https://app.netlify.com/sites/label-studio-docs-new-theme/deploys/646fa69dce185700081f70bd

@niklub niklub changed the title Update django version to fix CVE-2023-31047 fix: LSDV-5178: Update django version to fix CVE-2023-31047 May 25, 2023
@codecov
Copy link

codecov bot commented May 25, 2023

Codecov Report

Patch and project coverage have no change.

Comparison is base (bb885be) 75.74% compared to head (2ff7de9) 75.74%.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop    #4245   +/-   ##
========================================
  Coverage    75.74%   75.74%           
========================================
  Files          156      156           
  Lines        12075    12075           
========================================
  Hits          9146     9146           
  Misses        2929     2929           

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

@niklub niklub merged commit 86a2eb1 into develop May 29, 2023
37 of 39 checks passed
bmartel pushed a commit that referenced this pull request May 30, 2023
Update django version to fix CVE-2023-31047

Co-authored-by: nik <nik@heartex.net>
bmartel added a commit that referenced this pull request May 30, 2023
* feat: LSDV-5035: Use created_at from draft as the annotation draft_created_at (#4259)

* feat: LSDV-5035: Use created_at from draft as the annotation created_at

* fix the update statement as it cannot be mass assigned and should not be open to this

* save the draft created at to its own field to not disturb existing data

* [submodules] Build static heartexlabs/dm2

* [submodules] Build static heartexlabs/dm2

* fix: LSDV-5163: Storage errors AttributeError can't set attribute 'storage' when pre-signed proxy urls are turned on (#4243)

* fix: LSDV-5163: Storage errors AttributeError can't set attribute 'storage' when pre-signed proxy urls are turned on

* removing the cache on the server, too hard to predict that this won't cause gaps in the frontend cache and subsequent errors over time.

* forgot to commit the change to not set the self.storage property of the model

* Update feedback api.py

---------

Co-authored-by: bmartel <bmartel@users.noreply.github.com>

* fix: LSDV-5178: Update django version to fix CVE-2023-31047 (#4245)

Update django version to fix CVE-2023-31047

Co-authored-by: nik <nik@heartex.net>

* fix: LSDV-5199: API docs redoc version updated to fix DOMPurify incompatibility (#4267)

* [submodules] Build static heartexlabs/label-studio-frontend

* docs: LSF Update

* [submodules] Build static heartexlabs/dm2

* [submodules] Build static heartexlabs/dm2

* [submodules] Build static heartexlabs/label-studio-frontend

---------

Co-authored-by: bmartel <brandonmartel@gmail.com>
Co-authored-by: bmartel <bmartel@users.noreply.github.com>
Co-authored-by: niklub <lubimov.nicolas@gmail.com>
Co-authored-by: nik <nik@heartex.net>
Co-authored-by: Travis Clark <travisjosephclark@gmail.com>
shayantabatabaee pushed a commit to shayantabatabaee/label-studio that referenced this pull request Sep 19, 2023
…nal#4245)

Update django version to fix CVE-2023-31047

Co-authored-by: nik <nik@heartex.net>
@deppp deppp deleted the fb-lsdv-5178 branch March 20, 2024 04:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants