@netlify/build failing to load in Netlify builds

[richardtaylordawson]

Describe the bug

Nothing has changed with any of our applications but builds are continuing to fail all morning since the launch of a new @netlify/builds version yesterday

Steps to reproduce

Run a build in netlify with latest builds package

CLI command and flags

yarn build

Configuration

No response

CLI output

10:02:14 AM: Error message
10:02:14 AM: Plugin exited with exit code 1 and signal null.
10:02:14 AM: The plugin might have exited due to a bug terminating the process, such as an infinite loop.
10:02:14 AM: The plugin might also have explicitly terminated the process, for example with process.exit().
10:02:14 AM: Plugin methods should instead:
10:02:14 AM: - on success: return
10:02:14 AM: - on failure: call utils.build.failPlugin() or utils.build.failBuild()
10:02:14 AM: ​
10:02:14 AM: Plugin details
10:02:14 AM: Package: @netlify/build
10:02:14 AM: Version: 29.42.3
10:02:14 AM: Repository: https://github.com/netlify/build.git
10:02:14 AM: npm link: https://www.npmjs.com/package/@netlify/build
10:02:14 AM: Report issues: https://github.com/netlify/build/issues
10:02:14 AM: ​
10:02:14 AM: Error location
10:02:14 AM: While loading "@netlify/build" from core

Environment

This was in netlify itself and not using the CLI

[richardtaylordawson]

Ran builds for a nextjs application and it worked on 29.42.3

The application its not working on is an old gatsby app

[richardtaylordawson]

If I remove the following from the netlify.toml then builds work:

[[plugins]]
package = "@netlify/plugin-gatsby"

[richardtaylordawson]

Version is: "@netlify/plugin-gatsby": "^3.4.7",

[reilnuud]

We are also experiencing this issue -- is there a way to specify the @netlify/build version so we can roll back?

[richardtaylordawson]

I haven't been able to find a way...let me know if you do @reilnuud :)

[reilnuud]

@richardtaylordawson , no word yet on a way to specify which version to use during build, but support told me they're rolling it back.

This seems to be an issue on our end, our developers are currently working on reverting the change to the @netlify/build version to remedy this. This plugin isn't something you'd typically specify on your end. That should be rolled out shortly, I'll let you know when I have confirmation and you can attempt to re-deploy.

[richardtaylordawson]

Closing this since the Netlify team reverted back the version and builds are working now