zrhoffman opened a new pull request, #7705:
URL: https://github.com/apache/trafficcontrol/pull/7705

   <!--
   Thank you for contributing! Please be sure to read our contribution 
guidelines: https://github.com/apache/trafficcontrol/blob/master/CONTRIBUTING.md
   If this closes or relates to an existing issue, please reference it using 
one of the following:
   
   Closes: #ISSUE
   Related: #ISSUE
   
   If this PR fixes a security vulnerability, DO NOT submit! Instead, contact
   the Apache Traffic Control Security Team at 
[email protected] and follow the
   guidelines at https://apache.org/security regarding vulnerability disclosure.
   -->
   
   This PR makes the Go components of Traffic Control build using Go version 
1.21 (no `golang.org/x/` dependency updates needed)
   
   See the Go 1.21 [release notes](https://go.dev/doc/go1.21) and 
[milestone](https://github.com/golang/go/milestone/279?closed=1):
   
   > The latest Go release, version 1.21, arrives six months after <a 
href="https://go.dev/doc/go1.20";>Go 1.20</a>. Most of its changes are in the 
implementation of the toolchain, runtime, and libraries. As always, the release 
maintains the Go 1 <a href="https://go.dev/doc/go1compat";>promise of 
compatibility</a>; in fact, Go 1.21 <a 
href="https://go.dev/doc/go1.21#godebug";>improves upon that promise</a>. We 
expect almost all Go programs to continue to compile and run as before.
   
   ## Which Traffic Control components are affected by this PR?
   - Traffic Control Cache Config (`t3c`, formerly ORT)
   - Traffic Control Health Client (tc-health-client)
   - Traffic Control Client <!-- Please specify which (Python, Go, or Java) -->
   - Traffic Monitor
   - Traffic Ops
   - Traffic Stats
   - Grove
   - CDN in a Box - Enroller
   - CI tests for Go components
   - Build system - Go version in builder images
   
   ## What is the best way to verify this PR?
   <!-- Please include here ALL the steps necessary to test your PR.
   If your PR has tests (and most should), provide the steps needed to run the 
tests.
   If not, please provide step-by-step instructions to test the PR manually and 
explain why your PR does not need tests. -->
   Run unit tests and API tests. Since Because of the Go 1 <a 
href="https://go.dev/doc/go1compat";>promise of compatibility</a>, breaking 
changes would be unexpected.
   
   ## If this is a bugfix, which Traffic Control versions contained the bug?
   <!-- Delete this section if the PR is not a bugfix, or if the bug is only in 
the master branch.
   Examples:
   - 5.1.2
   - 5.1.3 (RC1)
    -->
   
   
   ## PR submission checklist
   - [x] Existing tests are sufficient, no additional tests necessary
   - [x] The documentation only mentions the major Go version, no documentation 
updates necessary.
   - [x] The changelog already mentions updating to Go 1.20, no additional 
changelog message necessary.
   - [x] This PR **DOES NOT FIX A SERIOUS SECURITY VULNERABILITY** (see [the 
Apache Software Foundation's security 
guidelines](https://www.apache.org/security/) for details)
   
   <!--
   Licensed to the Apache Software Foundation (ASF) under one
   or more contributor license agreements.  See the NOTICE file
   distributed with this work for additional information
   regarding copyright ownership.  The ASF licenses this file
   to you under the Apache License, Version 2.0 (the
   "License"); you may not use this file except in compliance
   with the License.  You may obtain a copy of the License at
   
       http://www.apache.org/licenses/LICENSE-2.0
   
   Unless required by applicable law or agreed to in writing,
   software distributed under the License is distributed on an
   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
   KIND, either express or implied.  See the License for the
   specific language governing permissions and limitations
   under the License.
   -->
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to