-
Notifications
You must be signed in to change notification settings - Fork 772
Description
Affected Packages
cli
"version": "2.18.1",
Problem
I have a monorepo of related packages and yarn changeset status succeeds locally, but fails in CI (azure devops). There is definitely a changeset file present in the ADO workspace.
Before I try
yarn changeset status
I am testing using just
ls -la
to make sure the files actually exist:
So i KNOW the changeset file exists. I generated it with a standard
yarn changeset add
However, when I run
yarn changeset status
right after those ls commands, i get:
I've also tried
yarn changeset status --since="origin/main"
since main is my baseBranch. When i run that, the error is different:
Here is my config.json:
{
"$schema": "https://unpkg.com/@changesets/config@1.6.3/schema.json",
"changelog": "@changesets/cli/changelog",
"commit": true,
"linked": [],
"access": "restricted",
"baseBranch": "main",
"updateInternalDependencies": "minor",
"ignore": ["@<scope>/docs", "@<scope>/playroom", "@<scope>/private-playroom"]
}
This CI job is running ON a merge of the main branch. So the --since= I would think isnt necessary, but i can't run the status command without origin/main because for some reason changesets cant find the main branch?
Any idea what is happening here? I do want to check for changesets, even an empty one in my CI at least for the time being until we get used to our deployment cadences and figure out better how and when we need changesets.



