Run roam, obsidian and database workflows when content-model changes

[MarkAlex1234]

Reviewer brief

• Result: changes to packages/content-model (and types / utils where they apply) now trigger the workflows that build on them. Today they're skipped.
• Why: @repo/database depends on @repo/content-model and @repo/utils, and apps/roam depends on @repo/content-model, @repo/database, @repo/types and @repo/utils (all workspace:*). The paths: filters predate content-model:

Workflow	Added
roam-pr.yaml (preview deploy)	packages/content-model/**, packages/types/**
roam-main.yaml (deploy)	packages/content-model/**, packages/types/**
obsidian-main.yaml	packages/content-model/** (via @repo/database)
test-database.yaml	packages/content-model/**, packages/utils/**

content-model is actively changing (most recently in #1513). A PR that only touches packages/content-model currently gets no Roam preview and doesn't run the database tests, though both use the changed code.

• Review focus: I deliberately left out packages/eslint-config and packages/typescript-config (dev tooling). Happy to add them if you want config changes to trigger these too.

Verification

All workflow YAML parses; 7 lines added, only inside paths:. I found the gaps by comparing each workflow's filters with the pnpm workspace graph (npx github:Continuous-Actions/dynamic-monorepo audit, a GitHub Action I maintain), then checked each against the package.json files. After this change, the only remaining findings are the two config packages above.

---

[vercel]

@MarkAlex1234 is attempting to deploy a commit to the Discourse Graphs Team on Vercel.

A member of the Team first needs to authorize it.

[devin-ai-integration]

Devin Review found 1 potential issue.

[devin-ai-integration]

🟡 Shared-package releases lose Linear tracking

For content-model-only pushes, obsidian-main publishes a beta without including the change in its Linear release. Its include_paths still excludes content-model; roam-main likewise excludes content-model and types after deploying them.

Learn more

The new push filters cause main-branch changes in shared packages to publish or deploy. The subsequent Linear syncs use separate path lists, which still exclude those packages in the Obsidian sync and the Roam sync. A change with no other matching paths therefore ships without its corresponding Linear release entry. The manual stable-release workflows reuse those older lists too.

Example: A merged PR changes only packages/content-model/src/schema/index.ts. Both main workflows run, but neither Linear sync includes that path, so the published builds lack that PR in their Linear release tracking.

Recommended fix: Add packages/content-model/** to Obsidian's Linear include_paths, and add both packages/content-model/** and packages/types/** to Roam's. Update the corresponding manual stable-release syncs to use the same paths.

---

Was this helpful? React with 👍 or 👎 to provide feedback.