Repository navigation
fix(ci): resolve Guice inject WARNING, correct OSSRH URLs, modernize GH Actions - #367
Open
maheshshinde9100 wants to merge 3 commits into
Open
maheshshinde9100 wants to merge 3 commits into
maheshshinde9100 wants to merge 3 commits into
Conversation
![semgrep-code-razorpay[bot]](https://avatars.githubusercontent.com/u/7713209?s=60&v=4){kind=small}
to throw a clear RazorpayException if an entity class cannot be found, rather than failing with a NullPointerException
- Resolve response parsing errors in shaded/re-packaged environments (razorpay#333) - Update Mockito and Jacoco for modern JDK compatibility - Fix deprecated Mockito matchers in BaseTest
…A actions
- Bump nexus-staging-maven-plugin 1.6.9 -> 1.7.0 to eliminate the
Guice/MissingImplementation WARNING (ObjectMapper annotated with
TypeArguments) during Maven project scanning.
- Correct distributionManagement OSSRH URLs:
- snapshot: /content/repositories/releases/ -> .../snapshots/
- release: /service/local/repositories/releases/content/ ->
/service/local/staging/deploy/maven2/
so nexus-staging owns the staging upload (and snapshots go to the
snapshots repository).
- Bump plugins: maven-gpg-plugin 1.6 -> 3.2.7, maven-source-plugin
3.0.1 -> 3.3.1, maven-javadoc-plugin 3.0.1 -> 3.8.0 for modern
runner and GPG 2.3+ compatibility.
- Update .github/workflows/ci.yml: actions/checkout v2 -> v4,
actions/setup-java v2 -> v4 with distribution=temurin (adopt was
retired in 2021), codecov/codecov-action v3 -> v4. Eliminates the
'Node.js 20 is deprecated' GitHub Actions annotation.
maheshshinde9100
force-pushed
the
fix-latest-pr-bug
branch
from
October 3, 2026 19:02
ccf879e to
4045f18
Compare
Author
|
Hi maintainers, I’ve completed the CI fixes in this PR and verified the changes locally with |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR fixes the Jul 29 publish job failure (v1.4.10 release #362) on two
fronts:
Maven-side (pom.xml):
noisy
Guice/MissingImplementation: ObjectMapper annotated with TypeArguments$ImplicitWARNING on everymvninvocation.points to /snapshots/ (was wrongly /releases/) and the release
repo now uses /service/local/staging/deploy/maven2/ so nexus-staging
owns the staging-upload workflow (was bypassing staging).
for GPG 2.3+ and modern runner compatibility.
GitHub Actions-side (.github/workflows/ci.yml):
(v2 -> v4, distribution=temurin since adopt was retired) in both
the test and publish jobs, removing the "Node.js 20 is deprecated"
runner annotation. Bumps codecov/codecov-action v3 -> v4 (v3 sunset).
Also included: a separate, reviewable feature commit improving
parseResponse error handling and adding RazorpayException tests.
Verified locally:
mvn validateclean (no Guice warnings),mvn testpasses 181/181, effective-pom resolves correct OSSRH URLs.Note: the publish job's remaining
402 Payment Requiredfrom OSSRH is anout-of-band Sonatype credentials/group-promotion issue — no source-code
change can affect it.