Skip to content

Prepare release of v5.0.0#199

Merged
richvdh merged 2 commits into
mainfrom
release-5.0.0
Jul 22, 2026
Merged

Prepare release of v5.0.0#199
richvdh merged 2 commits into
mainfrom
release-5.0.0

Conversation

@richvdh

@richvdh richvdh commented Jul 22, 2026

Copy link
Copy Markdown
Member

No description provided.

@richvdh
richvdh requested a review from poljar July 22, 2026 10:59
@helloskyline-a11y

helloskyline-a11y commented Jul 22, 2026

Copy link
Copy Markdown

I believe it is because seshat-node/Cargo.toml still use seshat = "4.3.0" as dependency.
Maybe a random question, but why you don't use seshat = { version = "x.x.x", path = ".." }?

@richvdh

richvdh commented Jul 22, 2026

Copy link
Copy Markdown
Member Author

Maybe a random question, but why you don't use seshat = { version = "x.x.x", path = ".." }?

Great question. @poljar ?

@poljar

poljar commented Jul 22, 2026

Copy link
Copy Markdown
Collaborator

I believe it is because seshat-node/Cargo.toml still use seshat = "4.3.0" as dependency. Maybe a random question, but why you don't use seshat = { version = "x.x.x", path = ".." }?

Because the Cargo.toml file will be put into the node package as is. This means that if you try to build the node package it will attempt to find seshat at the path, thus the build will fail.

We use a patch override in the workspace toml file to override this and do depend on the path there.

@helloskyline-a11y

Copy link
Copy Markdown

Because the Cargo.toml file will be put into the node package as is. This means that if you try to build the node package it will attempt to find seshat at the path, thus the build will fail.

We use a patch override in the workspace toml file to override this and do depend on the path there.

Right, didn't know that. Looks fair, thanks!

@poljar poljar left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good.

@poljar

poljar commented Jul 22, 2026

Copy link
Copy Markdown
Collaborator

I believe it is because seshat-node/Cargo.toml still use seshat = "4.3.0" as dependency. Maybe a random question, but why you don't use seshat = { version = "x.x.x", path = ".." }?

Because the Cargo.toml file will be put into the node package as is. This means that if you try to build the node package it will attempt to find seshat at the path, thus the build will fail.

We use a patch override in the workspace toml file to override this and do depend on the path there.

This is somewhat tersely documented in the workspace toml file:

seshat/Cargo.toml

Lines 63 to 67 in a0d88f9

[patch.crates-io]
# Ensure that seshat-node uses the local seshat version.
#
# The Cargo.toml file in the seshat-node directory needs to point to a published
# version as we're packaging and publishing this Cargo.toml file as is.

@richvdh
richvdh merged commit 7bf6378 into main Jul 22, 2026
7 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.

3 participants