Skip to content

fix: trigger re-release after vogue hotfix#275

Merged
meotch merged 1 commit into
masterfrom
mitch/rerelease_after_vogue_hotfix
Jun 1, 2026
Merged

fix: trigger re-release after vogue hotfix#275
meotch merged 1 commit into
masterfrom
mitch/rerelease_after_vogue_hotfix

Conversation

@meotch
Copy link
Copy Markdown
Contributor

@meotch meotch commented Jun 1, 2026

Summary of Changes

vogue update somehow caused jackson-core to look for non existent v2.22.0, causing release to fail. Vogue 4.0.1 resolves that issue, this MR will properly release the gradle 8 and java 21 changes for path-core

MC-12414

Public API Additions/Changes

None

Downstream Consumer Impact

None

How Has This Been Tested?

Verified locally against Wedge/Abagnale

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my code
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works

vogue update somehow caused jackson-core to look for non existent v2.22.0, causing release to fail
@meotch
Copy link
Copy Markdown
Contributor Author

meotch commented Jun 1, 2026

  • No change shows up for vogue because vogue plugin import uses 4.+ notation (and plugin dependencies do not get dumped to the lockfiles)
  • Verified pipeline succeeds now with vogue hotfix released
  • This MR is needed to retrigger a release using a new version, now that the release pipeline will not break

@meotch meotch merged commit 3c0dc3f into master Jun 1, 2026
10 of 11 checks passed
@meotch meotch deleted the mitch/rerelease_after_vogue_hotfix branch June 1, 2026 17:45
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.

3 participants