Repository navigation
chore(console): ship admin dashboard v0.9.1 - #369
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
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.
Bumps the admin dashboard served at
/consolefromv0.7.0tov0.9.1(SEAMLESS_ADMIN_DASHBOARD_REFin the Dockerfile, plus the matching note in docs/configuration.md).Between them, v0.8.0 and v0.9.x add:
All the routes these use are on main.
There is no
v0.9.0tag. That release's workflow run skipped tagging because a changeset landed first, andv0.9.1(fells-code/seamless-auth-admin-dashboard#288) is the release that carries all of it.I also removed a stale Dockerfile comment that said release tags had not been cut yet.
Verified:
v0.9.1resolves to 9e25a99 with a published GitHub Release.npm ci && npm run build:consoleat that tag builds cleanly, andindex.htmlreferences/console/assets. The commit hook ran lint, format, typecheck, coverage and build. I could not run a full Docker build locally (Docker isn't running), and CI does not build the image on pull requests (docker-publish.ymlruns on release tags), so the next API release is the first full build of this stage. The stage itself is unchanged apart from the ref.