What version of Next.js are you using?

10.0.8

What version of Node.js are you using?

14

What browser are you using?

N/A

What operating system are you using?

macOS

How are you deploying your application?

N/A

Describe the Bug

When enabling webpack5 in next.config.js (future: { webpack5: true }), the serverless target does not build and results in errors for eve

The fix described in issue #20179 introduces a regression, especially from an accessibility perspective. When declaring an empty alt-attribute for an image using the keyword GATSBY_EMPTY_ALT in markdown (![GATSBY_EMPTY_ALT](rel/path.jpg) and having set showCaptions: true in the plugin-options in gatsby-config.js, the plugin produces unwanted HTML:

<figure class="gatsby-resp-i

请不要直接在 issues 提交安全漏洞报告，目前已有一部分人正在使用该系统，你的公开提交很可能影响到他们的资料安全。

所以拜托以后直接发送安全漏洞信息到 hi@halo.run 谢谢！

Describe the bug

GitHub provides a few options when configuring a new repo like: license, .gitignore file, a README.md, and the Rennovate plugin. If you want to install any of these by default, which I usually do, then you get an error about the remote having newer content.

To Reproduce
Steps to reproduce the behavior:

1. Create a repo with a readme during the script
2. See the er