Skip to content

v2.6.0
Compare
Choose a tag to compare
@andreriesco andreriesco released this 30 Aug 21:07
· 78 commits to bookworm since this release
v2.6.0
4d76678
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

Release Notes

  • dotnetUno and dotnetUnoFrameBuffer deprecated due to the upcoming EOL of .NET 6 (Replaced by dotnetUno5 and dotnetUno5FrameBuffer templates, which use .NET 8.0;
  • pre-cleanup: docker-compose down now only stops the application container, but doesn't stop the dependencies containers (like weston for example), speeding up the debugging pipeline;
  • COPY of application's source code and executables on Dockerfile.debug was replaced with an rsync task, removing the need of decompressing this layer on the board (as Docker push and pull don't have the option to not use compression even on private/local registries) and therefore also speeding up the debugging pipeline;
  • tasks presentation: The presentation of the tasks was improved, adding more appropriate symbols and colors for each task, and grouping tasks that make sense to be in the same terminal. This improves the visualization of each task output on the terminal console, and also in cases where there is a pipeline of tasks being executed is sequence, like in the build and run pipelines (both debug and production/release), with all the outputs showing in sequence in the same terminal;
  • python3: Add a task that creates a venv when the project is opened on the workspace;
  • try-update-template task: Fixed missing files on the updates;
  • multi-containers: Updated the settings, launch and tasks to be on the .code-workspace file, as recommended by VSCode for multiroot workspaces;
  • multi-containers: Added a script to check for debug port and wait_sync (setting which handles race conditions) conflicts and fix this conflicts, avoiding conflicts between the single projects during execution on a multi-container environment;
  • base containers: Change from torizon base containers to commontorizon ones. It is important to highlight that the base of this commontorizon containers are still the torizon 3 stable ones, therefore still guaranteeing the quality and stability of torizon containers. This was done to standardize the names and tags of base containers (which avoids adding edge cases for the base containers on the IDE templates, which support multiple boards, can be used with all Toradex's board and even commontorizon supported boards like Raspberry PI, and multiple architectures), and also to add support for x86 where needed. Also, commontorizon has extra containers used within the IDE templates, like the mono, xfce and Slint containers;
  • Slint: Bump to Slint 1.7.2 and switch for winit-wayland to Linuxkms backend;
  • tcb: Fixes on tcb template and also add the possibility to use it on Github Actions in a docker-in-docker configuration;
  • tcb: Added initial documentation on tcb/.doc/README.md, with some informations about the template, it's current status and how to use it;
  • TCB: Bump to TCB version to 3.11 on all templates;
  • Adding packages to Dockerfiles: Parameters names updated on torizonPackages.json and also added buildDeps parameter, separating build/compilation and runtime dependencies. Also fixed auto-completion in the file and issue adding packages with target architecture;
  • tests: Bump vscode-extension-tester and ran automated tests on all templates (including the Community Supported ones), against the latest VSCode version (1.92.2);
  • show-documentation: Fixed it showing also a tab in plain markdown text;
  • settings: debug_port updated to debug_port1 for standardization;
  • Other minor fixes and improvements;
  • Experimental: x86_64 support was added on all templates;

Full Changelog: v2.5.2...v2.6.0

😍 Special Thanks : 😍

Thanks to all our contributors!

In this release, we had contributions from:

@tronical
@dk-coligo

Contributors

tronical
Assets 2
Loading