Releases: tibotiber/hasura-action
v3.0
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.
v2.1
This release fixes issue #13 by setting a fix version of the base docker image used. This is following the latest update to alpine-glibc, which seems to have broken the symbolic linking in libstdc++.
v2.0
Breaking change
We're going for 2.0 as the default behaviour has now changed. The default version of the CLI used to be stable, it now tries to get the version from the endpoint and use that. It falls back on stable if it fails to get the version from the endpoint. Thanks to @dbellotti for his PR that "syncs the cli with target hasura engine version" (#11).
Contributors
Assets 2
v1.5
Features
- Add environment variable to choose the CLI version (#9)
v1.4
Bug fixes
- Fix issue with special characters in password (#8)
v1.3
v1.2
v1.1
Second release came fast 😅.
Bug fixes
- Rename
action.yamlintoaction.ymlso GitHub lets me publish this.
v1.0
This is the first release of this action.
The code is based on the successful GitHub Action for Firebase.
Features
- Run any command using the Hasura CLI.
- Use environment variables to pass in a custom directory to find your Hasura working directory.
- Use environment variables to pass in your endpoint and (optional) admin secret via repository secret.