v2.46.0-beta.1
📦 hasura-authView on GitHub →
✨ 1 features🐛 7 fixes🔧 3 symbols
Summary
This release focuses on bug fixes, particularly around Postgres JSON handling in event triggers and metadata consistency. It also introduces an option to run SQL outside transactions and improves resource utilization in containerized environments.
✨ New Features
- Add optional `no_transaction` flag (default `false`) to `run_sql` API (Postgres) to execute SQL statements outside transaction blocks, with support for splitting multiple statements. Useful for operations like `CREATE INDEX CONCURRENTLY`.
🐛 Bug Fixes
- Fix an issue where Postgres reset JSON parameters to empty strings after a transaction, causing event trigger failures when executing mutations outside Hasura. The `insert_event_log` trigger function now correctly handles empty strings.
- Attempt to set Haskell runtime threads based on cgroup CPU limits, when present, for better automatic sizing in Docker and Kubernetes environments.
- Fix an issue where a source's metadata would be erased if the source was inconsistent and then a source update was performed.
- Mark remote schemas as inconsistent when type conflicts occur with the existing schema.
- Only show internal actions errors in logs if `HASURA_GRAPHQL_DEV_MODE` or `HASURA_GRAPHQL_ADMIN_INTERNAL_ERRORS` are switched on.
- Fix the `hasura_active_subscriptions` metric becoming inconsistent (e.g. showing a negative value). _(Cloud / Enterprise edition only)_
- Fix metrics label for DB with non-standard URI. _(Cloud / Enterprise edition only)_
🔧 Affected Symbols
run_sql API (Postgres)insert_event_log trigger functionhasura_active_subscriptions metric