feat: bump wrappers version to v0.4.6

[burmecia]

What kind of change does this PR introduce?

• upgrade wrappers from v0.4.5 to v0.4.6

Additional context

Add any other context or screenshots.

Action Items

• New extension releases were Checked for any breaking changes
• Extensions compatibility Checked
  • Proceed to extensions compatibility testing, mark as done after everything is completed
• Backup and Restore Checked
  • Proceed to backup testing while extensions are enabled
    • After every restore, re-run the tests specified at point 3.1

Extensions compatibility testing

1. Enable every extension
   1. Check Postgres’ log output for any error messages while doing so
      1. This might unearth incompatibilities due to unsupported internal functions, missing libraries, or missing permissions
2. Disable every extension
   1. Check Postgres’ log output for any cleanup-related error messages
3. Re-enable each extension
   1. Run basic tests against the features they offer, e.g.:
      1. pg_net - execute HTTP requests
      2. pg_graphql - execute queries and mutations
      3. …to be filled in

Backup Testing

Follow the testing steps steps for all the following cases:

• Pause on new Postgres version, restore on new Postgres version
• Pause on older Postgres version, restore on new Postgres version
• Run a single-file backup backup, restore the backup

Testing steps

1. Generate dummy data
   • the ‘Countries’ or ‘Slack clone’ SQL editor snippets are decent datasets to work with, albeit limited
2. Save a db stats snapshot file
   • Do this by running supa db-stats gather -p <project_ref>
3. Backup the database, through pausing the project, or otherwise
4. Restore the backup, through unpausing the project or cli
5. Check the data has been recovered successfully
   1. Visual checks/navigating through the tables works
   2. Run supa db-stats verify against the project and the previously saved file

[burmecia]

it seems the arm_runner disk space isn’t enough, can we increase its size?

[soedirgo]

If that's from Testinfra Integration Tests Nix you can ignore those - it's been broken for a while. Not sure while Nix CI is failing though, and only on macOS (it builds on my machine)

[samrose]

@burmecia you could be right. I’ll start looking into testinfra tests next week. Nix ci usually only fails if there is a real problem

[samrose]

If that's from Testinfra Integration Tests Nix you can ignore those - it's been broken for a while. Not sure while Nix CI is failing though, and only on macOS (it builds on my machine)

@soedirgo @burmecia if those testinfra tests fail like this, you can feel free to reach out to me and I'll prioritize looking into those, as they caught issues when working correct, and we really need them to be functioning/useful tests. So please reach out to me if you are running into issues and I will look into issues where the failure is just the test not working.

[samrose]

@burmecia when I try to build wrappers from this branch locally on macos, the nix build is failing. Looking into it now.

[soedirgo]

@samrose sorry yeah, should’ve flagged these earlier. Once these incidents are resolved lmk if I can help with that as I was the one who set it up way back when 👍

[samrose]

@burmecia @soedirgo got this all to pass in a pr to this one. Just merged and if it passes should be good to go, other than local infra testing.

[samrose]

@burmecia @soedirgo ok every thing is passing now. If we test this in local infra, then it should be good to go

[burmecia]

that's nice, thanks @samrose and @soedirgo !