Chris Raible 0130c9f553 Renamed foreign key constraint in migration v5.45 (#16664) ... - the autogenerated constraint name was too long for MySQL, yielding the error below (although it seems to be fine for sqlite) - this change adds an explicit, shorthand name for the constraint to stay under the limit on MySQL8 Error: alter table `post_revisions` add constraint `post_revisions_author_id_foreign` foreign key (`author_id`) references `users` (`id`), algorithm=copy - Specified key was too long; max key length is 3072 bytes		2023-04-18 15:02:13 +01:00
..
e2e-api	Persisted post revision author and title (#16653)	2023-04-18 14:15:26 +01:00
e2e-browser	Fixing error in browser test (#16583)	2023-04-07 01:11:37 -07:00
e2e-frontend	Added show_latest_posts column to newsletter table (#16402)	2023-03-20 11:10:49 +01:00
e2e-server	Removed unnecessary mockMail call	2023-04-07 14:34:57 +02:00
e2e-webhooks	Added post_revisions as a default include for posts (#16660)	2023-04-18 11:12:35 +01:00
integration	Added retries to a flaky batch sending test (#16591)	2023-04-07 17:44:11 -07:00
regression	Added post_revisions as a default include for posts (#16660)	2023-04-18 11:12:35 +01:00
unit	Renamed foreign key constraint in migration v5.45 (#16664)	2023-04-18 15:02:13 +01:00
utils	Fixed flaky test: posts API export can export with order (#16605)	2023-04-10 18:40:03 -07:00
.eslintignore	Converted Ghost repo into a monorepo	2022-07-20 16:41:05 +02:00
.eslintrc.js	Removed all unused variables from test files	2023-03-10 14:29:55 +01:00