@kapa.ai Is anyone using elementary in many projects that are hosted in one github repo? I'm tired of manually going through and incrementing elementary versions at different times and then having to manage different scripts and jobs and environments to make sure i'm running the correct version of the cli to match. I would like to have that version number or package/packages all handled in a shared file or variable or something referenced by the projects that I would like elementary running in. I would obviously have to handle the profiles and schema names and all that in the projects themselves. I could then manage the version in one place and then just make sure the models are being "built" on every run of the separate dbt jobs for each project in case the version does go up or something.

The knowledge sources don't contain enough information to give you a definitive, documented answer on managing a shared Elementary version across multiple dbt projects in a monorepo. However, based on what the community has shared, I can offer some relevant context. Multi-Project Monorepo with Elementary One community member described exactly this pattern and found a workable solution: > "What we ended up doing was creating a project that had the other 2 projects listed as packages and then we ran Elementary from there. That way both projects get included. This also works to have only one dbt docs." [Multi-project setup] This approach — a wrapper/parent dbt project that lists your individual projects as packages — would naturally centralize your

packages.yml

, meaning Elementary's version would be defined in one place. Each sub-project would still need its own Elementary schema and profiles configuration, which you've already accounted for. Key Caveats to Be Aware Of • Elementary OSS does not officially support multiple dbt projects sharing a single Elementary schema. Each project must write to its own distinct Elementary schema to avoid artifact overwrites. [Multi-project schema conflict] • Elementary Cloud does support connecting multiple dbt projects (each with its own Elementary schema) into a single unified environment, which would eliminate the need to manage separate reports and jobs. [Cloud multi-env] What the Knowledge Sources Don't Cover The specific mechanics of sharing a

packages.yml

or a version variable across sibling dbt projects in a monorepo (without a wrapper project) aren't documented in the available sources. Your instinct about a shared file or variable is reasonable from a dbt packaging perspective, but I can't confirm a supported pattern for this beyond the wrapper-project approach mentioned above. If the wrapper project approach isn't viable for you, reaching out directly to the Elementary team or the community Slack would be the best next step, as this is an active area of interest. 👍 0 button 👎 0 button ℹ️ Tip: Mention @elementary.ai in the thread for follow-ups or DM the app for 1-to-1 help.