Revert "Merge pull request #1780 from cloudfoundry/use-goversion-latest" #1781
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This reverts commit e635384, reversing changes made to ee6c75b.
Are you submitting this PR against the develop branch?
What is this change about?
WIth ths pr #1780 it Updated all Golang assets to use the latest available version. But this latest feature which is merge via this cloudfoundry/go-buildpack#524 made to the go buildpack source repo but no to the release. We have to wait until we have latest go-buildpack release.
Also It's unclear for us when a new go-buildpack-release will be available!
Now the run-cats-vm job is red in order to unblock it we have to revert that commit.
Please provide contextual information.
Include any links to other PRs, stories, slack discussions, etc... that will help establish context.
What version of cf-deployment have you run this cf-acceptance-test change against?
#1780
Please check all that apply for this PR:
Did you update the README as appropriate for this change?
How many more (or fewer) seconds of runtime will this change introduce to CATs?
N/A
What is the level of urgency for publishing this change?
Tag your pair, your PM, and/or team!