Skip to content

Jackson 2.20+ compatibility: replace removed PropertyNamingStrategy constants - #24

Open
engrams-agent[bot] wants to merge 5 commits into
masterfrom
engrams/jackson-2.22-upgrade
Open

Jackson 2.20+ compatibility: replace removed PropertyNamingStrategy constants#24
engrams-agent[bot] wants to merge 5 commits into
masterfrom
engrams/jackson-2.22-upgrade

Conversation

@engrams-agent

@engrams-agent engrams-agent Bot commented Aug 31, 2026

Copy link
Copy Markdown

What

Jackson 2.20 removed the deprecated PropertyNamingStrategy constants (SNAKE_CASE, LOWER_CAMEL_CASE). This fork pinned at 6.0.4 references both in JacksonJson, which throws NoSuchFieldError at runtime when the consuming app (cortexapps/brain-backend) upgrades to Jackson 2.22.

Changes

  • JacksonJson.java: PropertyNamingStrategy.SNAKE_CASEPropertyNamingStrategies.SNAKE_CASE; PropertyNamingStrategy.LOWER_CAMEL_CASEPropertyNamingStrategies.LOWER_CAMEL_CASE; import updated accordingly.
  • pom.xml: version 6.0.4 → 6.0.5.

Why

Unblocks the Jackson 2.18→2.22 upgrade in cortexapps/brain-backend, which depends on org.gitlab4j:gitlab4j-api-cortex.

Publishing 6.0.5 to GitHub Packages is via the ci-publish workflow (workflow_dispatch).

🤖 Generated with Claude Code

engrams-agent Bot and others added 5 commits August 31, 2026 12:31
…mpat

Jackson 2.20 removed PropertyNamingStrategy.SNAKE_CASE / LOWER_CAMEL_CASE.
Switch to PropertyNamingStrategies (available since 2.12). Bump version 6.0.4 -> 6.0.5.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The Build/Publish workflows hard-failed: actions/cache@v2 is deprecated
and auto-failed. Modernize all actions and add GitHub Packages server
credentials + packages:write for publish.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Add a publish job that deploys 6.0.5 to GitHub Packages after the
build job passes, gated to pull_request so the artifact is published
exactly once (not re-published on merge to master).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
A feature-branch push previously fired both a push build and a PR build
concurrently, each spinning up a heavy gitlab-ce container; the
contention caused transient GitLab 502s in integration tests. Restrict
the push trigger to master so a feature push runs the build once via the
PR event.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.

0 participants