Release 0.2: publish RC.2 with the sync foreign-key fix #31

Merged

james.maes merged 6 commits from chore/release-0.2.0-20261106 into release/0.2 2026-11-06 20:22:36 +00:00

Conversation 0 Commits 6 Files Changed 9

+152 -42

james.maes commented 2026-11-06 19:11:41 +00:00

Owner

Copy link

Copy source

Brings release/0.2 up to the 0.2.0 candidate content (PR 30 to main carries the same commits). Pushing this merge publishes the next 0.2.0 release candidate to the QRun-IO Gitea Maven registry, which GG Forge will pin in place of its local-only qbit-geo-data:0.1.0-forge.6ac6a0366c34-sync1.

Brings release/0.2 up to the 0.2.0 candidate content (PR 30 to main carries the same commits). Pushing this merge publishes the next 0.2.0 release candidate to the QRun-IO Gitea Maven registry, which GG Forge will pin in place of its local-only qbit-geo-data:0.1.0-forge.6ac6a0366c34-sync1.

james.maes added 6 commits 2026-11-06 19:11:41 +00:00

ci: use shared ci-workflows Maven workflow ... 006ae730d7

Replace the platform-ci release callers with one caller of
KofTwentyTwo/ci-workflows maven.yaml (qqq-orb port).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

ci: rerun checks after dispatcher retirement 2cb2646fe1

Merge pull request 'ci: use shared ci-workflows Maven workflow' (#25) from ci/ci-workflows into main 9c42b3d913

fix(sync): resolve country and state foreign keys and fail on rejected rows ... 2fd63e734b

Port the sync-step half of GG Forge's qualified geo-data-sync.patch (its
entity/producer half landed in b5787bb). The 0.1.0 step matched states on
countryAlpha2 + code and cities on countryAlpha2 + stateCode + name, columns
that do not exist in the schema, so it reported success after persisting 250
countries and zero states or cities.

Resolve the bundled source codes to the persisted countryId and
stateProvinceId before matching; match cities on stateProvinceId, name,
latitude and longitude at the schema's seven-decimal precision; compare
numbers by BigDecimal value so a second run is a no-op; reactivate an
inactive row whose source entry returns; and check insert/update results so
a row the backend rejects fails the sync with a QException.

Same change as the Forge pin 0.1.0-forge.6ac6a0366c34-sync1, with the inline
java.math qualifications turned into imports and the class Javadoc updated.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Signed-off-by: James Maes <james@kof22.com>

chore(release): prepare 0.2.0 ... 401e7ca471

Set the revision to 0.2.0: main already started the 0.2.0 line (6337bfe)
because the QQQ dependency moved from 0.35.0 to 4.1.0-RC.21, a minor
change, not a patch. Align GeoDataQBitProducer.VERSION and its test with
the pom. Add the 0.2.0 changelog entry, move the already-shipped 0.1.0
bullets out of Unreleased, and correct the README coordinates
(artifactId qbit-geo-data, version 0.2.0, Gitea registry, Java 21 / QQQ 4.1).

No tag, release or publish: a push to main only verifies; the v0.2.0 tag
publishes through the shared ci-workflows Maven workflow.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Signed-off-by: James Maes <james@kof22.com>

build(pom): flatten the CI-friendly revision in published POMs ... b50515a8e8

The root pom keeps its version in the CI-friendly ${revision} property and
the shared ci-workflows Maven workflow deploys with a plain mvn deploy, so
the installed and deployed module POMs carried an unresolved
<parent><version>${revision}</version> that a consuming build cannot resolve
(the retired CircleCI orb path published resolved POMs, 68e85e6). Add
flatten-maven-plugin 1.7.3 in resolveCiFriendliesOnly mode so the published
POMs carry the literal version; ignore the generated .flattened-pom.xml.

Verified with Maven 3.9.11: clean verify passes (29 tests), the installed
qbit-geo-data-0.2.0.pom declares parent version 0.2.0, and a throwaway
consumer resolves com.kingsrook.qbits:qbit-geo-data:0.2.0 through the full
parent chain.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Signed-off-by: James Maes <james@kof22.com>

james.maes merged commit 93e5e7a000 into release/0.2 2026-11-06 20:22:36 +00:00

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

Clear labels

bug

Something isn't working

dependencies

documentation

Improvements or additions to documentation

duplicate

This issue or pull request already exists

enhancement

New feature or request

good first issue

Good for newcomers

help wanted

Extra attention is needed

invalid

This doesn't seem right

java

Pull requests that update java code

question

Further information is requested

secuurity

wontfix

This will not be worked on

No labels

Milestone

No items

No Milestone

Projects

Clear projects

No projects

Assignees

Clear assignees

forge-recovery (Forge Recovery) james.maes (James Maes)

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: QRun-IO/qbit-geo-data#31