Jay Fitzgerald

>NI-Digital now supports multi-instrument sessions which handles the NI-Sync driver internally. This is the recommended usage. So we won't add `niDigital_EnableMatchFailCombination` to `nidigital` anymore. It's actually NI-TClk that's handled internally...

Note that this function still wouldn't be useful without a way to open an NI-Sync session, so it will remain unplanned, for now.

This would need to be balanced with a change to our release process to include periodically updating dependencies to tackle accumulated tech debt.

If you have an issue, please add a description. If you simply have a question, I'd recommend https://github.com/ni/nimi-python/discussions/categories/q-a, instead.

Examples could test this, if they had their own venv without grpcio and protobuf installed.

Alternatives to consider: 1. Stick with the Unified CHANGELOG and leave version out of the overall section heading (grouping releases by date) moving forward, but include release version in heading...

> What happens with CHANGELOG.md in the root directory? If we don't choose one of the alternatives, I'll delete it as part of this change.