@Bo98 what is the best way to re-trigger the builds? seems like failed downloads were the error.

Done

seems like the failures are

• auditbeat
• berglas
• charm
• dashing
• docker2aci
• packetbeat
• wellington
• ship

@SMillerDev and @Bo98 do we need to go fix these packages first? what are the steps we follow now?

If these are broken by the update they need to be reported and fixed.

@SMillerDev afaik, they have been or are broken. wellington is an example that has been broken since 10.13.

dashing has a https cert error (this is new, but is unrelated to go 1.14.6)

Looks like the Catalina build didn't complete.

There's also a merge conflict anyway. Can you rebase on master?

@Bo98 done. before we triggered a restart Catalina did finish and it was the same packages.

Merged master after fixing conflicts, hopefully we should have all builds complete with ~the same errors

Please don't introduce merge commits. We keep our log to one commit per formula. If you want the newest changes you'll have to rebase.

@SMillerDev updated.

curious: any reason why we don't use "squash and merge" so that even if a PR has multiple commits, history is linear? Im guessing because of the build pipeline, but want to double check

Bottle commits like 8c9d754 wouldn't get applied if we used GitHub's merge button.

Failing formulae:

• auditbeat
• berglas
• charm
• dashing
• gobuster
• grv
• heartbeat
• packetbeat
• ship
• wellington

I'm going to see which of them are existing issues and see if we can send fixes to the repos. @Bo98, curious if you know where we are painting the list of broken golang reps, the issue seems to be closed?

@roopakv previous upgrade failure tracker, #56539

What should be done to make go 1.14.6 available for upgrade?
What should be done to decrease time needed to prepare a new release?

Fix the build issues to get this migrated faster, and make sure that projects dependent on go have proper CI that'll catch these issues.

Hi, sorry for the delay in responding here - I've been less active this week.

@Bo98, curious if you know where we are painting the list of broken golang reps, the issue seems to be closed?

I believe #56539 is being used now.

I'll make this a priority to review tomorrow evening. I think it would be worthwhile rebasing in the meantime until then so I'm not reviewing unrelated breakages which have already been fixed.

@Bo98 seems like godep is archived: https://github.com/tools/godep

do we remove godep in a separate PR? brew says there is a problem since repo is archived.

You can mark it deprecated with a date in this one.

@SMillerDev is that as simple as adding

deprecate! date: "2020-07-28"

to the formula?

when i try running brew audit Formula/godep.rb i never see the github error. i tried updating brew and running with debug, seems like that check is always skipped. what am i missing?

Yeah, although it should be the date that it was archived. brew audit --online will show this (since it needs to connect to github)

@SMillerDev yeah i tried with --online and still no dice. not sure what i am missing

Did you already mark it as deprecated? Because it will be skipped if you do. Otherwise you have something making brew audits ignore --online

Thanks. I've gone through all that failed and have matched them up with existing issues or PRs, bar a couple which I'll open a separate PR to fix shortly.

Typically we do one commit per formula:

• go 1.14.6
• godep: revision bump for go

I've done that for you while merging.

Merged as 33b25d5 and cf7ad55.

thanks @Bo98 I'll keep that in mind for the future. I just copied what we did for 1.14.5