cfcli च्या जुन्या आवृत्त्या डाउनलोड करा

This release writes a lighthouse configuration file straight to a swarm.

### New features

• **Lighthouse configuration files for a swarm** — `swarm lh write` and
`swarm lh check` take a YAML file with `-i/--input`, as `lh config write -i`
and `lh config check -i` do for one Crazyflie. The file is used instead of
the stored configuration the swarm names, for example one from
`lh config read` or the Crazyflie client. `write` skips the Crazyflies that
already have it, as before. See
[docs/swarm.md](docs/swarm.md#lighthouse).
([#42](https://github.com/bitcraze/cfcli/issues/42))

```text
$ cfcli swarm lh write -i my_setup.yaml
Lighthouse config from my_setup.yaml：base stations 4, 5, 6, 7
CF-05：written and stored in flash
CF-06：up to date
```

### Improvements

• **`swarm lh` loads the configuration first** — a missing or broken file, or
an unknown stored configuration, fails at once, before any Crazyradio is
opened.
• **`swarm lh check` suggests the right `write`** — when Crazyflies differ, the
`swarm lh write` it suggests includes the `--config` or `-i` that was given.
It used to suggest plain `swarm lh write`, which writes the configuration
the swarm names.

This release is mostly about swarms. cfcli can now store lists of Crazyflies,
run commands on all of them at once, and share swarms and lighthouse
configurations with the people you fly with.

### New features

• **Swarms** — a swarm is a named list of Crazyflies, each with a short name,
stored in the same YAML format as
[Swarmkeeper](https://github.com/evoggy/swarmkeeper) so a file can move
between the two. `swarm config` manages them (`list`, `select`, `create`,
`delete`, `show`, `name`, `add`, `remove`, `rename`, `import`, `export`,
`move`), `swarm scan` shows which Crazyflies answer, and
`select --from-swarm CF-02` selects one of them for all the other commands.
See [docs/swarm.md](docs/swarm.md).

```text
$ cfcli swarm config import ~/Documents/Swarmkeeper/swarms/lab.yaml
Imported swarm 'lab' from …/lab.yaml (3 Crazyflies), 3 URIs now use radio:/// (any Crazyradio)
Selected swarm 'lab' (3 Crazyflies)
$ cfcli swarm scan
CF | URI | Radio | Online
------+---------------------------+-------+--------
CF-01 | radio:///80/2M/E7E7E7E701 | 1 | yes
CF-02 | radio:///90/2M/ABAD1DEA01 | 0 | yes
CF-03 | radio:///90/2M/ABAD1DEA02 | 0 | yes
3 of 3 Crazyflies answered
```

`swarm config add` takes URIs, `--scan`, or `--from-usb` (the one
USB-attached Crazyflie), and asks for a name when a single Crazyflie is added.
Swarm IDs and Crazyflie names complete in bash, zsh and PowerShell.

• **Any Crazyradio：`radio:///`** — a URI with the radio left empty means "any
Crazyradio". A single Crazyflie gets the first Crazyradio that can be opened,
so cfcli keeps working while another program holds radio 0. A swarm is spread
over all attached Crazyradios, and Crazyflies on the same channel, or on
channels less than 2 apart, always share one, so two radios never transmit on
the same channel. `radio://0/` is rewritten to `radio:///` when Crazyflies are
imported or added to a swarm; other radio indices are kept.

• **Commands on a whole swarm** — these run on every Crazyflie in the selected
swarm, or on the ones picked with `--cf`, `--exclude` or `--swarm`:

| Command | |
|---|---|
| `swarm platform info \| reboot \| power-off \| sleep \| wakeup` | |
| `swarm param get \| set \| store \| clear` | without names, the parameters are picked from the first Crazyflie |
| `swarm log print` | streaming, or one row per Crazyflie with `--once` |
| `swarm deck list`, `swarm debug assert` | |
| `swarm bootload info \| flash` | see below |
| `swarm rechannel` | see below |
| `swarm lh check \| write` | see below |

Listings look like the normal ones with a `CF` column in front, and `--csv`
rows start with `cf,uri`. A Crazyflie that fails doesn't stop the others; its
error goes to stderr with its name in front. The exit code is 0 when all
succeed, the usual code when all fail the same way (10 when none answer), and
the new **50** otherwise.

```text
$ cfcli swarm platform info
CF | Platform | Firmware | CRTP protocol
------+-------------------------+-------------+---------------
CF-BS | Crazyflie 2.1 Brushless | 2026.08 +84 | 13
CF-01 | Crazyflie 2.1 Brushless | 2026.08 | 12
CF-02 | Crazyflie 2.1 Brushless | 2026.08 | 12
```

Each Crazyradio talks to up to 8 Crazyflies at a time, and log and parameter
TOCs are downloaded once per firmware instead of once per Crazyflie (3.2 s
cold and 0.6 s warm for `swarm platform info` on 3 Crazyflies).

• **Flashing a swarm** — `swarm bootload flash` takes the same `--release`,
`--zip`, `--bin` and `--targets` as `bootload flash` and flashes the
Crazyflies one after another, with a summary table at the end. A release is
downloaded for each platform in the swarm, and everything is prepared before
the first Crazyflie is touched, so a wrong `--zip` stops the command instead of
failing halfway. STM32 and nRF51 images given with `--bin` are only flashed
when all the Crazyflies have the same platform; `--platform` flashes one
platform at a time in a mixed swarm.

`swarm bootload info` shows the bootloader versions of each Crazyflie and
re

### New features

• **Listing the attached decks** — the new `deck list` command prints one line per
attached expansion deck with its board name, board revision and serial number.
See [docs/deck.md](docs/deck.md).

```text
Name | Rev | Serial
---------------+-----+--------------------------
bcFlow2 | A | 0DD07B8E0000002D
WiFi camera de | G | 7E0048001250465753393020
```

Both kinds of deck identity memory are covered：`OneWire` decks, where the
serial is the 1-wire ROM id, and `DeckCtrl` decks, where the name and revision
come from the info page and the serial is the deck controller's CPU id. The
serial is reported together with the memory listing, so a deck whose memory
can't be read — a 1-wire memory failing its CRC check, for instance — is still
listed with its serial and `?` in the fields that could not be read, with the
reason on stderr. `--csv` gives machine-readable output. A deck with no
identity memory at all is not listed, since the Crazyflie has no way of knowing
it is there.

• **Verifying memory contents** — `mem verify` takes the same arguments as
`mem write`, but reads the memory back and compares it against the data you
give it, so a write can be confirmed:

```bash
cfcli mem verify DeckMemory -s 0x10000000 -i color-led.bin
```

The number of bytes read back is the length of the expected data, so the same
`--data`/`--input` that wrote a region verifies exactly that region. A match
prints a confirmation and exits **0**; otherwise the differing bytes are listed
with their absolute offsets and the command exits **1**, so a script can act on
it:

```text
Offset | Expected | Actual
-----------+----------+--------
0x00000004 | 0xFF | 0x00
0x00000005 | 0xBD | 0xBC
Error：Verify FAILED: 2 of 32 bytes differ
```

At most 16 differing bytes are listed, the rest are summarised as
`... and N more`. See [docs/memory.md](docs/memory.md).

### Bug fixes

• **Flashing no longer fails on a deck that is already up to date** — the
Lighthouse deck cannot be commanded into its bootloader, and the firmware only
leaves it there while its bitstream is out of date. A running deck is therefore
already up to date, and is now skipped instead of failing the whole flash run.
The Crazyflie is only restarted if something was actually written.
([#6](https://github.com/bitcraze/cfcli/issues/6))

### Improvements

• **Consistent table output** — `param list`/`get`, `log list`, `mem list`,
`loco display` and the new `deck list` now build their tables with
[tabled](https://crates.io/crates/tabled), so columns are sized to fit their
contents instead of being padded to a fixed width. A name longer than the old
fixed width no longer pushes the rest of the row out of alignment, a set of
short names no longer leaves a wide gap before the next column, and numeric
columns are right-aligned. Note that `mem list` changes shape as
part of this — it prints an `ID | Type | Size | Serial` table rather than one
formatted line per memory, so anything parsing that output should use `--csv`,
which is unchanged.

• **Warning when a deck product name is too long** — the product name in the
DeckCtrl info page is stored in a 15 byte field, so `util deck-ctrl bingen`
and `binflash` now warn on stderr when the name in the YAML configuration does
not fit and say how it will be stored. The configuration is still written, so a
name that was already flashed keeps working.

• **Arming moved to the supervisor subsystem** — `hlc arm`/`hlc disarm` now use
the supervisor API in crazyflie-lib, replacing a method deprecated in 0.8.2.
No change in behaviour.

• **crazyflie-link and crazyradio are used through crazyflie-lib** — both are
re-exported by crazyflie-lib, so the exact versions it was built against are
reachable as `crazyflie_lib::crazyflie_link` and no longer have to be direct
dependencies kept manually in sync. `packet_capture` is enabled through the
crazyflie-lib passthrough feature, still on Unix targets only. Internal change,
no difference in behaviour.

## What's Changed
• Added Flow 3.0 target

**Full Changelog**：https://github.com/bitcraze/cfcli/compare/0.12.0...0.13.0

## What's Changed
* Infer flash target for single bare bin by @ataffanel in https://github.com/bitcraze/cfcli/pull/10
* LH data in permanent storage by @ArisMorgens in https://github.com/bitcraze/cfcli/pull/11

## New Contributors
* @ArisMorgens made their first contribution in https://github.com/bitcraze/cfcli/pull/11

**Full Changelog**: https://github.com/bitcraze/cfcli/compare/0.11.1...0.12.0

Updated release scripts to check that tag matches the Cargo.toml version. Otherwise same as https://github.com/evoggy/cfcli/releases/tag/0.7.0

New features
- Added option for flashing binaries to a specific address/page offset
- Print more bootloader info during flash operations
Bug fixes
- Fixed missing console output
- Fixed issue with bootloader URI and timeout parameter

Initial windows release