Yotta

Latest version: v0.20.5

Safety actively analyzes 630130 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 4 of 5

0.13.0

New Features
- New [`yotta shrinkwrap`](http://yottadocs.mbed.com/reference/commands.htmlyotta-shrinkwrap) command which can be used to peg the versions of dependencies (including indirect dependencies).
- `yotta outdated` will now display information about why updates are prevented.
- The `yotta ls --json` format is now intended to be stable, and can be consumed by other applications.
- If you publish a module or target which uses `-official` keywords (for example, `mbed-official`), yotta will check that's really what you meant to do.

Fixes and Under-The-Hood Improvements
- Improved CI setup now uses nose, and produces a JUnit description of failures
- many, many more tests for [`yotta test`](http://yottadocs.mbed.com/tutorial/testing.html), test runners, and test reporter scripts

0.12.2

- Fix several issues with custom CMake support (and now custom CMake support is better covered by yotta's test-suite) (Thanks to LiyouZhou and niklas-arm for the patch and bug reports!)

0.12.0

New Things
- YOTTA_MODULE_NAME definition now available to CMake and the preprocessor, handy for debug logging and many other things.
- Targets can now define "cmakeIncludes", cmake files which will be included in the build description for every module. This allows a deeper level of customisation for build targets, including applying the flags necessary to produce code coverage info. It should make it possible to remove some of the other special-case handling for post-processing build products, too.

Fixed Things
- Various fixes to Eclipse project generation (Thanks [BrunoPires](http://forums.mbed.com/t/support-for-eclipse-ide/861/13) on the forums for reporting problems!
- Fixed various crashes that could occur in the `yotta licenses`, `yotta link`, and `yotta outdated` subcommands (thanks bogdanm, 0xc0170 and markus-becker-tridonic-com for reporting!)
- Fix an issue handling the YOTTA_USER_SETTINGS_DIR environment variable (Thanks markus-becker-tridonic-com for reporting!)

0.11.0

New Features and Significant Fixes
- display information about where config values came from in the output of `yotta config` (use `yotta --plain config` to disable)
- support overriding config on the commandline (see [docs](http://yottadocs.mbed.com/reference/config.htmlcommandline-config) for details)
- Fix various issues with the --cmake-generator / -G parameter to `yotta build`: now Eclipse project files should include the source for the module being built. You can also use this to generate project files for [Sublime text, Codeblocks, and others](http://yottadocs.mbed.com/reference/commands.htmlyotta-build).

Behind the Scenes
- The wire-format for JWTs used by yotta to authenticate against the registry has changed (it now conforms to the standard). This change should have no visible effects, as the registry accepts both new and old formats. (Thanks headlessme!)
- Improved the way that command line options are shared between subcommands, making it easier to re-use them.
- Bump the version of the argcomplete dependency (thanks kylemanna!)

0.10.1

- Fix encoding problems with JWTs used for authentication with the registry. There still remains an issue with the encoding of the public key (see 614), but that needs a further registry update before it can be fixed in a backwards-compatible way.
- add --github option to `yotta login` (resolves 608)

0.10.0

- add `yotta unlink-target` subcommand to remove a linked target
- new yotta `unlink` and `unlink-target` support for unlinking globally linked modules/targets
- improved validation for `yotta link`
- bugfixes to the cache implementation
- fix linking failure of application tests if the application contains no source
- various documentation improvements (thanks Patater!)

Page 4 of 5

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.