Releases

Release notes describe changes that reached a public release and explain their user impact. Roadmap items, source-code presence, and preview work are not release facts.

Each release entry links to the exact SenCore release, Device Operation contract, SenCLI version, affected workflows, and a summary of meaningful changes.

How to read a release

A release page is useful only when it answers three questions: what public capability changed, which release contains the change, and which user workflow needs attention. SenCore, Device Operation, and SenCLI changes are tied to explicit product versions. Component changes are described by their user-visible effect.

The page should distinguish additions, behavior changes, deprecations, and removals. A new entity is not automatically compatible with every board or application. Follow the compatibility and lifecycle fields on the corresponding Reference page, then rebuild or reselect the project artifact when the release gate requires it.

Before adopting a release

Read the change summary, review the affected workflow pages, and run the documented smoke path with the exact Web or CLI executor. Keep the previous release identity in the project record until the new artifact has passed device verification. If a release is marked Preview, do not use it as the production default.