Skip to content

fix(deploy): esptool v5 non-deprecated argv spellings#79

Merged
zackees merged 1 commit intomainfrom
fix/issue-77-esptool-v5-argv
Apr 18, 2026
Merged

fix(deploy): esptool v5 non-deprecated argv spellings#79
zackees merged 1 commit intomainfrom
fix/issue-77-esptool-v5-argv

Conversation

@zackees
Copy link
Copy Markdown
Member

@zackees zackees commented Apr 17, 2026

Summary

Closes #77.

esptool v5 deprecated the underscored argv tokens used by fbuild deploy:

  • write_flash -> write-flash
  • --before default_reset -> --before default-reset
  • --after hard_reset -> --after hard-reset

Running a deploy today emits three deprecation warnings before proceeding. This PR updates the exact argv strings passed to esptool so deploys are warning-free on esptool v5.

Scope

  • crates/fbuild-deploy/src/esp32.rs: change the write_flash subcommand literal, test-fixture defaults (before_reset/after_reset), and the matching assertion. Also updated the /// --after hard_reset doc-comment literals that describe the effective CLI semantics.
  • crates/fbuild-build/src/esp32/configs/esp32*.json (9 files): update before_reset/after_reset values, since they flow directly into the --before/--after argv passed to esptool.
  • crates/fbuild-build/src/esp32/mcu_config.rs: update the doc-comment examples to match the new values.

Rust identifiers (before_reset, after_reset struct fields, build_write_flash_args function) are unchanged - this is a pure value/argv rename.

Test plan

  • ./_cargo test -p fbuild-deploy - 32 passed, 8 ignored (real-hardware tests)
  • ./_cargo clippy --workspace --all-targets -- -D warnings - clean
  • ./_cargo fmt --all - no changes
  • Manual: deploy to an ESP32 with esptool v5 installed and verify no deprecation warnings appear in the flash output.

Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com

esptool v5 deprecated the underscored argv tokens `write_flash`,
`default_reset`, and `hard_reset`, emitting a warning for each when
they are used. Switch the argv we pass to esptool (and the ESP32 MCU
JSON configs whose `before_reset`/`after_reset` values flow directly
into `--before`/`--after`) to the hyphenated spellings `write-flash`,
`default-reset`, `hard-reset` so deploys stay warning-free on v5.

Only string values consumed by esptool are changed; Rust field
names (`before_reset`, `after_reset`) and function names
(`build_write_flash_args`) remain unchanged.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 17, 2026

Warning

Rate limit exceeded

@zackees has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 1 minutes and 22 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 1 minutes and 22 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 980dc01c-c351-4950-ad1c-4e4b0294da0d

📥 Commits

Reviewing files that changed from the base of the PR and between f2d1590 and 2092ad9.

📒 Files selected for processing (11)
  • crates/fbuild-build/src/esp32/configs/esp32.json
  • crates/fbuild-build/src/esp32/configs/esp32c2.json
  • crates/fbuild-build/src/esp32/configs/esp32c3.json
  • crates/fbuild-build/src/esp32/configs/esp32c5.json
  • crates/fbuild-build/src/esp32/configs/esp32c6.json
  • crates/fbuild-build/src/esp32/configs/esp32h2.json
  • crates/fbuild-build/src/esp32/configs/esp32p4.json
  • crates/fbuild-build/src/esp32/configs/esp32s2.json
  • crates/fbuild-build/src/esp32/configs/esp32s3.json
  • crates/fbuild-build/src/esp32/mcu_config.rs
  • crates/fbuild-deploy/src/esp32.rs
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/issue-77-esptool-v5-argv

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@zackees zackees merged commit 41982b2 into main Apr 18, 2026
76 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.

bug(deploy): update ESP32 esptool argv to non-deprecated v5 spellings

1 participant