Skip to content

Conversation

@MGaetan89
Copy link
Contributor

Pull request

Description

This PR removes secrets from public workflows (those who run on PR). It also updates Gradle to 8.12.1 and removes the build step from the quality.yml workflow.

Changes made

  • Replace secrets.GITHUB_TOKEN with github.token. Both are equivalent, but using github.token shows that it's not a custom secret.
  • Remove secrets.GRADLE_CACHE_ENCRYPTION_KEY from the gradle/actions action. It means that we will cache slightly less data, but it probably won't have a big impact on build time.
  • Remove the build step from the quality.yml workflow. This probably had no significant advantage in terms of performance. So now each step is independent.
  • Update to Gradle 8.12.1. The release notes are available here.

Checklist

  • APIs have been properly documented (if relevant).
  • The documentation has been updated (if relevant).
  • New unit tests have been written (if relevant).
  • The demo has been updated (if relevant).

@MGaetan89 MGaetan89 requested a review from StaehliJ February 18, 2025 10:06
@MGaetan89 MGaetan89 self-assigned this Feb 18, 2025
@github-actions
Copy link

Code Coverage

Overall Project 51.13% 🟢

There is no coverage information present for the Files changed

@MGaetan89 MGaetan89 added this pull request to the merge queue Feb 18, 2025
Merged via the queue into main with commit 415b4b2 Feb 18, 2025
8 checks passed
@MGaetan89 MGaetan89 deleted the gradle_8.12.1_update_workflow branch February 18, 2025 16:29
MGaetan89 added a commit that referenced this pull request Mar 4, 2025
In #899, the `cache-encryption-key` argument was removed from the `gradle/actions/setup-gradle` action in order to avoid using secrets.
However, this secrets is optional: if the value is not provided, the cache won't be read or updated.
This means that PRs created from the main repository will take advantage of Gradle's Configuration Cache, while PRs from forks won't.
MGaetan89 added a commit that referenced this pull request Mar 4, 2025
In #899, the `cache-encryption-key` argument was removed from the `gradle/actions/setup-gradle` action to avoid using secrets.
However, this secret is optional: if the value is not provided, the cache won't be read or updated.
This means that PRs created from the main repository will take advantage of Gradle's Configuration Cache, while PRs from forks won't.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: ✅ Done

Development

Successfully merging this pull request may close these issues.

2 participants