Update serve to the latest version 馃殌 #231
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![greenkeeper[bot]](https://avatars.githubusercontent.com/in/505?s=60&v=4){kind=small}
Version 6.0.2 just got published. |
Version 6.0.3 just got published.Update to this version instead 馃殌 Release Notes6.0.3Patches
CreditsHuge thanks to @albertstill for his help! CommitsThe new version differs by 8 commits.
See the full diff |
Version 6.0.4 just got published.Update to this version instead 馃殌 Release Notes6.0.4Patches |
Version 6.0.5 just got published. |
Version 6.0.6 just got published.Update to this version instead 馃殌 Release Notes6.0.6Patches |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Version 6.0.1 of serve just got published.
The version 6.0.1 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of serve.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Commits
The new version differs by 22 commits.
267bbb36.0.1c16c721Shorter error message for missing authentication flags0234ba4Fixed custom 404 pages (#218)dae446eImproved syntax for determining port6655ed6Better default caching for single page applications2e53727Prettified remaining code0c4e536ConvertPORTenvironment variable to integer (#242)4c3c733Prettified everythingbac0fd9Bumped dependencies to the latest version79a0b5dchore(package): update husky to version 0.14.2 (#241)4668cd6fix(package): update chalk to version 2.0.0 (#238)1ed2159chore(package): update prettier to version 1.5.2 (#236)0cf2f01chore(package): update prettier to version 1.5.1 (#235)f333a83chore(package): update prettier to version 1.5.0 (#234)54278bcUpdated description to reflect current stateThere are 22 commits in total.
See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 馃尨