beam-australia / react-env / 6a10d4f9e10cd5b4824a8a82c8069c7759d2e225

95%

Build Type

Pull #84

drone

Committed by dependabot[bot]

Commit Message

Bumps [next](https://github.com/vercel/next.js) from 10.0.7 to 11.1.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/vercel/next.js/releases">next's releases</a>.</em></p>
<blockquote>
<h2>v11.1.0</h2>
<p>A security team from one of our partners noticed an issue in Next.js that allowed for an open redirect to occur.</p>
<p>Specially encoded paths could be used when <code>pages/_error.js</code> was statically generated allowing an open redirect to occur to an external site.</p>
<p>In general, this redirect does not directly harm users although can allow for phishing attacks by redirecting to an attacker's domain from a trusted domain.</p>
<p>We recommend upgrading to the latest version of Next.js to improve the overall security of your application.</p>
<h2>How to Upgrade</h2>
<ul>
<li>We have released patch versions for both the stable and canary channels of Next.js.</li>
<li>To upgrade run <code>npm install next@latest --save</code></li>
</ul>
<h2>Impact</h2>
<ul>
<li><strong>Affected:</strong> Users of Next.js between 10.0.5 and 10.2.0</li>
<li><strong>Affected:</strong> Users of Next.js between 11.0.0 and 11.0.1 using <code>pages/_error.js</code> without <code>getInitialProps</code></li>
<li><strong>Affected:</strong> Users of Next.js between 11.0.0 and 11.0.1 using <code>pages/_error.js</code> and <code>next export</code></li>
<li><strong>Not affected</strong>: Deployments on Vercel (<a href="https://vercel.com">vercel.com</a>) are not affected</li>
<li><strong>Not affected:</strong> Deployments <strong>with</strong> <code>pages/404.js</code></li>
</ul>
<p>We recommend everyone to upgrade regardless of whether you can reproduce the issue or not.</p>
<h3>How to Assess Impact</h3>
<p>If you think sensitive code or data could have been exposed, you can filter logs of affected sites by <code>//</code> (double slash at the start of the url) followed by a domain.</p>
<h2>What is Being Done</h2>
<p>As Next.js has grown in pop

Pull Request Pull Request #84:

Run Details

35 of 38 branches covered (92.11%)

Branch coverage included in aggregate %.

54 of 56 relevant lines covered (96.43%)

36.38 hits per line