Dependent changes are always prepatch when type is premajor

When I use the type premajor, dependent changes are always prepatch, even when I specify something else in dependentChangeType. Is this intentional? Or, do I need to specify premajor instead of major for dependents?

I realize that prerelease changes are somewhat hidden (#947), so I might be stumbling onto functionality that hasn't been fully defined. 🙂

Thank you for your time!

Example

// beachball.config.js
module.exports = {
  prereleasePrefix: 'rc',
};

// a change file
{
  "comment": "feat: Inputs are purple now!!",
  "type": "premajor",
  "packageName": "@myorg/myinput",
  "email": "test@example.com",
  "dependentChangeType": "major"
}

// package.json for @myorg/myinput
"name": "@myorg/myinput",
"version": "1.1.0",

// package.json for a package that depends on @myorg/myinput
"name": "@myorg/mydependent",
"version": "1.19.0",

Expected behavior

When I run beachball bump, I expect to see the following updates:

• @myorg/myinput 2.0.0-rc.0
• @myorg/mydependent 2.0.0

Alternative: Beachball could throw an error saying something like, "Only prerelease changes are available when the repo is in prerelease mode. Please select premajor, preminor, or prepatch."

Actual behavior

When I run beachball bump, I actually see the following updates:

• @myorg/myinput 2.0.0-rc.0
• @myorg/mydependent 1.19.1-rc.0

Start with the prerelease handling used by beachball bump, comparing the change file's type: "premajor" and dependentChangeType: "major" with the versions shown in the example package.json files. Reproduce the issue using the provided beachball.config.js and change file; done means dependent changes either honor the requested major type or produce a clear validation error.