-
Recovery version 2026.7.2128
-
-
- Updated the
nrfutil sdk-managerbinary bundled with the extension to v1.15.0. - Fixed issues with the detection of LTS versions.
- Updated the
-
- Fixed an issue with starting toolchain installations multiple times.
-
-
- Updated the
nrfutil devicebinary bundled with the extension to v2.19.3.
- Updated the
-
General improvements
- Added board classification messages to build configuration and diagnostics. The messages are taken from the SDK and are valid from the nRF Connect SDK v3.4.0 onwards.
-
Bug fixes
- Fixed an issue with the Active Follow Editor feature.
- Fixed an issue with ignoring some child images for newer SDK versions.
-
-
Recovery version 2026.6.2060
-
Bug fixes
- Fixed an issue with an exception caused when using Action View actions (for example, Flash) with one or more devices that have no serial number. Such devices are now ignored and not available for those actions.
- Fixed an issue where
ZEPHYR_BASEhad to be a child oftopdir. It can now be its descendant.
-
-
General improvements
- With this release, we are moving away from using the nRF Connect for VS Code Extension Pack. The nRF Connect for VS Code extension will take the role of the extension pack moving forward: the three other extensions will now be installed by the main extension.
- Added URI handler to the main extension.
- Added Nordic MCP to the VS Code's tools list.
-
-
- Added support for Long Term Support (LTS) releases of the nRF Connect SDK. The LTS releases are now marked with the corresponding label and prioritized in SDK lists.
- Added command to reset cached data stored about SDKs.
- Added error handling of nRF Util's
sdk-managercommand errors when working offline.
-
- Fixed an issue with the duplicated filter button in the Install Toolchain quickpick.
-
- Changed the mechanism for handling the default application location and validating the chosen location when creating a new application.
-
-
-
Add/Edit Build Configuration page
- Added validation of CMake arguments.
- Added support for LTS releases in the Build Configuration page. This includes a warning if a build configuration is using an outdated LTS patch.
-
- Improved the color coding of the active application and active context by making them more prominent. Stale builds are deemphasized.
- Fixed an issue that would prevent creating multiple builds for the same application at the same time.
- Fixed an issue with the Build All Configurations for Application action.
- Fixed an issue with configuring sysbuild domains.
- Fixed an issue with shields not showing for custom SDKs.
- Fixed an issue with matching Zephyr module.
- Fixed an inconsistency in the build image context menu.
- Fixed an issue with regenerating build when a devicetree overlay is added.
-
-
- Added a notification when rebuilding a build context in case it has an SDK or toolchain missing.
- Changed the mechanism for providing Flash, Debug, and Memory report actions: they are now only available for build contexts that define them.
- Updated the build context pickers to be more consistent, with the active context now preselected in pickers.
- Updated the device pickers for flashing and debugging with the information about device compatibility with the active context.
-
- Fixed issues with the search bar and keyboard shortcuts in the Memory report section.
-
- Added color coding to indicate the device compatibility with the active context.
-
-
- Fixed issues with DAP requests when communicating with the debugger.
-
- Removed "nRF" from terminal name.
- Fixed issues with memory search input validation in the Memory Explorer.
-
-
Other improvements
- Fixed issues with some features only being available based on the nRF Connect SDK version instead of Zephyr's.
- Fixed issues with quick pick menus that would not close.