Release 0.79.0 - #3914
Merged
Merged
Release 0.79.0#3914
Conversation
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>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
* refactor(mui): migrate off the legacy MUI Grid API
Move every remaining `@mui/material/Grid` usage to the v2 Grid API
(`@mui/material/Grid2`), which is a prerequisite for the @mui/material v7
bump: v7 removes the `Grid2` import path and repoints `Grid` at the v2 API,
renaming the old one to `GridLegacy`. Doing the API move on v6 first keeps
the version bump a mechanical rename.
The two APIs lay out differently, so this is not purely cosmetic:
- Legacy Grid spaces items with a negative container margin plus per-item
padding; the v2 Grid uses `gap` and subtracts the gap from item widths.
- A legacy `container` carried `width: 100%`. A v2 container does not, so a
container that is also a flex item (legacy `<Grid item container>`) needs
an explicit `size` to stay full-width. The three converted rows in
ItemsListingComponent and the one in LearningPathListingPage get
`size={12}` for this reason; containers whose parent is not itself a
container need nothing, since a block-level flex box already fills its
parent.
Also drop GridLayout's `GridContainer`/`GridColumn`. Both were already
marked `@deprecated` in-repo as predating the site's formal designs, and
both wrapped the legacy API; their two consumers now use Grid directly with
the column widths inlined. The legacy `Grid` re-export is removed from the
ol-components barrel so the old API cannot come back by accident.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* refactor(mui): drop the no-op grid wrapper left by GridContainer
`GridContainer`/`GridColumn` always rendered a container holding a single
full-width column, so the pair contributed two divs and no layout: a v2
container spaces items with `gap`, and a gap never renders when there is one
item per row. Inlining them in the previous commit preserved that shape to
keep the API migration reviewable on its own; this removes it.
The wrapper was not quite free. `<Grid size={12}>` is a flex item, which
establishes an independent formatting context, so `ListHeaderGrid`'s vertical
margins could not collapse out of it — removing the wrapper puts them in
`Container`'s block formatting context, where they can. Verified they don't:
against the pre-migration render, `/learningpaths` differs only inside a
2x40px region near the page bottom, with the heading and every element above
it byte-identical. Collapsing a 1rem margin would have shifted the page.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix(docker): install chromium from trixie instead of Debian sid trixie now carries chromium 152.0.7977.75-1~deb13u1, so the sid apt source added for chromium is no longer needed. Keeping it pulled libc6 2.43-4 from sid over the hardened base image's 2.41-12+deb13u3+dhi2, which is what made #3888's --force-confnew necessary in the first place. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * Fix comment formatting in Dockerfile Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --------- Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com> Co-authored-by: Tobias Macey <tmacey@mit.edu> Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
OpenAPI ChangesNo changes to report, but the specs are different. Unexpected changes? Ensure your branch is up-to-date with |
odlbot
added
waiting for checkboxes
all checkboxes checked
and removed
deploying to rc
waiting for checkboxes
all checkboxes checked
labels
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
Matt Bertrand
renovate[bot]
Nathan Levesque
Chris Chudzicki
zawan-ila