@andrew-demb note that I would like this for the v6 of this package, how would you like to proceed?

I'm OK with introducing it for the v6, we too had problems with update graphqlite to v8.

Let's retarget to 6.x branch then.

@andrew-demb note that I would like this for the v6 of this package, how would you like to proceed?

I'm OK with introducing it for the v6, we too had problems with update graphqlite to v8.
Let's retarget to 6.x branch then.

Okay, I rebased on 6.x. Note that I had some minimal conflicts during cherry-pick (use function ... were in between classes, processRequest did not have an assert after it), so cherry-picking to master should observe some small, straightforward conflicts, I can handle the port to master once this get merged to 6.x.

Do you know why there are no CI checks presented in the PR?
@homersimpsons

Do you know why there are no CI checks presented in the PR? @homersimpsons

I do not know, .github/workflows/test.yaml file has the following configuration (that did not change for 4 years):

on:
    pull_request: ~
    push:
        branches:
            - master

Edit: looks like it ran with the following error:

Error: This request has been automatically failed because it uses a deprecated version of actions/cache: v4.0.2. Please update your workflow to use v3/v4 of actions/cache to avoid interruptions. Learn more: https://github.blog/changelog/2024-12-05-notice-of-upcoming-releases-and-breaking-changes-for-github-actions/#actions-cache-v1-v2-and-actions-toolkit-cache-package-closing-down

OK, now all is green.

Approved. Please release v6, merge to master, and release v7

Released as https://github.com/thecodingmachine/graphqlite-bundle/releases/tag/v6.2.0, I pulled it to my local project, and it worked correctly (when uploading a file and when not uploading one too)