@codemation/agent-skills 0.1.0 → 0.1.1

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.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,13 @@
1
1
  # @codemation/agent-skills
2
2
 
3
+ ## 0.1.1
4
+
5
+ ### Patch Changes
6
+
7
+ - [#35](https://github.com/MadeRelevant/codemation/pull/35) [`75b885b`](https://github.com/MadeRelevant/codemation/commit/75b885b111cc34ffe3a192ca9cc8cd3864fdf8ff) Thanks [@cblokland90](https://github.com/cblokland90)! - Replace the local-development `pglite` path with SQLite across the host, CLI, scaffolding templates, and packaged dev flows while keeping PostgreSQL for production-aligned and shared integration scenarios.
8
+
9
+ Split Prisma into provider-specific PostgreSQL and SQLite schema and migration tracks so generated clients and startup migrations select the correct backend without the old `pglite` socket adapter.
10
+
3
11
  ## 0.1.0
4
12
 
5
13
  ### Minor Changes
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@codemation/agent-skills",
3
- "version": "0.1.0",
3
+ "version": "0.1.1",
4
4
  "description": "Reusable agent skills for Codemation projects and plugin development.",
5
5
  "publishConfig": {
6
6
  "access": "public"
@@ -17,9 +17,6 @@
17
17
  "bin": {
18
18
  "codemation-agent-skills": "./bin/codemation-agent-skills.mjs"
19
19
  },
20
- "scripts": {
21
- "test": "vitest run"
22
- },
23
20
  "keywords": [
24
21
  "codemation",
25
22
  "agent",
@@ -38,5 +35,8 @@
38
35
  "CHANGELOG.md",
39
36
  "bin",
40
37
  "skills"
41
- ]
42
- }
38
+ ],
39
+ "scripts": {
40
+ "test": "vitest run"
41
+ }
42
+ }
@@ -33,7 +33,7 @@ Do not use this skill for workflow graph design, custom node implementation, or
33
33
  1. Treat `codemation.config.ts` as the consumer entrypoint.
34
34
  2. Mention `.codemation/output` only when build artifacts or runtime bootstrap details matter.
35
35
  3. When the user is in the monorepo, distinguish framework-author mode from normal consumer mode explicitly.
36
- 4. When Redis-backed execution is involved, mention the shared PostgreSQL requirement instead of assuming PGlite still fits.
36
+ 4. When Redis-backed execution is involved, mention the shared PostgreSQL requirement instead of assuming local SQLite still fits.
37
37
 
38
38
  ## Read next when needed
39
39
 
@@ -57,6 +57,6 @@ Use `codemation dev --watch-framework` when working inside the Codemation monore
57
57
 
58
58
  ## Environment notes
59
59
 
60
- - PGlite is the zero-setup default for starter apps.
61
- - When `REDIS_URL` is set, use a shared PostgreSQL `DATABASE_URL`; BullMQ cannot run on PGlite.
60
+ - SQLite is the zero-setup default for starter apps.
61
+ - When `REDIS_URL` is set, use a shared PostgreSQL `DATABASE_URL`; BullMQ cannot run on SQLite.
62
62
  - Use `--consumer-root` when commands need to target a different consumer app root.
@@ -22,7 +22,7 @@ Use the minimum setup when:
22
22
 
23
23
  - you are starting a new app
24
24
  - one process is enough
25
- - local PGlite is fine
25
+ - local SQLite is fine
26
26
  - fast local iteration matters more than shared worker infrastructure
27
27
 
28
28
  ## Production setup
@@ -36,7 +36,7 @@ Move to the production shape when:
36
36
 
37
37
  That usually means:
38
38
 
39
- - PostgreSQL instead of embedded PGlite
39
+ - PostgreSQL instead of local SQLite
40
40
  - Redis for queue-backed execution
41
41
  - BullMQ-backed scheduling
42
42