Releases: exograph/exograph
Releases · exograph/exograph
v0.8.2
v0.8.1
Highlights
- Support average aggregate for the 'Vector' type #1050
- Support retrieving distance support in the queries for the
Vector
type #1052 - Fix predicate formation for
null
operand #1051 - Add the GraphiQL Explorer plugin #1049
Internal improvements
- Upgrade to Rust 1.77.1 #1045
- Remove the Xcode override from the CI workflow #1048
- Upgrade Docusaurus to 3.2.1 #1054
Full Changelog: v0.8.0...v0.8.1
v0.8.0
Highlights
- Support for embeddings using pgvector 🎉 #1042
Internal improvement
Full Changelog: v0.7.2...v0.8.0
v0.7.2
Highlights
- Update Deno to 1.41.3 #1031, #1034, and #1038
- Fix primitive
Ordering
wrapping in an array (this is a backwards compatible change, since the array version in earlier versions issued an error during resolution) #1033 - Improve the docs for using external packages with Deno #1025
Internal improvements
- Upgrade various packages #1023, #1024, #1028, and #1029, #1030
- Switch to vite (from react-script) to build playground #1026
- Prevent failures when installing dependencies of Postgres on macos-13 in CI #1027
- Fix CI build for AWS #1032
- Fix release script #1035
- Separate DEVELOPMENT.md from README.md #1037
Full Changelog: v0.7.0...v0.7.2
v0.7.0
Highlights
- Support trusted documents (also called persisted queries or persisted documents). Please see https://exograph.dev/docs/production/trusted-documents for more details 🎉 #1015
Internal changes
- Switch to macos-13 to build the x86 target #1020
- Use macos-14 runner for GitHub actions #1012
- Upgrade to Rust 1.76 #1013
Documentation improvements
- Document unique queries #1010
- Document types for Exograph and ExographPriv #1011
- Document using external npm packages #1014
- Upgrade Docusaurus to 3.1.0 #1009
Full Changelog: v0.6.0...v0.7.0
v0.6.0
Highlights
- Support queries by unique fields. For example, Exograph will now define queries such as
userByEmail
ifemail
is marked as@unique
#1005
Breaking change
The id queries (such as user
or concert
) now return an optional value. For example, instead of the earlier user(id: Int!): User!
, the new query is user(id: Int!): User
. The behavior itself remains unchanged, but the signature now correctly reflects it. This might affect clients in typed languages, and fixing them will require guarding against possibly null/undefined return values.
Internal improvements
- Fix an issue with the npm module integration test #1006
- Fix the syntax used for sed in release script #1007
Full Changelog: v0.5.4...v0.6.0
v0.5.4
Highlights
- Fix
ExographError
usage error #998 (thanks @affanshahid) - Improve typing for query execution #1000 (thanks @affanshahid)
- Switch the base image for AWS Lambda to
amazonlinux:2023
#994 - Fix the persistence of headers in playground #999
- Use type name as the namespace for unique constraint names #1001
- Allow update mutations to pass
null
for optional relations #1002 - Use the same format for integration tests as that of exotest to allow multi-operation initialization #992
Internal improvements
- Add to test to ensure multi-mutation transactions #990
- Refactor integration testing code #993
- Upgrade dependent action versions in CI #995
- Upgrade async-graphql in preparation for using
@oneOf
#996 - Exclude ExographError from generated imports #1003
New Contributors
- @affanshahid made their first contribution in #998
Full Changelog: v0.5.3...v0.5.4
v0.5.3
Fixes
- Ignore index set due to unique constraint. This fixes a migration error for fields with
@unique
constraint #988
Full Changelog: v0.5.2...v0.5.3
v0.5.2
Highlights
- Consider only non-pk columns during migration. This fixes migrations from the older pre-
@index
style schema #986 - Unset EXO_* envs before running integration tests to make it deterministic and fix an issue when
EXO_OIDC_URL
is defined #984 - Make Postgres error messages opaque #985
Full Changelog: v0.5.1...v0.5.2
v0.5.1
Highlights
Full Changelog: v0.5.0...v0.5.1