chore(sdk): sync Java SDK v12.0.0-rc.1 - #23
Merged
giriraj12000 merged 7 commits intoSep 22, 2026
Merged
giriraj12000 merged 7 commits into
giriraj12000 merged 7 commits into
Conversation
added 4 commits
September 17, 2026 17:36
Generated output — do not edit this repository by hand; change the factory and re-sync, or the next run will overwrite it. factory commit: 3a42f20 (clean) sdk version: 12.0.0-rc.1 generator: v7.10.0 spec: spec/LoginRadius-Public-APIs.yaml
Adds .github/workflows/{ci.yml,release.yml}, now generated by SDK-FACTORY from
languages/java/static/.github/workflows/ rather than hand-maintained per repo.
CI builds, tests and lints this SDK on push and pull request, using the same
commands the factory's own verify gate runs. Release publishes from a v* tag
only, behind a 'release' GitHub Environment that should be configured with
required reviewers before the first tag.
The pre-factory workflows are removed where they existed: they built paths the
v12 tree no longer has (dot-net-sdk: Source/LoginRadiusSDK.V2/, java-sdk:
LoginRadius-JavaSDK/pom.xml) and published on every push to master.
factory commit: 3a42f20 (DIRTY — generated from uncommitted factory changes)
The workflow comments referenced internal tooling paths and repository names that do not belong in a public repository. The steps themselves are unchanged.
Generated file headers, code comments and documentation referenced internal tooling names and paths that do not belong in a public repository. They now name the LoginRadius SDK generator without pointing at internal locations. No functional change: only comments, headers and documentation text differ. The 'Code generated ... DO NOT EDIT.' header keeps the form the Go toolchain recognises, so generated files are still detected as generated.
hemant404
changed the title
added 3 commits
September 21, 2026 15:27
Maven Central refuses a bundle without a -javadoc.jar. The javadoc execution is now part of the sign-artifacts profile, so a release build produces it while an ordinary `mvn package` still does not. It is bound to `package` because maven-gpg-plugin signs at `verify` — an artifact attached later would ship unsigned, which Central also rejects.
maven-jar-plugin's excludes do not propagate to maven-source-plugin or maven-javadoc-plugin, so the sources and javadoc jars shipped demo and example code while the main jar was clean. Each plugin now carries its own exclusion (javadoc by package name, since that is how it filters). Also drops the test-jar: it was attached, and an attached artifact is deployed, so Maven Central would have received it. Nothing consumes it. A release now publishes the three artifacts Central expects, all free of demo and example code.
A comment in DemoServer described where demo.css comes from in terms of internal tooling that does not exist from this repository's point of view.
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
2 participants
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.
Automated sync of the generated LoginRadius Java SDK.
12.0.0-rc.1v7.10.0LoginRadius-Public-APIs.yamlEverything in this repository is generated output, including
.github/workflows/. Fix a problem at the source and regenerate — edits madehere are overwritten by the next sync.
ci.ymlbuilds, tests and lints this SDK on every push and pull request.release.ymlpublishes only from av*tag, behind areleaseGitHubEnvironment that must be configured with required reviewers before the first
tag is pushed.