What's new?
- Manage published mods in the registry from the CLI, including their status and
description. For example
turbot registry modify --mod "@turbot/aws" --mod-version "5.0.0" --status RECOMMENDED --description "updated description". - Usually a newly published version should be the recommended one. So now you
can do that automatically during
turbot publishusing the--status RECOMMENDEDflag. turbot template buildnow supports instance root branch names with a random suffix, following the naming convention:wip/<instance root name>/*. We've found scheme much more effective at scale.- We now automatically include
RELEASE_NOTES.mdas well asCHANGELOG.mdwhen building a mod. Release notes are intended for users while a changelog is intended for developers or others obsessed over details. turbot testvalidates input query, but only works for a single query (not for the more advanced array of queries syntax). Previously the test would always fail for an array of queries, so we're now skipping the test in these cases until it can be fully supported.
Bug fixes
turbot publish --dir <mod folder>did not work if run outside the mod folder - the function zips were not correctly created.