Releases: bright/cloudform
Releases · bright/cloudform
3.2.1
3.2.0
3.1.0
Got rid of typescript
dependency from cloudform-types
package. Fixes #13 (thanks @DenSpirit!)
3.0.0
- Updated CloudFormationResourceSpecification.json to version 2.7.0
- Moved type definitions into a separate cloudform-types package for separate use use-cases (#13)
- Fixed an error when invoking CLI without parameters
This release is breaking only if you referenced any of the types via:
import Sth from 'cloudform/types/sth'
Types are now in cloudform-types
, so that import will now look like:
import Sth from 'cloudform-types/sth'
If you only import from cloudform
root space, there are no breaking changes for you.
2.3.0
2.2.1
- Option to minify the CLI output with
-m
or--minify
(#9) - Cross-regional support. Now the schemas for all the AWS Regions are merged together to ensure full coverage (#11)
- Fix for Windows issue in CLI (#7)
- Expose internal
Template
type to allow validation in client-side code (#8)
Thanks @fhewitt for your feedback!
2.1.0
2.0.1
Quick fix of previous release that was missing the TypeScript dependency.
2.0 changes:
- Definitions updated to the newest CloudFormationResourceSpecification.json – v2.0.0
- Now using ts-node when evaluating template file, so that splitting the template into separate files is actually possible as intended (thanks @sisisin for the contribution!)
- Breaking change: cloudform invocation must now be exported from the template with export default – see example in README.md
- npm package now doesn't contain actual TypeScript files (only transpiled JavaScript and TypeScript declarations), so that external compilation of the template is now possible independently of cloudform's tsc configuration
- Breaking change: if you imported transpiled JavaScript from cloudform/dist, switch to cloudform instead
- Breaking cleanup in naming: DataTypes is now DataType and DeletionPolicies is now DeletionPolicy
2.0.0
- Definitions updated to the newest CloudFormationResourceSpecification.json – v2.0.0
- Now using ts-node when evaluating template file, so that splitting the template into separate files is actually possible as intended (thanks @sisisin for the contribution!)
- Breaking change:
cloudform
invocation must now be exported from the template withexport default
– see example in README.md
- Breaking change:
- npm package now doesn't contain actual TypeScript files (only transpiled JavaScript and TypeScript declarations), so that external compilation of the template is now possible independently of cloudform's
tsc
configuration- Breaking change: if you imported transpiled JavaScript from
cloudform/dist
, switch tocloudform
instead
- Breaking change: if you imported transpiled JavaScript from
- Breaking cleanup in naming:
DataTypes
is nowDataType
andDeletionPolicies
is nowDeletionPolicy