Skip to content

fix(bedrock): interim default gen-0/warn until v2 producer ships - #153

Merged
minekube-ai-engineer[bot] merged 1 commit into
mainfrom
bedrock-v2-trackB-interim-default
Aug 24, 2026
Merged

fix(bedrock): interim default gen-0/warn until v2 producer ships#153
minekube-ai-engineer[bot] merged 1 commit into
mainfrom
bedrock-v2-trackB-interim-default

Conversation

@minekube-ai-engineer

Copy link
Copy Markdown

Source: Discord ask-support thread — the exact thread the report came from (myrixx/foxof7207, Aug 22).

What this fixes

connect-java 0.15.7/0.15.8 ship a gen-2 mode: require default for bedrock-principal with public-keys: {} — but the moxy producer side of the frozen v2 contract was never completed (metadata 404 + no signed envelopes), so every fresh Bedrock join is rejected with BedrockPrincipalAdmissionException / READINESS (see kanban t_87f2966f).

Track B (interim unblock)

Change the shipped default to config-generation: 0 + mode: warn so fresh installs keep working on the already-working v1 identity path until the v2 producer ships (Track A: moxy routing + signing config + CF worker proxy, tracked separately).

  • core/src/main/resources/config.yml + proxy-config.yml: default gen 0 / warn
  • Test renamed/updated: newlyGeneratedServerAndProxyConfigsDefaultToV2WarnUntilProducerShips
  • Existing gen-2 configs (0.15.7/0.15.8) are unaffected on disk; they keep require until the user regenerates/upgrades (product decision approved by Robin 2026-08-22).

Fixes the READINESS rejection for fresh installs of the CURRENT public release.

@minekube-ai-engineer
minekube-ai-engineer Bot merged commit 7dcf9c7 into main Aug 24, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants