This change declares a new major release of the CLI (4.0.0) incorporating a new release of the deployer (4.2.0). There are three changes.
The status directory generated by the deployer in the base of a deployed project is now called .deployed rather than .nimbella. This change is backward compatible for the most part in that both .nimbella and .deployed continue to be ignored by the deployer during project reading. However, only .deployed will be generated and only deployed will be re-read during incremental deploys, so there can be a one-time hiccup in incremental deployment where the entire project is deployed.
The parsing of project.yml now accepts both functions and actions where only actions was accepted before. This is also a backwards-compatible change (actions continues to be accepted).
The generation of a project configuration output, both in nim project create and nim project get-metadata, will use functions rather than actions. This is a breaking change for tools that expect to parse the get-metadata output.
This change declares a new major release of the CLI (4.0.0) incorporating a new release of the deployer (4.2.0). There are three changes.
.deployedrather than.nimbella. This change is backward compatible for the most part in that both.nimbellaand.deployedcontinue to be ignored by the deployer during project reading. However, only.deployedwill be generated and onlydeployedwill be re-read during incremental deploys, so there can be a one-time hiccup in incremental deployment where the entire project is deployed.project.ymlnow accepts bothfunctionsandactionswhere onlyactionswas accepted before. This is also a backwards-compatible change (actionscontinues to be accepted).nim project createandnim project get-metadata, will usefunctionsrather thanactions. This is a breaking change for tools that expect to parse theget-metadataoutput.