etc breaking changes
hackage10 curated breaking changes across major versions of etc. Use this as a migration checklist before bumping dependencies.
- v0.3.2.0 \u2192 v0.4.0.0breaking
Add new `type` field to `etc/spec` with support for `string`, `number`, `bool`, `[string]`, `[number]` and `[bool]`, `[object]`
- v0.3.2.0 \u2192 v0.4.0.0breaking
Remove `type` field in `cli` spec in favor of `type` on `etc/spec`
- v0.3.2.0 \u2192 v0.4.0.0breaking
Allow ENV vars to accept supported types (only strings were allowed) (closes #30)
- v0.3.2.0 \u2192 v0.4.0.0breaking
Allow CLI options to accept supported types (only strings and numbers were allowed)
- v0.3.2.0 \u2192 v0.4.0.0breaking
Allow spec file to have array as default values
- v0.2.0.0 \u2192 v0.3.0.0breaking
Bump resolver to lts-11
- v0.2.0.0 \u2192 v0.3.0.0breaking
Replace `protolude` in favor of `rio`
- v0.2.0.0 \u2192 v0.3.0.0breaking
Update `parseConfigSpec` to no longer attempt to parse JSON when `yaml` cabal flag is set
- v0.2.0.0 \u2192 v0.3.0.0breaking
Add `sensitive` setting to `etc/spec` entries
- v0.2.0.0 \u2192 v0.3.0.0breaking
Add `Value` type to deal with sensitive values
Get this data programmatically \u2014 free, no authentication.
curl https://depscope.dev/api/breaking/hackage/etc