Open
Conversation
This file contains hidden or 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
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.
Hello lovely humans,
lost just published its new version 8.0.0.
This version 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 lost.
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.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project ✨
You rock!
🌴
GitHub Release
[v8.0.0] - 2016-12-31
Fixed
lost-alignwas targeting the incorrect element when using flexbox.Changed
lost-wafflelast element in a row is floated. Before, the last element in a row would be floated right where everything else would float left. This is typically with row based grids, however when using the waffle grid it was a bit strange. This now allows for a param to be used instead if you want the last element to float right and all elements floating left is default.Added
masterbranch a warning was added for older versions of Node.JS so that there could be a notification for those using older version that it was being dropped in LostGrid version 8. This is included in this release but will probably be removed by the time this is merged intomaster.@ rounder [insert percent here]or you can do it on the local level withlost-column-rounder: 100rule.Removed
LostGrid Infrastructure
Diff with previous major version 7.1.1
The new version differs by 151 commits .
396d6bdMerge pull request #353 from peterramsing/release/v87b66527Adds getting started to READMEab5785dupdates link in Changelogb0d04f2Version Bump 🚀3222098Updates the Node Support noted6cdf79Changes spelling of changelog [ci skip]4d98344Merge branch 'master' into release/v8f41a541Updates PostCSS version343ec9bAdjusts changelog for new version18e8603Updates dependencies974faedUpdates Changelog with the rc [ci skip]db280f9Merge pull request #352 from peterramsing/rtl-support9bfaa24Adds a prefix as it's going to be in beta in the v8 launchb9dea38Not yet to support older versions of node...df979ceAdds test script explicitly to TravisThere are 151 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? ⚡
greenkeeper upgrade