SqlCommandReader.IsBeginningOfGo does not cater for whether there is any whitespace after a "go" combination of characters. This version now truncates scripts and fails to deploy where there is a whitespace combination before "go" regardless of what comes after those two characters.

For example, the following is a procedure that got truncated:

CREATE PROCEDURE dbo.GetDetails

    @AccountId uniqueidentifier

AS
BEGIN

SELECT AccountId,
        EstimatedInCents,
        OccupationInCents,
        GovernmentInCents,
-- other statements here

What DbUp executes is this:

CREATE PROCEDURE dbo.GetDetails

    @AccountId uniqueidentifier

AS
BEGIN

SELECT AccountId,
        EstimatedInCents,
        OccupationInCents,