Skip to content

Bump vite from 6.4.1 to 6.4.2 in /app/status_monitor/frontend#371

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/app/status_monitor/frontend/vite-6.4.2
Closed

Bump vite from 6.4.1 to 6.4.2 in /app/status_monitor/frontend#371
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/app/status_monitor/frontend/vite-6.4.2

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Apr 7, 2026

Copy link
Copy Markdown
Contributor

Bumps vite from 6.4.1 to 6.4.2.

Release notes

Sourced from vite's releases.

v6.4.2

Please refer to CHANGELOG.md for details.

Changelog

Sourced from vite's changelog.

6.4.2 (2026-04-06)

Commits

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Apr 7, 2026
@dependabot dependabot Bot requested a review from a team as a code owner April 7, 2026 04:31
@github-actions github-actions Bot requested a review from roxanne-o April 7, 2026 04:31
Bumps [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) from 6.4.1 to 6.4.2.
- [Release notes](https://github.com/vitejs/vite/releases)
- [Changelog](https://github.com/vitejs/vite/blob/v6.4.2/packages/vite/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite/commits/v6.4.2/packages/vite)

---
updated-dependencies:
- dependency-name: vite
  dependency-version: 6.4.2
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot force-pushed the dependabot/npm_and_yarn/app/status_monitor/frontend/vite-6.4.2 branch from 74012ca to f97f2c0 Compare April 30, 2026 22:06
@dependabot @github

dependabot Bot commented on behalf of github Jun 14, 2026

Copy link
Copy Markdown
Contributor Author

Superseded by #429.

@dependabot dependabot Bot closed this Jun 14, 2026
@dependabot dependabot Bot deleted the dependabot/npm_and_yarn/app/status_monitor/frontend/vite-6.4.2 branch June 14, 2026 09:22
timmarkhuff pushed a commit that referenced this pull request Jun 23, 2026
Build the registry-switching seam now rather than deferring it. A chart-local
ecrRegistryMap keys the ECR image base (registry host plus optional repo prefix)
off upstreamEndpoint, the signal edge installs already provide, so no new install
argument is introduced. Two helpers consume it: ecrRegistry (full image base, for
the edge-endpoint and inference images) and ecrRegistryHost (host portion only, for
the registry-credentials pull secret docker-server, which keys on the host).

An explicit ecrRegistry value still overrides the map, and upstreams absent from
the map fall back to the prod (api.groundlight.ai) entry, so self-hosted installs
are unaffected.

No behavior change: the only map entry points at the GL_Public host, so the default
and fallback both render the byte-identical image strings as before. When the
dedicated Axon edge ECR accounts exist (aws-global #371), adding their host plus the
edge/ repo prefix (and jetson repo naming) to the map flips the switch as a data-only
change.

Co-authored-by: Cursor <cursoragent@cursor.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants