Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bumped dependencies to the latest version #468

Merged
merged 1 commit into from
Aug 21, 2018
Merged

Bumped dependencies to the latest version #468

merged 1 commit into from
Aug 21, 2018

Conversation

leo
Copy link
Contributor

@leo leo commented Aug 21, 2018

This introduces version 5.0.0 of serve-handler, so we need this to be a major release.

@leo leo added the major label Aug 21, 2018
@leo leo requested a review from timneutkens August 21, 2018 18:00
@leo leo merged commit 1cbb5ec into master Aug 21, 2018
@leo leo deleted the upgrade branch August 21, 2018 18:06
durancristhian pushed a commit to durancristhian/futbol that referenced this pull request Aug 26, 2018

## Version **10.0.0** of **serve** was just published.

<table>
  <tr>
    <th align=left>
      Dependency
    </th>
    <td>
      <a target=_blank href=https://github.com/zeit/serve>serve</a>
    </td>
  </tr>
  <tr>
      <th align=left>
       Current Version
      </th>
      <td>
        9.6.0
      </td>
    </tr>
  <tr>
    <th align=left>
      Type
    </th>
    <td>
      dependency
    </td>
  </tr>
</table>



The version **10.0.0** is **not covered** by your **current version range**.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

It might be worth looking into these changes and trying to get this project onto the latest version of serve.

If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.


---


<details>
<summary>Release Notes</summary>
<strong>10.0.0</strong>

<h3>Major Changes</h3>
<ul>
<li>Bumped dependencies to the latest version: <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="352648752" data-permission-text="Issue title is private" data-url="vercel/serve#468" href="https://urls.greenkeeper.io/zeit/serve/pull/468">#468</a></li>
</ul>
</details>

<details>
<summary>Commits</summary>
<p>The new version differs by 2 commits.</p>
<ul>
<li><a href="https://urls.greenkeeper.io/zeit/serve/commit/254432fbd01e41e563ea9315244fae0834041be6"><code>254432f</code></a> <code>10.0.0</code></li>
<li><a href="https://urls.greenkeeper.io/zeit/serve/commit/1cbb5ec274c3142b8736b37a2db7ddcc052562b2"><code>1cbb5ec</code></a> <code>Bumped dependencies to the latest version (#468)</code></li>
</ul>
<p>See the <a href="https://urls.greenkeeper.io/zeit/serve/compare/089d71c33d86d835ad057461984a2eea53a4728e...254432fbd01e41e563ea9315244fae0834041be6">full diff</a></p>
</details>

<details>
  <summary>FAQ and help</summary>

  There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).
</details>

---


Your [Greenkeeper](https://greenkeeper.io) bot 🌴
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants