Skip to content

docs: Mark repo for release; change lifecycle to Production - #226

Open
sarina wants to merge 1 commit into
mainfrom
sarina/catalog-info-updates
Open

docs: Mark repo for release; change lifecycle to Production#226
sarina wants to merge 1 commit into
mainfrom
sarina/catalog-info-updates

Conversation

@sarina

@sarina sarina commented Jul 31, 2026

Copy link
Copy Markdown
Contributor

Description

Align catalog-info.yaml with the fact that this is a production component & needs to be included in releases, per https://open-edx-proposals.readthedocs.io/en/latest/processes/oep-0010-proc-openedx-releases.html

@sarina sarina mentioned this pull request Jul 31, 2026
@codecov

codecov Bot commented Jul 31, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.55%. Comparing base (c4b53a3) to head (b45b5ce).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #226   +/-   ##
=======================================
  Coverage   91.55%   91.55%           
=======================================
  Files         151      151           
  Lines        2793     2793           
  Branches      610      610           
=======================================
  Hits         2557     2557           
  Misses        230      230           
  Partials        6        6           

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

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@arbrandes arbrandes left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See inline comment.

Comment thread catalog-info.yaml
# Note: This will only work if the repo is in the `openedx` org in github. Repos in other orgs that have this
# setting will still be treated as if they don't want to be part of the Open edX releases.
openedx.org/release: null
openedx.org/release: main

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Frontend-base apps are not meant to be release-tagged: they're semantically released instead. What defines which version is in a particular release is the frontend-template-site package.json (though the actual point-release comes from package-lock.json).

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants