intuit / intuit/auto

Auto fails to keep the latest prerelease (next) version of independant package after new commit

Open
#2,371 0 comments 1 reaction 0 assignees View on GitHub
bug
Dominant language
TypeScript
Stars
2.5k
Forks
221
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**
I'm using Auto with PNPM workspace. I use the default `next` branch for my prerelease(s).

Suppose I have 3 independent packages:

1. `@pkg/foo:0.1.0`
2. `@pkg/bar:0.1.0` - Has dependency `"@pkg/foo": "workspace:*"`
3. `@pkg/baz:0.1.0`- Has dependency `"@pkg/foo": "workspace:*"`

With my `next` prerelease with `patch` bump. As part of my first commit in my PR (`next`), I do a change to all packages. The bump is done accordingly:

1. `@pkg/foo:0.1.1-next.0`
2. `@pkg/bar:0.1.1-next.0`
3. `@pkg/baz:0.1.1-next.0`

However, in my 2nd commit in the same PR, if I do another commit that only changes `@pkg/baz`. The bump only happens to that package (i.e. `@pkg/baz:0.1.1-next.1`), but it's dependant package `@pkg/foo` will revert back to its original version (i.e. `@pkg/foo:0.1.0`). Therefore, when I try to install `pnpm add @pkg/baz:0.1.0@next`, I get the following error:

```
 ERR_PNPM_NO_MATCHING_VERSION  No matching version found for @pkg/foo:0.1.0

This error happened while installing the dependencies of @pkg/baz:0.1.1-next.1

The latest release of @pkg/foo is "0.1.1-next.0".
```

The expected outcome should be to use the latest `pre-release` next version for its dependent packages as well.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.