Repository navigation
fix(deps): point Causals and ZeroProb at their re-minted v8 UUIDs - #77
Merged
Merged
Conversation
Causals (c4a8b6d2-… → 01a11d29-d897-8383-92d8-041d500f9c95) and ZeroProb (f9e8c2e0-… → 01a11d29-d894-81ed-be3f-5f3acc80d59a) were re-minted as UUIDv8 (ADR-008 profile T) in Causals.jl#68 and ZeroProb.jl#61, both merged. Pkg resolves deps by UUID, so this package must carry the new UUIDs to resolve them at all. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WPSJ7fBhVAMcpSffCBWUDo Signed-off-by: Jonathan D.A. Jewell <6759885+hyperpolymath@users.noreply.github.com>
|
Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configuration
📒 Files selected for processing (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
7 of 14 tasks
hyperpolymath
added a commit
that referenced
this pull request
Oct 9, 2026
<!-- SPDX-License-Identifier: CC-BY-SA-4.0 Copyright (c) Jonathan D.A. Jewell <j.d.a.jewell@open.ac.uk> --> ## Summary This mints a fresh v8 UUID for the package and bumps it to **0.1.1**, so it can be registered in `julia-professional-registry` (JPR) under its current name. JPR registers this package as **`InvestigativeJournalist`** (UUID `379a7c0a-…`, 0.1.0, tree `725a1870`). It was later renamed in-repo to **`InvestigativeJournalism`** in 98ccf6b, which renamed the module too. REGISTRY-POLICY treats a rename as a new package with a new UUID, and D320 mints every new ID as v8. The registered 0.1.0 also cannot stay. Its `Deps.toml` binds the **old** Causals and ZeroProb UUIDs, which JPR is rebinding to their v8 re-mints in the same registry change (Causals#68, ZeroProb#61, this repo's #77). The owner ruled on 2026-10-09 (selection UI) to remove `InvestigativeJournalist` 0.1.0 and register `InvestigativeJournalism` 0.1.1 at a new v8. The JPR PR with ADR 0002 will link here. ## Changes - `uuid`: `379a7c0a-3675-4b32-b948-cb4760c6e442` → `01a11de2-b9d3-80b4-b616-640df22918c0` (ADR-008 profile T, minted with `bun standards/scripts/uuid-v8.js t`) - `version`: 0.1.0 → 0.1.1 - `ffi/zig/src/main.zig` (header, `VERSION`, `BUILD_INFO`) and `stapeln.toml` `[metadata].version` now carry the new name and 0.1.1. CodeRabbit flagged both; fixed in `ea0faa0`. ⚠ **Breaking:** existing installs must `Pkg.rm("InvestigativeJournalist")`, then `Pkg.add("InvestigativeJournalism")`. No other package in JPR depends on this one (checked across the registry's `*/Deps.toml`). ## 📌 New pins - **Head SHA: `ea0faa0d206cb7482e11febdc82d98c5a752a8b3`** (tree `6e624d2077ca172390591328e5faaf894c2b0d21`). The JPR entry registers this tree and is re-confirmed against the squash commit. - No action, lockfile or container pins are added or changed. ## RSR Quality Checklist ### Required - [ ] Tests pass: not yet runnable. The test environment resolves Causals and ZeroProb at their new UUIDs, which are not in JPR until the registry PR merges. I will run it against the registry branch and record the result here. - [x] Code is formatted: only string and version literals changed (two TOML values, three Zig lines). - [x] Linter is clean: no source changed. - [x] No banned language patterns. - [x] No `unsafe` blocks: not applicable, no source changed. - [x] No banned functions: not applicable, no source changed. - [x] SPDX headers: no new files, and Project.toml carries none today. - [x] No secrets, credentials or `.env` files. ### As Applicable - [ ] `.machine_readable/*.a2ml`: not applicable. A2ML is retired (D99/D269c), and this PR touches no descriptile. - [ ] Documentation: none references the UUID or version (`git grep 379a7c0a` hit only Project.toml). - [ ] `TOPOLOGY.md`: no architecture change. - [ ] CHANGELOG: none in this repo for package versions; the version bump is the record. - [ ] New dependencies: none. - [ ] ABI/FFI: unchanged. ## Testing - `git grep -n 379a7c0a origin/main` → `Project.toml:2` only. - Old-name leftovers, not changed here because they predate this PR (from the rename in 98ccf6b/ebb4b2d) and are logged for the owner: `Investigativejournalist.Jl` in the Justfile, `.machine_readable/contractiles/Justfile`, `setup.sh` and `QUICKSTART-*.adoc`. Also, `ffi/zig/src/main.zig:55` `export fn InvestigativeJournalism.jl_init()` is not a valid Zig identifier: `zig ast-check` rejects the file on base `e949898` too, and Julia never loads it. - The UUID shape was checked against `^[0-9a-f]{8}-[0-9a-f]{4}-8[0-9a-f]{3}-[89ab][0-9a-f]{3}-[0-9a-f]{12}$` (version 8, RFC variant). - Commits `3051a2e` and `ea0faa0` are signed (`%G?` = `G`). 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_016XJoh8YA2sCWQmq93CF8RX --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Points two dependencies at their re-minted UUIDv8 identities. Causals.jl#68 and ZeroProb.jl#61 (both merged 2026-10-08) replaced patterned placeholder UUIDs with ADR-008 profile-T v8 UUIDs, per the owner ruling of 2026-10-08 that extends D320. Pkg resolves a dependency by UUID, so without this change the package cannot resolve either one once
julia-professional-registryre-registers them.Changes
Project.toml[deps]Causals:c4a8b6d2-f9e3-4c1a-b8d7-9f2e3c4d5e6f→01a11d29-d897-8383-92d8-041d500f9c95Project.toml[deps]ZeroProb:f9e8c2e0-8b4a-4d5f-9a3c-1e2d3c4b5a6f→01a11d29-d894-81ed-be3f-5f3acc80d59a📌 New pins
45aaca0c5b4d2dbcf38051096d01fc112348e7f1(treee6f7a448c91650b024d7e20e5a7c5f53018dbe88)RSR Quality Checklist
Required
unsafeblocks: none touchedProject.tomlcarries none by convention.envfiles includedAs Applicable
.machine_readable/*.a2ml: n/a, A2ML is retired (D99) and is not editedTOPOLOGY.md: architecture unchangedCHANGELOG: identity-only dependency changeTesting
Pkg.test()on Julia 1.12.6, with the re-minted Causals and ZeroProb copiesPkg.developed:InvestigativeJournalism.jl174/174,E2E Pipeline Tests28/28,Property-Based Tests870/870;InvestigativeJournalism tests passed.origin/main3d5a1df, deps resolved from the registry): does not precompile,UndefVarError: Granger not defined in Causals. The registered Causals 0.2.0 tree predatesGranger. That is a pre-existing break, not caused by this PR; the re-registration at Causals 0.2.1 picks up the current tree.Notes for reviewers
julia-professional-registryre-registration PR lands.InvestigativeJournalistwhile this package's name isInvestigativeJournalism. That is a separate, pre-existing finding, recorded indev-notes/inbox/findings.mdand not touched here.🤖 Generated with Claude Code
https://claude.ai/code/session_01WPSJ7fBhVAMcpSffCBWUDo