SDK
SDK 0.15.0
cms.getTaxonomy({ key, region })takes a region, by key or short code such asgermanyorde, as the other calls do. Terms hidden in that region are left out, and labels the region has of its own win over the language's. Withoutregionthe space's first region is used, so terms hidden there are left out too. The answer carriesregion, the region the labels follow, ornullwhen the space has none. A language without its own label now falls back along the region's language fallbacks before the default label.- The mirror keeps taxonomies per region as well, so
getTaxonomywithregionis answered from it when CMS Orbit can't be reached. npx cms-orbit import <file>imports entries, files, references, translations and redirects from an import file with a management token (ORBIT_TOKEN,ORBIT_ORGANISATIONandORBIT_SPACE).--dry-runchecks every entry against the schema, every file's address and the redirects without changing anything, and--publishpublishes once imported. Each entry's key is kept as its external ID, so running it again updates what it made, with no state file. See Import content with the Management API.npx cms-orbit promote --from staging --to production --region <key> --locale <code>publishes every published entry of a language, or of one folder with--folder, in another environment, with its redirects.--dry-runshows what would change.