Repository navigation
Tag helm-charts 9.0.0-beta.3 and bump the submodule pointer off beta.2 #70
Description
Question
The ui_react Helm component is stranded and unreachable from this repo.
- Upstream
helm-chartscommit3d3aca8— "feat(ui-react): deploy the React UI via the MINT chart (9.0.0-beta.3) (fix(ui-react): load the thread execution pipeline from Hasura (#104) #105)" — adds the component, but was never tagged. Newest tag is9.0.0-beta.2. - This repo's
helm-chartssubmodule points atab0571e(9.0.0-beta.2), which predates it.
So the chart work exists but nothing in the monorepo can reach it. Tag 3d3aca8 as 9.0.0-beta.3 upstream, then bump the submodule pointer here and commit on a branch off develop.
Confirm while you are in there: the component is opt-in and disabled by default, and the legacy ui component is byte-for-byte unchanged.
Activity
mosoriob commentedon Aug 8, 2026
Done
Upstream tag.
9.0.0-beta.3now exists onmintproject/mint, pointing at3d3aca8dfd0facf96f4d2ec71c9df8fa52d0fc76— thefeat(ui-react)release commit.Published as a pre-release with the packaged chart attached, matching how
9.0.0-beta.1and9.0.0-beta.2were cut:https://github.com/mintproject/mint/releases/tag/9.0.0-beta.3
Submodule pointer. Bumped
ab0571e->3d3aca8onchore/helm-charts-9.0.0-beta.3,PR against
develop: #82Both confirmations hold
The component is opt-in.
components.ui_react.enabled: falseby default. Thereason is documented in
values.yamland is worth carrying forward: enabling itrequires an OAuth2 client registered with the identity provider, distinct from
the legacy UI's — the provider allows one callback URL per client, so sharing
one would break login on the existing UI. That is a hard input to
Settle the window.MINT_CONFIG values for the TACC deployment
and to Check whether the OAuth2 redirect URI for mint.tacc.utexas.edu is already registered.
The legacy
uicomponent is untouched.values.yaml: 52 insertions, 0 deletions — a newui_react:block appendedafter the
ui:block, nothing edited.ui.yaml,ingress-ui.yamlorui-config.yamltemplate appears in the diff._helpers.tplonly appends three new definitions (helm.ui_react_node_port,mint.component_url,mint.ui_react.endpoint); no existing helper is modified.index.yamlgained exactly one entry (131 -> 132) — the beta.3 chart. Diffing theversion/digest sets shows nothing dropped.
Two facts later tickets depend on
components.ui_react.image.tagcurrently reads55a3472a975b11af51fcfedf3f6f9b66db024bf0. Unlike every other component,ui-reactlives in this repo rather than a submodule, soupdate-helm-image-tags/dynamo-bump-from-branch— which resolve submoduleSHAs — will silently skip it. It must be set by hand at deploy time.
ui_reactgets its own host, not a path prefix. The chart defaults tonext.mint.localbecause the app is built to be served from the root. The flipat Flip mint.tacc.utexas.edu to ui-react
is therefore a host reassignment, not a route change.
Open loop
PR #82 is not merged. Nothing downstream is blocked on the merge except the flip
itself — settling the config values can proceed against the chart as tagged.
chore: bump helm-charts to 9.0.0-beta.3 (ui-react chart component) (#82)
mosoriob commentedon Aug 8, 2026
Open loop closed: #82 merged to
developas200a0d7.git submodule status helm-chartsnow reads3d3aca8… (9.0.0-beta.3)— the pointer and the tag agree, and nothing downstream is waiting on this ticket any more.