Skip to content

cli: rename LIGATE_LGT_TOKEN_ID env var to LIGATE_AVOW_TOKEN_ID (post-#42 follow-up)#47

Merged
proofmancer merged 1 commit into
mainfrom
cli/avow-token-id-env-rename
May 26, 2026
Merged

cli: rename LIGATE_LGT_TOKEN_ID env var to LIGATE_AVOW_TOKEN_ID (post-#42 follow-up)#47
proofmancer merged 1 commit into
mainfrom
cli/avow-token-id-env-rename

Conversation

@proofmancer
Copy link
Copy Markdown
Member

@proofmancer proofmancer commented May 26, 2026

Summary

#42 renamed every LGT-prefixed identifier in this repo to AVOW (prose, base units, internal Rust idents, wire-deserialize fields) but missed the clap env = attribute on --token-id. This PR closes that gap.

Concrete: in src/transfer.rs and src/balance.rs, #[arg(long, env = "LIGATE_LGT_TOKEN_ID")]env = "LIGATE_AVOW_TOKEN_ID". README updated to match.

Breaking surface

Breaking on env-var name only. Operators who set export LIGATE_LGT_TOKEN_ID=token_1... in their shell rc need to rename the variable. No flag-name change, no wire-format change. The CLI's --token-id flag is unaffected.

CHANGELOG.md historical [0.2.2] section is intentionally NOT rewritten, LIGATE_LGT_TOKEN_ID was what shipped with v0.2.2; history stays accurate. New [Unreleased] entry documents the rename.

Test plan

  • Local cargo check + cargo fmt --check pass (pre-commit hook ran).
  • CI green on this PR.
  • Next cli release (v0.2.3 candidate) carries the rename + the [Unreleased] entry folds into the new version section.

@proofmancer proofmancer merged commit 456be09 into main May 26, 2026
5 checks passed
@github-actions github-actions Bot locked and limited conversation to collaborators May 26, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant