Keep the kyo experiment out of every publish #89

Merged

claude merged 1 commit from fix/kyo-unpublished into main

2026-10-16 13:41:14 +00:00

claude commented

2026-10-16 09:38:12 +00:00

Member

Summary

KX-D7 holds kyo as an unpublished experiment, and build.mill said so. But kyo extended SharedModule, which mixed in PublishModule, so the publish selector __:PublishModule.publishArtifacts took it: claude-code-query-kyo_3:0.7.0-SNAPSHOT is in the registry since 2026-10-01. Tagging v0.7.0 would have added a release of it that the registry cannot overwrite.

SharedModule carries the compile settings only.
PublishedModule adds PublishModule, the version and the POM. Every module except kyo extends it.

This must merge before the 0.7.0 release.

Verification

./mill resolve __:PublishModule.publishArtifacts lists core, core.js, direct, effectful, zio, ui, ui.js — no kyo.
./mill show core.publishVersion → "0.7.0-SNAPSHOT" (the publish gate reads it).
./mill __.compile passes with no warnings.

🤖 Generated with Claude Code

https://claude.ai/code/session_01XE9uNVmKpVQiZvc3kLY2zh

## Summary KX-D7 holds `kyo` as an unpublished experiment, and `build.mill` said so. But `kyo` extended `SharedModule`, which mixed in `PublishModule`, so the publish selector `__:PublishModule.publishArtifacts` took it: `claude-code-query-kyo_3:0.7.0-SNAPSHOT` is in the registry since 2026-10-01. Tagging v0.7.0 would have added a release of it that the registry cannot overwrite. - `SharedModule` carries the compile settings only. - `PublishedModule` adds `PublishModule`, the version and the POM. Every module except `kyo` extends it. This must merge before the 0.7.0 release. ## Verification - `./mill resolve __:PublishModule.publishArtifacts` lists core, core.js, direct, effectful, zio, ui, ui.js — no kyo. - `./mill show core.publishVersion` → `"0.7.0-SNAPSHOT"` (the publish gate reads it). - `./mill __.compile` passes with no warnings. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01XE9uNVmKpVQiZvc3kLY2zh

claude added 1 commit

2026-10-16 09:38:12 +00:00

Keep the kyo experiment out of every publish

CI / Compile (pull_request) Successful in 2m1s

Details

CI / Check Formatting (pull_request) Successful in 39s

Details

CI / Check Linting (pull_request) Successful in 1m29s

Details

CI / Check Bundle Size (pull_request) Successful in 46s

Details

CI / Run Tests (pull_request) Failing after 2m55s

Details

CI / Run Integration Tests (pull_request) Successful in 1m49s

Details

8484ae442c

KX-D7 holds kyo as an unpublished experiment, and build.mill said so,
but kyo extended SharedModule, which mixed in PublishModule. The publish
selector __:PublishModule.publishArtifacts therefore took it, and
claude-code-query-kyo_3:0.7.0-SNAPSHOT reached the registry. Tagging
v0.7.0 would have added a release of it that the registry cannot
overwrite.

SharedModule now carries the compile settings only. PublishedModule adds
PublishModule, the version and the POM, and every module except kyo
extends it. ./mill resolve __:PublishModule.publishArtifacts no longer
lists kyo.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XE9uNVmKpVQiZvc3kLY2zh

claude referenced this pull request

2026-10-16 09:40:13 +00:00

Release 0.7.0 #90

claude referenced this pull request

2026-10-16 13:26:59 +00:00

ci: give the jobs that run the unit suite a reaping PID 1 #91

claude merged commit baaaf94e47 into main

2026-10-16 13:41:14 +00:00

claude deleted branch fix/kyo-unpublished

2026-10-16 13:41:14 +00:00

claude referenced this pull request from a commit

2026-10-16 13:41:15 +00:00