Repository navigation
chore: release - #831
chore: release#831marvin-hansen wants to merge 2 commits into
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
deep-causality-cfd-prod | 4830789 | Commit Preview URL Branch Preview URL |
Oct 06 2026, 07:05 AM |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
quantum | 4830789 | Commit Preview URL Branch Preview URL |
Oct 06 2026, 07:05 AM |
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
2 issues found across 24 files
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="deep_causality_context/Cargo.toml">
<violation number="1" location="deep_causality_context/Cargo.toml:6">
P2: Bumping deep_causality_context to only 0.1.3 (patch) is not API-compatible with 0.1.2: the crate's `deep_causality_core` dependency requirement (workspace = true) changes from `^0.13` to `^0.14`, and 0.14.0 is a breaking release (`CausalityError` enum variant changed kind/constructor). Per the Cargo semver reference, tightening a dependency's required version range to exclude previously allowed versions is itself a breaking change for the dependent crate. Consumers on core 0.13 pinned with context 0.1.2 will fail to resolve after updating context to 0.1.3, and `cargo update` will silently pull the breaking core 0.14 into otherwise-patch-compatible builds. This version should be 0.2.0 to match the incompatible dependency change (same applies to the other core dependents physics 0.10.3, quantum 0.4.3, cfd 0.3.4, which also only received patch bumps).</violation>
</file>
<file name="deep_causality_ethos/CHANGELOG.md">
<violation number="1" location="deep_causality_ethos/CHANGELOG.md:14">
P3: This changelog marks the sole 0.5.0 change `[**breaking**]`, and the crate was bumped 0.4.1 -> 0.5.0 (the 0.x slot reserved for breaking changes), but the PR description classifies `deep_causality_ethos` as "✓ API compatible changes". The two artifacts contradict each other. A deterministic topological order + lexicographic ranking fix changes observable verdict results (behavioral break for downstream code that relied on prior ordering), so the marker has substance — but then the "API compatible" verdict in the release description is wrong, and if the semver check is right, the marker forces an unnecessary breaking-equivalent bump. Decide which classification holds and make the changelog, version bump, and release description agree before publishing.</violation>
</file>
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
| [package] | ||
| name = "deep_causality_context" | ||
| version = "0.1.2" | ||
| version = "0.1.3" |
There was a problem hiding this comment.
P2: Bumping deep_causality_context to only 0.1.3 (patch) is not API-compatible with 0.1.2: the crate's deep_causality_core dependency requirement (workspace = true) changes from ^0.13 to ^0.14, and 0.14.0 is a breaking release (CausalityError enum variant changed kind/constructor). Per the Cargo semver reference, tightening a dependency's required version range to exclude previously allowed versions is itself a breaking change for the dependent crate. Consumers on core 0.13 pinned with context 0.1.2 will fail to resolve after updating context to 0.1.3, and cargo update will silently pull the breaking core 0.14 into otherwise-patch-compatible builds. This version should be 0.2.0 to match the incompatible dependency change (same applies to the other core dependents physics 0.10.3, quantum 0.4.3, cfd 0.3.4, which also only received patch bumps).
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At deep_causality_context/Cargo.toml, line 6:
<comment>Bumping deep_causality_context to only 0.1.3 (patch) is not API-compatible with 0.1.2: the crate's `deep_causality_core` dependency requirement (workspace = true) changes from `^0.13` to `^0.14`, and 0.14.0 is a breaking release (`CausalityError` enum variant changed kind/constructor). Per the Cargo semver reference, tightening a dependency's required version range to exclude previously allowed versions is itself a breaking change for the dependent crate. Consumers on core 0.13 pinned with context 0.1.2 will fail to resolve after updating context to 0.1.3, and `cargo update` will silently pull the breaking core 0.14 into otherwise-patch-compatible builds. This version should be 0.2.0 to match the incompatible dependency change (same applies to the other core dependents physics 0.10.3, quantum 0.4.3, cfd 0.3.4, which also only received patch bumps).</comment>
<file context>
@@ -3,7 +3,7 @@
[package]
name = "deep_causality_context"
-version = "0.1.2"
+version = "0.1.3"
edition = { workspace = true }
rust-version = { workspace = true }
</file context>
|
|
||
| ### Fixed | ||
|
|
||
| - *(deep_causality_ethos)* [**breaking**] resolve conflicts in topological order and rank lexicographically |
There was a problem hiding this comment.
P3: This changelog marks the sole 0.5.0 change [**breaking**], and the crate was bumped 0.4.1 -> 0.5.0 (the 0.x slot reserved for breaking changes), but the PR description classifies deep_causality_ethos as "✓ API compatible changes". The two artifacts contradict each other. A deterministic topological order + lexicographic ranking fix changes observable verdict results (behavioral break for downstream code that relied on prior ordering), so the marker has substance — but then the "API compatible" verdict in the release description is wrong, and if the semver check is right, the marker forces an unnecessary breaking-equivalent bump. Decide which classification holds and make the changelog, version bump, and release description agree before publishing.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At deep_causality_ethos/CHANGELOG.md, line 14:
<comment>This changelog marks the sole 0.5.0 change `[**breaking**]`, and the crate was bumped 0.4.1 -> 0.5.0 (the 0.x slot reserved for breaking changes), but the PR description classifies `deep_causality_ethos` as "✓ API compatible changes". The two artifacts contradict each other. A deterministic topological order + lexicographic ranking fix changes observable verdict results (behavioral break for downstream code that relied on prior ordering), so the marker has substance — but then the "API compatible" verdict in the release description is wrong, and if the semver check is right, the marker forces an unnecessary breaking-equivalent bump. Decide which classification holds and make the changelog, version bump, and release description agree before publishing.</comment>
<file context>
@@ -7,6 +7,12 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
+
+### Fixed
+
+- *(deep_causality_ethos)* [**breaking**] resolve conflicts in topological order and rank lexicographically
+
## [0.4.1](https://github.com/deepcausality-rs/deep_causality/compare/deep_causality_ethos-v0.4.0...deep_causality_ethos-v0.4.1) - 2026-09-29
</file context>
b50620c to
5e092c5
Compare
5e092c5 to
4830789
Compare
There was a problem hiding this comment.
2 issues found across 15 reviewed files. 1 file intentionally excluded from review.
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="deep_causality_context/Cargo.toml">
<violation number="1" location="deep_causality_context/Cargo.toml:6">
P2: The README still directs consumers to `deep_causality_context = "0.1"`, which excludes this release and leaves users on the incompatible 0.1 API. Update the dependency example to `0.2` alongside this bump.</violation>
</file>
<file name="deep_causality_context_store/Cargo.toml">
<violation number="1" location="deep_causality_context_store/Cargo.toml:6">
P3: The 0.2.0 release is breaking (record/relation renames), but the crate's README (published via `readme = "README.md"`) still instructs users to add `deep_causality_context_store = "0.1"` (deep_causality_context_store/README.md:17), pointing them at the previous API. Update the snippet to "0.2" alongside the version bump.</violation>
</file>
Tip: Review your code locally with the cubic CLI to iterate faster.
Re-trigger cubic
| [package] | ||
| name = "deep_causality_context" | ||
| version = "0.1.2" | ||
| version = "0.2.0" |
There was a problem hiding this comment.
P2: The README still directs consumers to deep_causality_context = "0.1", which excludes this release and leaves users on the incompatible 0.1 API. Update the dependency example to 0.2 alongside this bump.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At deep_causality_context/Cargo.toml, line 6:
<comment>The README still directs consumers to `deep_causality_context = "0.1"`, which excludes this release and leaves users on the incompatible 0.1 API. Update the dependency example to `0.2` alongside this bump.</comment>
<file context>
@@ -3,7 +3,7 @@
[package]
name = "deep_causality_context"
-version = "0.1.3"
+version = "0.2.0"
edition = { workspace = true }
rust-version = { workspace = true }
</file context>
| [package] | ||
| name = "deep_causality_context_store" | ||
| version = "0.1.2" | ||
| version = "0.2.0" |
There was a problem hiding this comment.
P3: The 0.2.0 release is breaking (record/relation renames), but the crate's README (published via readme = "README.md") still instructs users to add deep_causality_context_store = "0.1" (deep_causality_context_store/README.md:17), pointing them at the previous API. Update the snippet to "0.2" alongside the version bump.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At deep_causality_context_store/Cargo.toml, line 6:
<comment>The 0.2.0 release is breaking (record/relation renames), but the crate's README (published via `readme = "README.md"`) still instructs users to add `deep_causality_context_store = "0.1"` (deep_causality_context_store/README.md:17), pointing them at the previous API. Update the snippet to "0.2" alongside the version bump.</comment>
<file context>
@@ -3,7 +3,7 @@
[package]
name = "deep_causality_context_store"
-version = "0.1.2"
+version = "0.2.0"
edition = { workspace = true }
rust-version = { workspace = true }
</file context>
1 participant
🤖 New release
deep_causality_algebra: 0.4.7 -> 0.4.8 (✓ API compatible changes)deep_causality_context_store: 0.1.2 -> 0.2.0 (⚠ API breaking changes)deep_causality_core: 0.13.2 -> 0.14.0 (⚠ API breaking changes)deep_causality_uncertain: 0.5.9 -> 0.5.10 (✓ API compatible changes)deep_causality_context: 0.1.2 -> 0.2.0 (⚠ API breaking changes)deep_causality: 0.18.2 -> 0.19.0 (✓ API compatible changes)deep_causality_tensor: 0.6.4 -> 0.6.5 (✓ API compatible changes)deep_causality_file: 0.2.2 -> 0.2.3 (✓ API compatible changes)deep_causality_physics: 0.10.2 -> 0.10.3 (✓ API compatible changes)deep_causality_cfd: 0.3.3 -> 0.3.4 (✓ API compatible changes)deep_causality_ethos: 0.4.1 -> 0.5.0 (✓ API compatible changes)deep_causality_quantum: 0.4.2 -> 0.4.3 (✓ API compatible changes)⚠
deep_causality_context_storebreaking changes⚠
deep_causality_corebreaking changes⚠
deep_causality_contextbreaking changesChangelog
deep_causality_algebradeep_causality_context_storedeep_causality_coredeep_causality_uncertaindeep_causality_contextdeep_causalitydeep_causality_tensordeep_causality_filedeep_causality_physicsdeep_causality_cfddeep_causality_ethosdeep_causality_quantumThis PR was generated with release-plz.