payloadcms

Files

Paul 5368440115 chore: fix jest global teardown incorrectly always returning process exit status 0 (#12907 )

We were running scripts as they were without encompassing our logic in a
function for jest's teardown and we were subsequently running
`process.exit(0)` which meant that tests didn't correctly return an
error status code when they failed in CI.

The following tests have been skipped as well:
```
  ● postgres vector custom column › should add a vector column and query it
  ● Sort › Local API › Orderable › should not break with existing base 62 digits
  ● Sort › Local API › Orderable join › should set order by default
  ● Sort › Local API › Orderable join › should allow setting the order with the local API
  ● Sort › Local API › Orderable join › should sort join docs in the correct
```

---------

Co-authored-by: Elliot DeNolf <denolfe@gmail.com>
Co-authored-by: Alessio Gravili <alessio@gravili.de>

2025-06-25 17:43:57 -07:00

collections

fix(ui): reordering with a join field inside a group (#12803 )

2025-06-13 12:31:07 -04:00

config.ts

fix(db-*): ensure consistent sorting even when sorting on non-unique fields or no sort parameters at all (#12447 )

2025-05-19 12:59:12 -07:00

e2e.spec.ts

fix(ui): reordering with a join field inside a group (#12803 )

2025-06-13 12:31:07 -04:00

int.spec.ts

chore: fix jest global teardown incorrectly always returning process exit status 0 (#12907 )