-
Notifications
You must be signed in to change notification settings - Fork 896
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
Updating signing tasks to use .NET 6 #25021
Conversation
Pull Request Test Coverage Report for Build 6961800062Warning: This coverage report may be inaccurate.We've detected an issue with your CI configuration that might affect the accuracy of this pull request's coverage report.
💛 - Coveralls |
build/azure-pipelines/darwin/sql-product-build-darwin-signing.yml
Outdated
Show resolved
Hide resolved
Should the STS pipeline also be updated to use this updated signing task? Doesn't look like the STS pipelines are failing yet, but might be good to update those to use the new task too |
Yup, can do. |
I'll proceed to merge, since Product builds have been failing.. |
* Updating signing tasks to EsrpCodeSigning@3 * Updating .NET versions * removing UseDotNet steps * Restoring UseDotNet for linux builds
* Codesign unis000.exe with ESRP client (#25089) * update version to 1.41.3 * Use python 3.11.x in GitHub workflows (#25019) (#25113) * Use python v3.11 for Darwin (#24976) (#25115) Co-authored-by: Lewis Sanchez <87730006+lewis-sanchez@users.noreply.github.com> * Updating signing tasks to use .NET 6 (#25021) (#25160) * Updating signing tasks to EsrpCodeSigning@3 * Updating .NET versions * removing UseDotNet steps * Restoring UseDotNet for linux builds Co-authored-by: Benjin Dubishar <benjin.dubishar@gmail.com> * Use python 3.11 (#24646) * Fix duplicate setup-python in windows ci * change node version back to 16 for github workflows --------- Co-authored-by: Cheena Malhotra <13396919+cheenamalhotra@users.noreply.github.com> Co-authored-by: Lewis Sanchez <87730006+lewis-sanchez@users.noreply.github.com> Co-authored-by: Benjin Dubishar <benjin.dubishar@gmail.com>
Successful run (minus release)