Canary mode ignores independent version mode — uses root package version for all packages

[blowsie]

Description

When using versionMode: 'independent' in a monorepo, canary mode (relizy release --canary) computes a single version from the root package.json and applies it to all packages, ignoring each package's actual version.

Expected behavior

Canary versions should be based on each package's individual version, matching how bumpIndependentMode works. For example:

• @my-org/ui@9.1.0 → @my-org/ui@9.1.1-rc.<sha>.0
• @my-org/config@1.2.0 → @my-org/config@1.2.1-rc.<sha>.0

Actual behavior

All packages get the same canary version derived from the root package.json version:

• @my-org/ui@9.1.0 → @my-org/ui@1.0.1-rc.<sha>.0
• @my-org/config@1.2.0 → @my-org/config@1.0.1-rc.<sha>.0

Root cause

In bumpCanaryMode (relizy source), line ~3831:

const currentVersion = rootPackageBase.version;

This always reads from the root package.json, then applies the single computed canary version to all packages (line ~3864-3867):

const packagesWithCanaryVersion = packages.map((pkg) => ({
  ...pkg,
  newVersion: canaryVersion
}));

Compare with bumpIndependentMode which correctly resolves tags and versions per-package.

Config

export default defineConfig({
  monorepo: {
    versionMode: 'independent',
    packages: ['packages/*'],
  },
})

Environment

• relizy v1.2.0
• pnpm workspace monorepo
• CI: GitHub Actions

[LouisMazel]

Hi @blowsie,

Thanks for the bug report!

I released the fix into the beta version v1.2.2-beta.1
Can you test it and tell me if everything works correctly before releasing a stable version?

Thanks!

[blowsie]

I have a branch I should be able to test with thank you.

Fwiw I found the package to work quite well with most of my requirements, but not so much with my release strategy and model.

I'm running some experiments with googles release-please package too

[LouisMazel]

Thanks!

Curious to hear more about your release strategy. What's missing for you in Relizy?
Always open to ideas, feel free to open an issue or share your thoughts here, whichever you prefer!