ekwo-os 0.17.0 → 0.18.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "schemaVersion": "0.17.0",
3
- "migration": "20261020180100",
3
+ "migration": "20261020190000",
4
4
  "socle": {
5
5
  "schema": "public",
6
6
  "tables": [
@@ -0,0 +1,15 @@
1
+ -- Ekwo OS — an invoice is elegant unless its company says classic.
2
+ --
3
+ -- `@ekwo-ai/invoice-pdf` now prints in its `elegant` pair when a theme names
4
+ -- no typeface, so a company whose `invoice_typeface` is null prints in Inter,
5
+ -- with Fraunces for the title, the names and the headings. Nothing in the
6
+ -- rows changes: null still means "the package's default", and only the
7
+ -- comment that names that default moves.
8
+
9
+ comment on column companies.invoice_typeface is
10
+ 'The pair of typefaces of this company''s invoice PDF, by the name @ekwo-ai/invoice-pdf embeds it under: elegant (Inter, with Fraunces for the title, the names and the headings) or classic (Noto Sans). Null is the default, elegant.';
11
+
12
+ -- What every migration of this directory ends with: a function never comes
13
+ -- out of one with the built-in default, which Supabase would publish as an
14
+ -- anonymous RPC endpoint.
15
+ revoke execute on all functions in schema public from public;
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "ekwo-os",
3
- "version": "0.17.0",
3
+ "version": "0.18.0",
4
4
  "description": "Install and operate Ekwo OS on your own Supabase project: npx ekwo-os init.",
5
5
  "keywords": [
6
6
  "accounting",
@@ -50,7 +50,7 @@
50
50
  "typecheck": "tsc -p tsconfig.json --noEmit"
51
51
  },
52
52
  "dependencies": {
53
- "@ekwo-ai/core": "^0.17.0",
53
+ "@ekwo-ai/core": "^0.18.0",
54
54
  "postgres": "^3.4.5"
55
55
  }
56
56
  }