-
Notifications
You must be signed in to change notification settings - Fork 18
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.
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
♻️🚇 Use GITHUB_OUTPUT instead of set-output in github actions #1166
Conversation
Benchmark is done. Checkout the benchmark result page. Benchmark diff v0.6.0 vs. mainParametrized benchmark signatures: BenchmarkOptimize.time_optimize(index_dependent, grouped, weight)
Benchmark diff main vs. PRParametrized benchmark signatures: BenchmarkOptimize.time_optimize(index_dependent, grouped, weight)
|
Codecov ReportBase: 87.6% // Head: 87.6% // No change to project coverage 👍
Additional details and impacted files@@ Coverage Diff @@
## main #1166 +/- ##
=====================================
Coverage 87.6% 87.6%
=====================================
Files 103 103
Lines 4899 4899
Branches 807 807
=====================================
Hits 4292 4292
Misses 489 489
Partials 118 118 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
Kudos, SonarCloud Quality Gate passed! |
Ooops initially wanted to open the PR against my fork for testing 😅 |
GitHub deprecated the usage of
set-output
in favor of using the environment file located at$GITHUB_OUTPUT
.The old syntax already gives warnings and will be switched off 31st May 2023.
This change makes the CI more future proof.
Ref.: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Change summary
Checklist