fix: workspace:* for example packages + nx prisma:generate ordering

[Copilot]

Example packages had hardcoded version strings for internal workspace packages, causing ERR_PNPM_OUTDATED_LOCKFILE in CI on every version bump. Additionally, frontend-core:compile was racily failing in parallel CI runs because tsc --build resolves @igstack/app-catalog-backend-core to its TypeScript source (via my-custom-condition) — which needs generated Prisma types — but backend-core:prisma:generate had no ordering guarantee relative to frontend-core:compile.

Changes

• examples/*/package.json — replaced pinned versions with workspace:* for all internal @igstack/ dependencies
• pnpm-lock.yaml — regenerated to reflect the above
• nx.json — two fixes:
  • Added ^prisma:generate to compile.dependsOn so all upstream prisma:generate tasks complete before any compile runs
  • Added outputs: ["{projectRoot}/src/generated"] to prisma:generate so nx cache correctly stores/restores generated Prisma client files

 "prisma:generate": {
   "cache": true,
-  "inputs": ["{projectRoot}/prisma/schema.prisma", "{workspaceRoot}/package.json"]
+  "inputs": ["{projectRoot}/prisma/schema.prisma", "{workspaceRoot}/package.json"],
+  "outputs": ["{projectRoot}/src/generated"]
 },
 "compile": {
   "cache": true,
-  "dependsOn": ["prisma:generate"],
+  "dependsOn": ["prisma:generate", "^prisma:generate"],

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• checkpoint.prisma.io
  • Triggering command: /opt/hostedtoolcache/node/24.14.0/x64/bin/node /opt/hostedtoolcache/node/24.14.0/x64/bin/node /home/REDACTED/work/app-catalog/app-catalog/node_modules/.pnpm/prisma@7.4.2_@types+react@19.2.7_react-dom@19.1.2_react@19.1.2__react@19.1.2_typescript@5.9.2/node_modules/prisma/build/child {"product":"prisma","version":"7.4.2","cli_install_type":"local","information":"","local_timestamp":"2026-03-05T19:17:53Z","project_hash":"2b52c108","cli_path":"/home/REDACTED/work/app-catalog/app-catalog/packages/backend-core/node_modules/prisma/build/inde (dns block)
  • Triggering command: /opt/hostedtoolcache/node/24.14.0/x64/bin/node /opt/hostedtoolcache/node/24.14.0/x64/bin/node /home/REDACTED/work/app-catalog/app-catalog/node_modules/.pnpm/prisma@7.4.2_@types+react@19.2.7_react-dom@19.1.2_react@19.1.2__react@19.1.2_typescript@5.9.2/node_modules/prisma/build/child {"product":"prisma","version":"7.4.2","cli_install_type":"local","information":"","local_timestamp":"2026-03-05T19:23:37Z","project_hash":"2b52c108","cli_path":"/home/REDACTED/work/app-catalog/app-catalog/packages/backend-core/node_modules/prisma/build/inde (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[lislon]

@copilot build fails

[Copilot]

@copilot build fails

The build was failing because pnpm-lock.yaml was out of sync with the updated package.json files. Fixed in 6927c4f by regenerating the lockfile to reflect the new workspace:* references.