Release 0.5.0; publish only to the iterative-works Maven registry #61

Merged

mph merged 1 commit from release/0.5.0 into main

2026-08-13 19:12:31 +00:00

mph commented

2026-08-13 13:04:06 +00:00

Owner

Summary

Cuts version 0.5.0 and makes the iterative-works Forgejo Maven registry the single publish target.

Why Maven Central is dropped

core now depends on works.iterative.support::iw-support-time:0.2.0 (build.mill:45, and :56 for core.js). That dependency arrived after v0.4.1, in b20b21e (log timestamps moved from java.time.Instant to Moment) and e86bc72 (pinned to the released 0.2.0).

Sonatype Central does not host it. Verified:

https://repo1.maven.org/maven2/works/iterative/ lists only claude-code-query-*, mill-iw-support, and scalatags-*. There is no works/iterative/support/ path.
The Central search index returns numFound: 0 for both a:iw-support-time* and g:works.iterative.support.
The artifact resolves from the forge registry (iw-support-time_3-0.2.0.pom → 200).

A Central copy of core would therefore name a dependency that a Central-only consumer cannot resolve. No published version breaks — nothing before 0.5.0 carries this dependency — but 0.5.0 itself would be unusable from Central. Central becomes a viable second target once iw-support-time publishes there.

Changes

build.mill — publishVersion 0.5.0
.github/workflows/publish.yml — drop the Sonatype Central step; comment records the registry constraint
README.md — add the resolver consumers need; version 0.1.0 → 0.5.0 (stale since 0.2.0)
ARCHITECTURE.md — publish target is the iterative-works registry

Artifacts at 0.5.0

claude-code-query-core_3, claude-code-query-core_sjs1_3 (new, from ADR 0002), claude-code-query-direct_3, claude-code-query-effectful_3, claude-code-query-zio_3. uispike is not published.

Verification

./mill __.compile — SUCCESS
./mill __.test — SUCCESS
./mill __.fix --check — SUCCESS
Generated claude-code-query-core_3-0.5.0.pom inspected; version and dependency set correct

## Summary Cuts version 0.5.0 and makes the iterative-works Forgejo Maven registry the single publish target. ## Why Maven Central is dropped `core` now depends on `works.iterative.support::iw-support-time:0.2.0` (`build.mill:45`, and `:56` for `core.js`). That dependency arrived after v0.4.1, in `b20b21e` (log timestamps moved from `java.time.Instant` to `Moment`) and `e86bc72` (pinned to the released 0.2.0). Sonatype Central does not host it. Verified: - `https://repo1.maven.org/maven2/works/iterative/` lists only `claude-code-query-*`, `mill-iw-support`, and `scalatags-*`. There is no `works/iterative/support/` path. - The Central search index returns `numFound: 0` for both `a:iw-support-time*` and `g:works.iterative.support`. - The artifact resolves from the forge registry (`iw-support-time_3-0.2.0.pom` → 200). A Central copy of `core` would therefore name a dependency that a Central-only consumer cannot resolve. No published version breaks — nothing before 0.5.0 carries this dependency — but 0.5.0 itself would be unusable from Central. Central becomes a viable second target once `iw-support-time` publishes there. ## Changes - `build.mill` — `publishVersion` 0.5.0 - `.github/workflows/publish.yml` — drop the Sonatype Central step; comment records the registry constraint - `README.md` — add the resolver consumers need; version 0.1.0 → 0.5.0 (stale since 0.2.0) - `ARCHITECTURE.md` — publish target is the iterative-works registry ## Artifacts at 0.5.0 `claude-code-query-core_3`, `claude-code-query-core_sjs1_3` (new, from ADR 0002), `claude-code-query-direct_3`, `claude-code-query-effectful_3`, `claude-code-query-zio_3`. `uispike` is not published. ## Verification - `./mill __.compile` — SUCCESS - `./mill __.test` — SUCCESS - `./mill __.fix --check` — SUCCESS - Generated `claude-code-query-core_3-0.5.0.pom` inspected; version and dependency set correct

mph added 1 commit

2026-08-13 13:04:06 +00:00

Release 0.5.0; publish only to the iterative-works Maven registry

CI / Compile (pull_request) Successful in 1m12s

Details

CI / Check Formatting (pull_request) Successful in 49s

Details

CI / Check Linting (pull_request) Successful in 49s

Details

CI / Run Tests (pull_request) Successful in 1m3s

Details

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

Details

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

Details

01b005c1a5

core depends on works.iterative.support::iw-support-time, which Sonatype
Central does not host. A Central copy of core would name a dependency that
a Central-only consumer cannot resolve, so the forge registry is the single
publish target. Central becomes viable again once iw-support-time reaches it.

README now shows the resolver consumers need, and the current version.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

mph merged commit b66a0e18ee into main

2026-08-13 19:12:31 +00:00

mph deleted branch release/0.5.0

2026-08-13 19:12:32 +00:00

mph referenced this pull request from a commit

2026-08-13 19:12:33 +00:00

Merge pull request 'Release 0.5.0; publish only to the iterative-works Maven registry' (#61) from release/0.5.0 into main

mph referenced this pull request

2026-08-13 19:16:45 +00:00

Open 0.6.0-SNAPSHOT after the 0.5.0 release #62