Skip to content

deps: bump cairosvg to 2.9.1 (GHSA-c3jg-qh8m-j3h2) - #4741

Open
katsugtgz wants to merge 2 commits into
openedx:masterfrom
katsugtgz:deps-cairosvg-2.9.1
Open

katsugtgz wants to merge 2 commits into
openedx:masterfrom
katsugtgz:deps-cairosvg-2.9.1

Conversation

@katsugtgz

Copy link
Copy Markdown

Updates cairosvg to 2.9.1 to address GHSA-c3jg-qh8m-j3h2.

Evidence:

  • requirements/base.txt, requirements/production.txt, and requirements/local.txt pinned cairosvg==2.9.0 (requirements/base.in leaves the version unpinned, so the compiled files carry the pin)
  • osv-scanner reported GHSA-c3jg-qh8m-j3h2 for cairosvg 2.9.0 in requirements/base.txt before the update
  • updated version: 2.9.1, clean across all currently listed cairosvg advisories per OSV

Validation (make ci_up plus make ci_test TOXENV=py312-django52, same as CI):

  • split groups 1 through 5: 369, 374, 455, 486, and 483 passed, 0 failures
  • group 6: 366 passed, 4 teardown errors. That group ran on a test database left over from a flaky first group-1 run on a cold stack. On a fresh stack, group 1 passes clean (369 passed, matching main with the same numbers), so the group-1 failures were first-run flakiness, not this change.
  • osv-scanner no longer reports GHSA-c3jg-qh8m-j3h2 after the update

Scope: dependency pin update only.

Commit author katsugtgz, unsigned.

@openedx-webhooks openedx-webhooks added the open-source-contribution PR author is not from Axim or 2U label Oct 13, 2026
@openedx-webhooks

Copy link
Copy Markdown

Thanks for the pull request, @katsugtgz!

This repository is currently maintained by @openedx/2u-phoenix.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

  • If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
    • This process (including the steps you'll need to take) is documented here.
  • If it doesn't, simply proceed with the next step.
🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

  • Dependencies

    This PR must be merged before / after / at the same time as ...

  • Blockers

    This PR is waiting for OEP-1234 to be accepted.

  • Timeline information

    This PR must be merged by XX date because ...

  • Partner information

    This is for a course on edx.org.

  • Supporting documentation
  • Relevant Open edX discussion forum threads
🔘 Submit a signed contributor agreement (CLA)

⚠️ We ask all contributors to the Open edX project to submit a signed contributor agreement or indicate their institutional affiliation.
Please see the CONTRIBUTING file for more information.

If you've signed an agreement in the past, you may need to re-sign.
See The New Home of the Open edX Codebase for details.

Once you've signed the CLA, please allow 1 business day for it to be processed.
After this time, you can re-run the CLA check by adding a comment below that you have signed it.
If the CLA check continues to fail, you can tag the @openedx/cla-problems team in a comment for further assistance.

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

Details
Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

  • The size and impact of the changes that it introduces
  • The need for product review
  • Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

@mphilbrick211

Copy link
Copy Markdown

Hi @katsugtgz - Welcome, and thank you for this contribution! In order for your CLA check to turn green, you'll need to submit a CLA form. If you are contributing as an individual, please fill out the individual CLA form here.

If you are contributing on behalf of an organization, please have your manager reach out to [email protected] so you may be added to your org's existing entity agreement.

Please let me know if you have any questions. Thanks!

@mphilbrick211 mphilbrick211 moved this from Needs Triage to Needs Tests Run or CLA Signed in Contributions Oct 22, 2026
@mphilbrick211 mphilbrick211 added the needs test run Author's first PR to this repository, awaiting test authorization from Axim label Oct 22, 2026
@mphilbrick211 mphilbrick211 removed the needs test run Author's first PR to this repository, awaiting test authorization from Axim label Oct 27, 2026
@katsugtgz

Copy link
Copy Markdown
Author

Hi @mphilbrick211, thanks for the welcome and sorry for the slow reply! I've just submitted the individual CLA form, so now I'm waiting on the DocuSign email. I'll sign it as soon as it shows up.

@mphilbrick211

Copy link
Copy Markdown

Thanks, @katsugtgz! I see it on our side, though we need a more detailed address. Is there a house or building number you could provide? If you don't mind, please re-submit with the updated address and I'll get this rolling for you!

@mphilbrick211

Copy link
Copy Markdown

Sorry, one more question, @katsugtgz - are you contributing on behalf of the organization in your email address, or is that your personal email? If you're contributing on behalf of an organization there's a different form we'll need to complete.

@katsugtgz

Copy link
Copy Markdown
Author

I'm contributing as an individual. My commits use my personal address ([email protected]). The other commit in the list ([email protected]) is a merge into this branch from the Open edX side, not mine.

I'll resubmit the individual CLA form with the full street address included.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

open-source-contribution PR author is not from Axim or 2U

Projects

Status: Needs Tests Run or CLA Signed

Development

Successfully merging this pull request may close these issues.

4 participants