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.

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

Bump go from 1.20 to 1.21 in .github/workflows/quickstart_2.0.yml #11927

Merged
merged 4 commits into from
Jan 22, 2025

Conversation

osamaesmailmsft
Copy link
Contributor

@osamaesmailmsft osamaesmailmsft commented Jan 15, 2025

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

  • The toolchain has been rebuilt successfully (or no changes were made to it)
  • The toolchain/worker package manifests are up-to-date
  • Any updated packages successfully build (or no packages were changed)
  • Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
  • Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
  • All package sources are available
  • cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
  • LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
  • All source files have up-to-date hashes in the *.signatures.json files
  • sudo make go-tidy-all and sudo make go-test-coverage pass
  • Documentation has been updated to match any changes to the build system
  • Ready to merge

Summary

What does the PR accomplish, why was it needed?
The workflow Verify Quickstart 2.0 has been failing for an extended period of time, and this change fixes the simple issues.

Change Log
  • Updated the prerequisites in .github/workflows/quickstart_2.0.yml to match those in 2.0's Quickstart README
Does this affect the toolchain?

NO

Test Methodology

@microsoft-github-policy-service microsoft-github-policy-service bot added the 3.0-dev PRs Destined for AzureLinux 3.0 label Jan 15, 2025
@osamaesmailmsft osamaesmailmsft marked this pull request as ready for review January 15, 2025 21:16
@osamaesmailmsft osamaesmailmsft requested a review from a team as a code owner January 15, 2025 21:16
@osamaesmailmsft osamaesmailmsft force-pushed the osamaesmail/fix_quickstart branch 3 times, most recently from da1106e to 510c0e4 Compare January 16, 2025 22:41
@osamaesmailmsft osamaesmailmsft force-pushed the osamaesmail/fix_quickstart branch from fb9c9b2 to 3205e4d Compare January 22, 2025 18:00
@osamaesmailmsft osamaesmailmsft merged commit ff0bfbe into 3.0-dev Jan 22, 2025
15 checks passed
@osamaesmailmsft osamaesmailmsft deleted the osamaesmail/fix_quickstart branch January 22, 2025 22:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3.0-dev PRs Destined for AzureLinux 3.0 Packaging
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants