chore(deps): bump next from 16.2.4 to 16.2.6 in /frontend in the npm_and_yarn group across 1 directory - #1
Open
dependabot[bot] wants to merge 1 commit into
Conversation
dependabot
Bot
added
dependencies
Bumps the npm_and_yarn group with 1 update in the /frontend directory: [next](https://github.com/vercel/next.js). Updates `next` from 16.2.4 to 16.2.6 - [Release notes](https://github.com/vercel/next.js/releases) - [Changelog](https://github.com/vercel/next.js/blob/canary/release.js) - [Commits](vercel/next.js@v16.2.4...v16.2.6) --- updated-dependencies: - dependency-name: next dependency-version: 16.2.6 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
changed the title
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/frontend/npm_and_yarn-152f59e559
branch
from
May 29, 2026 12:30
f2b1de9 to
dcb163d
Compare
keksmd
added a commit
that referenced
this pull request
Jul 10, 2026
…isable cluster discovery by default Resources become visible in the console purely from the two git paths, where project+env come from the git PATH — so a resource can never surface in a project it wasn't committed under. This closes the isolation gap of the cluster-wide discover() pass, which mirrored EVERY platform CR on the cluster into snapshots and fell back to attributing orphans to `platform` (a leakage risk). - restore chart-template indexing (reverts the earlier revert): the git-watcher now scans both apps/<app>/resources.values.yaml AND apps/<app>/chart/templates/*.yaml. Needed because most buckets and many DBs are helm-chart-authored (audit of argo-infra console-migration: S3Bucket 0 in resources.values.yaml vs 5 chart templates; ServiceDatabaseV2 3 vs 6) — path #1 alone never saw them, which is why discovery was leaned on. - gate the reconciler's discover() pass behind GITOPS_CLUSTER_DISCOVERY_ENABLED (default false). reconcile()/reconcileModels() still run — live App/AIModel phase updates only touch existing rows, no leakage. No snapshots are deleted; disabling discovery just stops cluster-sourced creation. go build + go test ./... green. Needs a gitops-agent image rollout. Caveat: existing discovery-sourced snapshots (63: incl 12 ServiceDatabaseV2, 37 PublicApi) persist but their phase stops refreshing once discovery is off; any that are genuinely cluster-only (rough audit shows ~11 PublicApi may lack a git manifest) won't get NEW snapshots — verify git coverage before rollout, or set GITOPS_CLUSTER_DISCOVERY_ENABLED=true to fall back.
keksmd
added a commit
that referenced
this pull request
Jul 13, 2026
#5/#8 extensions Correct the #1 root cause (user-service is broker-free; rabbitmq unused, HTTP not AMQP — the broker theory was stale). Record the durable name-uniqueness fix (#2: per-project + spec.argoName) and the additional #4/#5/#8 sites the first sweep missed. Remove the duplicate registry file created this session.
keksmd
added a commit
that referenced
this pull request
Jul 13, 2026
…s hang (personal orgs), not rabbitmq
keksmd
added a commit
that referenced
this pull request
Jul 13, 2026
…re evidence; retract hang theory (invalid probe)
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 npm_and_yarn group with 1 update in the /frontend directory: next.
Updates
nextfrom 16.2.4 to 16.2.6Release notes
Sourced from next's releases.
... (truncated)
Commits
ee6e79bv16.2.6afa053dTurbopack: Match proxy matchers with webpack implementation (#93594)97a154eTurbopack: Fix middleware matcher suffix (#93590)83899bc[backport] Disable build caches for production/staging/force-preview deploys ...7b222b9[backport][test] Pin package manager to patch versions (#93595)a8dc24f[backport] Turbopack: more strict vergen setup (#93587)766148fv16.2.50dd9483fix: add explicit checks for RSC header (#83) (#98)d166096fix proxy matching for segment prefetch URLs (#89) (#96)9d50c0bStrip next-resume header from incoming requests (#92)Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for next since your current version.