feat: update v112 upgrade handler

[AdriaCarrera]

PR Name

Motivation 💡

• Issue

Changes 🛠

• 1st change ✨
• 2nd change ✨

Considerations 🤔

• Warning... ⚠️
• This part could be improved...

Dependencies 📦

• Main

Summary by CodeRabbit

• Release Management

  • Release workflows now classify releases as prereleases when the latest-release option is not enabled.
  • Added support for applying the v11.2.0 upgrade path.

• Bug Fixes

  • Updated upgrade processing and release metadata to consistently identify v11.2.0, improving reliability for upgrades and prerelease publishing.

[coderabbitai]

Understand this PR’s impact

Explore downstream dependencies and potential security impact with Blast Radius.

View blast radius →

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 30c3efa1-f592-4c12-a334-c7b0edb6463d

📥 Commits

Reviewing files that changed from the base of the PR and between 7d342fe and b128769.

📒 Files selected for processing (5)

• .github/workflows/release.yml
• app/upgrades.go
• app/upgrades/v112/constants.go
• app/upgrades/v112/keepers.go
• app/upgrades/v112/upgrades.go

Included review availability: Your plan provides up to 4 included reviews per hour; 3 remain after this review.

---

📝 Walkthrough

Walkthrough

The release workflow now derives prerelease status from the dispatch input. The application upgrade registration and implementation now use the v11.2.0 upgrade package and identifier.

Changes

Release prerelease selection

Layer / File(s)	Summary
Map release input to prerelease flag .github/workflows/release.yml	The release action sets prerelease to true unless is_latest_release equals 'true'.

v11.2 upgrade registration

Layer / File(s)	Summary
Align upgrade package and handler app/upgrades.go, app/upgrades/v112/*	The upgrade package and handler registration changed from v111 and v11.1.0 to v112 and v11.2.0. The handler log messages use v11.2. The store upgrade switch still assigns an empty StoreUpgrades{}.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~8 minutes

Change: Feature

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description includes all required headings, but it retains template placeholders such as "Issue" and "1st change". It does not explain the v11.2.0 upgrade changes or the release workflow correctio…	Replace the placeholder content with the actual motivation, changes, considerations, and dependencies. Describe the v11.2.0 upgrade handler updates and the corrected prerelease condition.
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 4 files. (1 skipped: 1 …	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the main change: updating the v112 upgrade handler.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

Full details: Description check

Explanation

The description includes all required headings, but it retains template placeholders such as "Issue" and "1st change". It does not explain the v11.2.0 upgrade changes or the release workflow correction.

Full details: Docstring Coverage

Explanation

Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 4 files. (1 skipped: 1 unsupported.)

• Fix all pre-merge checks with AI

✨ Finishing Touches 💡 1

📝 Generate docstrings 💡

• Commit to this branch
• Create a new PR

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

Warning

Some tools did not complete. Review the errors below.

🔧 golangci-lint (2.13.2)

Error: can't load config: unsupported version of the configuration: "" See https://golangci-lint.run/docs/product/migration-guide for migration instructions
The command is terminated due to an error: can't load config: unsupported version of the configuration: "" See https://golangci-lint.run/docs/product/migration-guide for migration instructions

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[kpitapeersyst]

LGTM 🚀