Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Emit deprecation warnings when using deprecated inputs / actions #108

Closed
bigdaz opened this issue Apr 4, 2024 · 0 comments · Fixed by #139
Closed

Emit deprecation warnings when using deprecated inputs / actions #108

bigdaz opened this issue Apr 4, 2024 · 0 comments · Fixed by #139
Assignees
@bigdaz
Labels
enhancement New feature or request
Milestone
v3.3

Comments

@bigdaz
Copy link
Member

bigdaz commented Apr 4, 2024 •
edited

We should emit deprecation warnings when using:

  • gradle-build-action
  • setup-gradle multiple times in a Job (or after a dependency-submission step)
  • arguments and build-root-directory input for actions/setup-gradle (and gradle-build-action)
  • build-scan-terms-of-service-url and build-scan-terms-of-service-agree.

For each of these, we should link to an "upgrade guide" that gives an example of the replacement.
@bigdaz bigdaz added the enhancement New feature or request label Apr 4, 2024
@bigdaz bigdaz self-assigned this Apr 9, 2024
@bigdaz bigdaz mentioned this issue Apr 9, 2024
Merged
bigdaz added a commit that referenced this issue Apr 9, 2024
@bigdaz
Emit warnings when using deprecated inputs / actions (#139)
1824c01 
Fixes #108
@bigdaz bigdaz added this to the v3.3 milestone Apr 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bigdaz bigdaz

Labels
enhancement New feature or request
Projects
None yet
Milestone
v3.3
Development

Successfully merging a pull request may close this issue.

Emit warnings when using deprecated inputs / actions gradle/actions
1 participant
@bigdaz