Skip to content

change lerna config to keep versions in sync #58

@mumenthalers

Description

@mumenthalers

change version behavior from independent to force-publish

Synchronized Versions
Lerna will only version and publish packages that have changed since the previous release, causing package versions to drift apart over time. To prevent this, use the --force-publish option with lerna version. This will force Lerna to always version all packages, regardless of if they have changed since the previous release. Then they will all be published to the registry by lerna publish from-git. As a result, all package versions will stay synchronized to the version in lerna.json.
https://lerna.js.org/docs/features/version-and-publish

Reason: when changing something in ngx-component, it is hard to know, whether now the ngx-components only supports the latest ngx-core or still an older version of ngx-core as well (like "@shiftcode/ngx-core": "^11.0.0 || ^12.0.0"). therefore it is safer to always keep the versions in sync.

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