Skip to content

build: Use Gradle credentials system#6467

Merged
oSumAtrIX merged 2 commits intoReVanced:devfrom
validcube:build/gradle-cred
Jan 11, 2026
Merged

build: Use Gradle credentials system#6467
oSumAtrIX merged 2 commits intoReVanced:devfrom
validcube:build/gradle-cred

Conversation

@validcube
Copy link
Member

@validcube validcube commented Jan 8, 2026

Switch to PasswordCredentials when during authentication with ghcr

nts:

githubPackagesUsername=
githubPackagesPassword=

List of what repository have PR submitted see: ReVanced/revanced-manager-downloaders-template#16 (comment)

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This pull request modernizes the Gradle credentials system by switching from explicit credential configuration to Gradle's built-in PasswordCredentials system for GitHub Packages authentication.

Key Changes:

  • Replaced explicit credential blocks with credentials(PasswordCredentials::class) in build scripts
  • Updated GitHub Actions workflows to use ORG_GRADLE_PROJECT_* environment variables
  • Simplified credential management across both plugin management and publishing repositories

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File Description
settings.gradle.kts Replaced explicit credential block with PasswordCredentials for plugin repository
patches/build.gradle.kts Replaced explicit credential block with PasswordCredentials for publishing repository
.github/workflows/release.yml Updated to use ORG_GRADLE_PROJECT environment variables instead of GITHUB_TOKEN
.github/workflows/build_pull_request.yml Updated to use ORG_GRADLE_PROJECT environment variables instead of GITHUB_TOKEN

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@rospino74
Copy link
Contributor

Please also update the setup docs so we know how to use this new method

thanks!

@validcube
Copy link
Member Author

validcube commented Jan 9, 2026

Please also update the setup docs so we know how to use this new method

thanks!

Whoops, I forgotten about that completely. I'll quickly write it for documentation in a bit.

Quick remedy for now you can use this breaking change advisory that I sent to the team.

Team notice 0801 (updated: 0901)

Hiiiiii

⚠️ This is just a notice only, will only be applied once all the PRs of the new system have been merged: ReVanced/revanced-manager-downloaders-template#16 (comment)

New changes in build configuration that change the credentials system of ReVanced, ReVanced Gradle Credentials based system.

To make sure that you weren't affected, (if not already) create gradle.properties in Gradle User Home directory. (~/.gradle/gradle.properties or C:\Users\%USERNAME%\.gradle\gradle.properties) with this configuration.

githubPackagesUsername=LabubuCrusher
githubPackagesPassword=ghp_PopmartDestory

Migration

In Global properties at Gradle User Home directory gradle.properties:

  • Replace gpr.user with githubPackagesUsername
  • Replace gpr.key with githubPackagesPassword

Diff

- gpr.user=LabubuCrusher
- gpr.key=ghp_PopmartDestory
+ githubPackagesUsername=LabubuCrusher
+ githubPackagesPassword=ghp_PopmartDestory

@oSumAtrIX oSumAtrIX merged commit 004b590 into ReVanced:dev Jan 11, 2026
1 check passed
xehpuk pushed a commit to xehpuk/revanced-patches that referenced this pull request Jan 13, 2026
oSumAtrIX pushed a commit that referenced this pull request Feb 12, 2026
oSumAtrIX pushed a commit that referenced this pull request Feb 27, 2026
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.

4 participants