Skip to content

fix(update-node): sync git submodules before source builds - #6

Merged
blu3chipsx merged 1 commit into
mainfrom
update-tn-contracts
Jul 24, 2026
Merged

fix(update-node): sync git submodules before source builds#6
blu3chipsx merged 1 commit into
mainfrom
update-tn-contracts

Conversation

@grantkee

Copy link
Copy Markdown
Contributor
  • detect updates for submodule

v0.12.0-adiri moved the tn-contracts submodule pointer and the new code
include_str!'s files that only exist in the new submodule commit. Both
source prepare paths (interactive + --json) did checkout + pull but never
git submodule update, so every source-build node died in cargo on a
missing deployments-*.json. Fresh installs were unaffected (setup-node.sh
already syncs).

- lib/common.sh v1.3.7: new tn_sync_submodules() -- submodule sync then
  update --init --recursive --force; callers pick hard-fail vs warn.
- update-node.sh v1.1.57: both prepare paths hard-fail with a clear
  message (and the manual one-liner) before any build or confirmation.
- ensure_chain_configs_available + edit-config.sh v1.2.4 chain-config
  refresh: warn-only sync (configs live in the superproject).
- ui/server.py v1.8.5: no UI change; bump redeploys the root-owned
  update engine in /opt/telcoin-ui-update/ so UI-driven updates get this.
- update-scripts.sh v1.1.64 release marker; sidecars regenerated;
  README changelog entry with the operator recovery command.

Recovery on an already-failed node: re-run the update (prepare now heals
the tree), or manually:
  sudo git -C /opt/telcoin-source submodule update --init --recursive --force

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@grantkee
grantkee requested a review from blu3chipsx July 24, 2026 17:37
@grantkee grantkee self-assigned this Jul 24, 2026
@blu3chipsx
blu3chipsx merged commit 2b08d1c into main Jul 24, 2026
6 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.

2 participants