Breaking change and major version bump
This action used to create an empty config file if none was found. This implicitly assumes the Hasura config v1 is used as the CLI will consider v1 if no version is specified. This could break some builds in an unexpected manner. So we have chosen to force users to provide a config file specifying the version their project use. We believe this makes the action more predictable now that the Hasura CLI supports 3 different and non-compatible versions of the config. Please reach out if you have a better idea on how to handle this.
Fixes
This release fixes issue #15 and makes sure that externally sourced secrets are not printed to the console.
Changes
We now skip update checks, which results in less confusing logs.