Feat/clean exclude schema

[PhilipWee]

I removed my windows specific changes and installed the specific original migra version manually in order to make these changes

There is one failing test, but I diffed the 'differences' and according to diffchecker.com there's no difference, so I'm not sure if I'm reading it correctly or just blind or what but I want to see if the tests pass on CICD first

Also a small refactor, such that

• python parity fixtures are in FIXTURES
• new feature fixtures are in NEW_FIXTURES

 set
    check_function_bodies = off;

  CREATE
- OR REPLACE FUNCTION public.newfunc (i integer, t text []) RETURNS TABLE (a text, c integer) LANGUAGE plpgsql STABLE STRICT AS $function$
-  declare
-         BEGIN
-                 select 'no', 1;
-         END;
-
+ OR REPLACE FUNCTION public.newfunc (i integer, t text []) RETURNS TABLE (a text, c integer) LANGUAGE plpgsql STABLE STRICT AS $function$
+  declare
+         BEGIN
+                 select 'no', 1;
+         END;
+
  $function$;

  CREATE
- OR REPLACE FUNCTION public.changed (i integer, t text []) RETURNS TABLE (a text, c integer) LANGUAGE plpgsql STRICT SECURITY DEFINER AS $function$    
-  declare
-         BEGIN
-                 select 'no', 1;
-         END;
-
+ OR REPLACE FUNCTION public.changed (i integer, t text []) RETURNS TABLE (a text, c integer) LANGUAGE plpgsql STRICT SECURITY DEFINER AS $function$    
+  declare
+         BEGIN
+                 select 'no', 1;
+         END;
+
  $function$;
  create materialized view "public"."matvvv" as
  SELECT
    2 AS a;

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
pgkit	🛑 Canceled (Inspect)			Jul 30, 2025 6:03am

[sweatybridge]

@mmkal would you mind taking another look at this? excluding multiple schemas is really useful

[mmkal]

This looks good! I like the separation of ported/parity tests from new features.

Minor request to make it fully non-breaking. I am a bit allergic to breaking changes, especially for projects like this where I'll be dipping in and out of it, and I want to minimise confusion over which version has which API.

[mmkal]

This looks good! Let's just make fully non breaking by using singular everywhere

[mmkal]

Sorry for double comment, first wasn't showing up for me

[sweatybridge]

Thanks for following up on this PR. When can we expect a new release to land on npm?

[mmkal]

Today! Had some problems with the release script, but it's just the changelog generation that's going wrong, so I'll release manually today even if I can't fix.

[github-actions]

Release v0.6.0 addresses this.