Skip to content

chore(layout-elk): release the first version on the @joint/core version line - #3564

Merged
kumilingus merged 2 commits into
clientIO:masterfrom
kumilingus:fix/layout-elk-version
Oct 26, 2026
Merged

kumilingus merged 2 commits into
clientIO:masterfrom
kumilingus:fix/layout-elk-version

Conversation

@kumilingus

Copy link
Copy Markdown
Contributor

Summary

The release PR (#3527) would publish @joint/layout-elk as 4.4.0, while @joint/core goes to 4.3.4. The package started at 4.3.0 and its new-package changeset is a minor, and it is not linked with @joint/core, so Changesets bumps it on its own: 4.3.0 + minor.

@joint/layout-elk has never been published, so its first version can still start on the @joint/core version line:

  • packages/joint-layout-elk/package.json: 4.3.0 → 4.3.3 (the current @joint/core version).
  • .changeset/layout-elk-new-package.md: minor → patch - a minor would also move the linked @joint/core to 4.4.0.
  • .changeset/config.json: add @joint/layout-elk to the linked group with @joint/core, @joint/layout-directed-graph, @joint/layout-msagl and @joint/router-avoid, so later releases stay on the same line.

In the package's changelog the "new package" entry moves from "Minor Changes" to "Patch Changes".

Testing

changeset version on a copy of this branch: @joint/layout-elk 4.3.4 and @joint/core 4.3.4; the other packages unchanged from #3527. yarn.lock is unaffected.

…on line

The package started at 4.3.0 with a minor changeset, so the release
would publish it as 4.4.0 - ahead of @joint/core (4.3.4). It has never
been published, so start it at the current @joint/core version with a
patch changeset instead, and link it with @joint/core and the other
layout packages so later releases stay on the same version line.
@kumilingus
kumilingus merged commit 7dd1459 into clientIO:master Oct 26, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants