Skip to content

fix: own domain metadata JSON reader - #1365

Merged
azurras merged 1 commit into
mainfrom
codex/domain-release-metadata-mapper
Aug 13, 2026
Merged

fix: own domain metadata JSON reader#1365
azurras merged 1 commit into
mainfrom
codex/domain-release-metadata-mapper

Conversation

@azurras

@azurras azurras commented Aug 13, 2026

Copy link
Copy Markdown
Owner

What changed

Makes DomainCollectionReleaseMetadata own its narrow JSON reader instead of requiring a legacy Jackson 2 ObjectMapper bean, and updates the Spring context regression to intentionally provide no mapper bean.

Root cause

After constructor selection was fixed, the production Spring Boot 4 candidate revealed that it does not expose com.fasterxml.jackson.databind.ObjectMapper as an autowire candidate. This component only reads one protected release metadata file and does not need application mapper customization.

Validation

  • focused RED reproduced No qualifying bean of type ObjectMapper
  • focused metadata suite GREEN 4/4
  • full :website:test :website:bootJar BUILD SUCCESSFUL
  • git diff --check

The guarded cutover recovered automatically; production is healthy on the legacy release and no legacy collection was deleted.

@azurras
azurras merged commit 753df05 into main Aug 13, 2026
8 checks passed
@azurras
azurras deleted the codex/domain-release-metadata-mapper branch August 14, 2026 13:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant