forked from openedx/frontend-component-header
-
Notifications
You must be signed in to change notification settings - Fork 18
feat!: upgrade to ulmo #36
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
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…enedx#557) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
….4.1 (openedx#558) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…enedx#559) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…edx#561) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…enedx#563) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…edx#566) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
This is going to be changing soon with the module federation work so I think it makes sense to be maintained by the committers-frontend group. I'm also cleaning up the old openedx.yaml file which is obsolete and out of date while I'm adding the new metadata that should be up-to-date.
…enedx#569) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
This reverts commit a229c34. We are temporarily re-introducing the Maintenance link, as the Maintenance Announcements tool is still in use, as discussed on: openedx/edx-platform#35852 For more details, see the related edx-platform revert: openedx/edx-platform#36107 In the future, this will be re-removed: openedx/edx-platform#36263
…edx#570) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…edx#576) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
BREAKING CHANGE: consumers must now use Paragon 22
Co-authored-by: Diana Catalina Olarte <diana.olarte@edunext.co>
…edx#581) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
We remove husky, which is triggering pre-push git hooks, including
running "npm lint". This is causing failures when building Docker
images, because "npm clean-install --omit=dev" automatically triggers "npm
prepare", which attemps to run "husky". But husky is not listed in the
build dependencies, only in devDependencies. As a consequence, package
installation is failing with the following error:
14.13 > @edx/frontend-app-ora-grading@0.0.1 prepare
14.13 > husky install
14.13
14.15 sh: 1: husky: not found
Similar to: openedx/frontend-app-learning#1622
…edx#587) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…edx#590) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…enedx#591) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…edx#592) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…edx#596) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…edx#599) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…edx#601) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…edx#605) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…enedx#609) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## ulmo/indigo #36 +/- ##
============================================
Coverage 68.58% 68.58%
============================================
Files 49 49
Lines 487 487
Branches 110 110
============================================
Hits 334 334
Misses 150 150
Partials 3 3 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
67f0273 to
27a9a5f
Compare
DawoudSheraz
approved these changes
Jul 16, 2025
27a9a5f to
eaca287
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is to sync teak/Indigo's changes with upstream master. We're doing this now to bring design token changes from upstream, the lack of which is currently failing our MFE build.
There are no build issues anymore, but there are styling/layout problems. Probably because we need to use design tokens in Indigo-related styling. I would create a follow-up PR for those changes.
Fixes: overhangio/tutor#1249