Skip to content

feat(config): wire --bzz-token-address through bee config#592

Open
martinconic wants to merge 2 commits into
masterfrom
feat/bzz-token-address
Open

feat(config): wire --bzz-token-address through bee config#592
martinconic wants to merge 2 commits into
masterfrom
feat/bzz-token-address

Conversation

@martinconic
Copy link
Copy Markdown
Contributor

Bee PR #5476 (refactor: add BzzAddress to ChainConfig) makes the BZZ token address strict: known networks resolve it from the static config, unknown networks must supply --bzz-token-address. The local CI chain is neither mainnet nor testnet, so bee refuses to start without it.

Add BzzTokenAddress to orchestration.Config / BeeConfig, render it in the k8s template, and set the bee-localchain BZZ token address in the local-chain cluster configs (already used by beekeeper itself in beekeeper-local.yaml). Bee versions without #5476 ignore the new key (viper silently drops unknown keys), so this lands safely ahead of the bee merge.

dependabot Bot and others added 2 commits May 27, 2026 19:10
…590)

Bumps [github.com/go-git/go-git/v5](https://github.com/go-git/go-git) from 5.19.0 to 5.19.1.
- [Release notes](https://github.com/go-git/go-git/releases)
- [Changelog](https://github.com/go-git/go-git/blob/main/HISTORY.md)
- [Commits](go-git/go-git@v5.19.0...v5.19.1)

---
updated-dependencies:
- dependency-name: github.com/go-git/go-git/v5
  dependency-version: 5.19.1
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
@martinconic martinconic force-pushed the feat/bzz-token-address branch from eef2389 to 6d6ea64 Compare May 27, 2026 16:12
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.

1 participant