« Changelog History


Hasura v2.1.0-beta.1 Release Notes

    • server: Ignore unexpected fields in action responses (#5731)
    • server: add webhook transformations for Actions and EventTriggers
    • ⚡️ server: optimize SQL query generation with LIMITs
    • 🔀 server: add GraphQL request query in the payload for synchronous actions
    • 🌲 server: improve the event trigger logging on errors NOTE: This change introduces a breaking change, earlier when there was a client error when trying to process an event, then the status was reported as 1000. Now, the status 1000 has been removed and if any status was received by the graphql-engine from the webhook, the status of the invocation will be the same otherwise it will be NULL.
    • 👍 server: support extensions field in error responses from action webhook endpoints (fix #4001)
    • server: fix custom-check based permissions for MSSQL (#7429)
    • 🐎 server: query performance improvements
    • 🚚 server: remove identity notion for table columns (fix #7557)
    • 👍 server: support MSSQL transactions
    • 🌲 server: log individual operation details in the http-log during a batch graphQL query execution
    • ⏱ server: update create_scheduled_event API to return event_id in response
    • 📇 server: fix bug which allowed inconsistent metadata to exist after the replace_metadata API even though allow_inconsistent_object is set to false.
    • server: fix explicit null values not allowed in nested object relationship inserts (#7484)
    • server: introspect_remote_schema API now returns original remote schema instead of customized schema
    • server: prevent empty subscription roots in the schema (#6898)
    • 👍 server: support database-to-database joins (for now, limited to Postgres as the target side of the join)
    • 👍 server: add support for user comments for trackable functions (#7490)
    • 👍 console: support tracking of functions with return a single row
    • console: add GraphQL customisation under Remote schema edit tab
    • console: fix cross-schema array relationship suggestions
    • 🐎 console: add performance fixes for handle large db schemas
    • 🏗 console: fix missing cross-schema computed fields in permission builder
    • 🔒 console: add time limits setting to security settings
    • 📇 cli: add support for network metadata object
    • cli: hasura migrate apply --all-databases will return a non zero exit code if operation failed on atleast one database (#7499)
    • cli: migrate create --from-server creates the migration and marks it as applied on the server
    • 📇 cli: support query_tags in metadata
    • 🚀 cli: add hasura deploy command
    • 📇 cli: allow exporting and applying metadata from yaml/json files
    • cli: allow squashing specific set of migrations. A new --to flag is introduced in migrate squash command. eg: hasura migrate squash --from <v1> --to <v4>
    • 📇 cli: hasura init --endpoint <endpoint> adds an option to export metadata and create initial migration from the server.