Skip to content

fix: shelve pull in a monorepo doesn't work #712

Description

@MarkLyck

Environment

OS: Macos 26
Browser: N/A
Node.js version: v22.21.0
Package manager: bun 1.2.18

Version

v4.1.7

Reproduction

Create monorepo,
add 1 app with shelve.json and env varaibles in shelve.
add 1 shelve.json at the root with team slug.

try shelve pull

Description

I have a monorepo using turborepo.
I don't have any root level .env file or env variables to put in the root.
I have one .env file in my /apps/web folder

I want to be able to run bunx shelve pull from the root of my monorepo and have the .env file in my /apps/web folder update to the selected env. (the docs says this should work but it does not).

I have two shelve.json files

one shelve.json in the root with just my team slug.
one shelve.json in my /apps/web project with the project and defaultEnvironment.

When I run bunx shelve pull I get this response:

┌  Pulling variable from monorepo-test project
│
◇  Fetching 'monorepo-test' project
│
◇  Fetching environments
│
◇  Select the environment:
│  Development
│
◇  Fetching variables
│
▲  No variables found in the specified environment
│
└  Successfully pulled variable from development environment

It tries to pull environment variables from "monorepo-test", but this is the root of my monorepo, not the web app. Since the root of the monorepo has no environment variables it says no variables was found (expected).

It auto created this project that I don't want/need in shelve, which is fine I guess.

But the problem is that it never tried to pull the web project in the monorepo where I actually do have environment variables to pull.

Additional context

No response

Logs

Activity

  1. MarkLyck commented on Mar 6, 2026

    @MarkLyck
    Author

    @HugoRCD is this still being maintained?

  2. HugoRCD commented on Mar 6, 2026

    @HugoRCD
    Owner

    @HugoRCD is this still being maintained?

    Yes, it's still maintained, but I'm having a bit of trouble managing all the projects at the moment as I have quite a few other priorities. I'll try to look into it this weekend without fail

  3. EmilGramDK commented on Jun 1, 2026

    @EmilGramDK

    @HugoRCD Will this be fixed or is there another way to use shelve in turborepo?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions