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: upgrade pymongo and event-tracking #463

Merged
merged 1 commit into from
Nov 12, 2024
Merged

Conversation

regisb
Copy link
Contributor

@regisb regisb commented Nov 9, 2024

Description:

The constraint on event tracking is causing packages that depend on event-tracking (such as edx-search) to require pymongo==3.3.13, which is turn breaking other packages, such as openedx/forum. This requirement is no longer necessary since July 31st 2024 when this issue was closed: openedx/edx-platform#34586
Edx-platform now runs pymongo=4.4.0: https://github.com/openedx/edx-platform/blob/master/requirements/edx/base.txt

Merge checklist:

  • All reviewers approved
  • CI build is green
  • If adding new checks, followed how_tos/0001-adding-new-checks.rst
  • Changelog record added (should I?)
  • Documentation updated (not only docstrings) (if needed)
  • Commits are squashed

The constraint on event tracking is causing packages that depend on event-tracking (such as edx-search) to require pymongo==3.3.13, which is turn breaking other packages, such as openedx/forum. This requirement is no longer necessary since July 31st 2024 when this issue was closed: openedx/edx-platform#34586
Edx-platform now runs pymongo=4.4.0: https://github.com/openedx/edx-platform/blob/master/requirements/edx/base.txt
@openedx-webhooks openedx-webhooks added the open-source-contribution PR author is not from Axim or 2U label Nov 9, 2024
@openedx-webhooks
Copy link

Thanks for the pull request, @regisb!

What's next?

Please work through the following steps to get your changes 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

🔘 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.

🔘 Let us know that your PR is ready for review:

Who will review my changes?

This repository is currently maintained by @openedx/axim-engineering. Tag them in a comment and let them know that your changes are ready for review.

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.

@UsamaSadiq UsamaSadiq merged commit c037a1b into openedx:master Nov 12, 2024
4 checks passed
@regisb regisb deleted the patch-1 branch November 12, 2024 10:22
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
None yet
Development

Successfully merging this pull request may close these issues.

Upgrade pymongo to Ensure Compatibility with MongoDB 6.0 and 7.0
3 participants