[pmathew92]

Changes

Reverts #1131 so 5.0.0-beta.3 can be released again through a new release PR.

The release pipeline for #1131 never published:

• The first run failed in rl-scanner because the runner's default JDK 25 can't run Gradle 8.11.1. chore(ci): set up JDK 17 in the rl-scanner release job [non-main] #1133 fixed that.
• A manual workflow_dispatch on v5_development then got past the build but failed in Run RL Scanner, because the scanner's AWS OIDC role does not accept dispatches from that branch.

Merging a release/* PR is the trigger the role accepts, so the plan is to revert the version bump here and re-raise it as a new release/5.0.0-beta.3 PR.

This PR changes:

• .version: 5.0.0-beta.3 back to 5.0.0-beta.2
• CHANGELOG.md: removes the 5.0.0-beta.3 section
• README.md: install snippet back to 5.0.0-beta.2

Merging this does not trigger a release, since the branch is not release/*. No SDK code changes.

References

• Original release PR: Release 5.0.0-beta.3 #1131
• JDK fix: chore(ci): set up JDK 17 in the rl-scanner release job [non-main] #1133
• Failed release run (JDK 25): https://github.com/auth0/Auth0.Android/actions/runs/42964608762
• Failed manual dispatch (OIDC): https://github.com/auth0/Auth0.Android/actions/runs/42967938430

Testing

Release metadata only. The follow-up release PR re-applies the same three changes and runs the release pipeline on merge.

• This change adds unit test coverage

• This change adds integration test coverage

• This change has been tested on the latest version of the platform/language or why not

Checklist

• I have read the Auth0 general contribution guidelines

• I have read the Auth0 Code of Conduct

• All existing and new tests complete without errors

🤖 Generated with Claude Code

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts