fix: Adds release branch in catalog-info

[farhaanbukhsh]

Description

This PR adds the key to catalog-info so that we can tag a release automatically next time.

[openedx-webhooks]

Thanks for the pull request, @farhaanbukhsh!

This repository is currently maintained by @openedx/axim-engineering.

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

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

---

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:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

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.

[farhaanbukhsh]

@feanil Please, can you review this PR :) thanks a lot in advance.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 55.35%. Comparing base (78d4077) to head (722ee85).
Report is 2 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #278   +/-   ##
=======================================
  Coverage   55.35%   55.35%           
=======================================
  Files           3        3           
  Lines          56       56           
=======================================
  Hits           31       31           
  Misses         25       25           

Flag	Coverage Δ
unittests	55.35% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[feanil]

@farhaanbukhsh why do we need to tag this repo for releases? We normally don't tag libraries that are getting pulled into the release via a tagged repo, in this case edx-platform.

[farhaanbukhsh]

@farhaanbukhsh why do we need to tag this repo for releases? We normally don't tag libraries that are getting pulled into the release via a tagged repo, in this case edx-platform.

Hey @feanil I am sorry I don't have much knowledge about which repos we tag and which we don't so I would be happy if you could point to any discussion or document where I can learn more about it.

I had a brief discussion with Sarina on openedx/axim-engineering#1338 (comment) which led to the two PRs

I am open to learning more about this process so that I don't cause more trouble :)