Skip to content

Dependent changes are always prepatch when type is premajor #1027

Open
@rdebeasi

Description

@rdebeasi

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": "[email protected]",
  "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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions