Update liquid-fire to version 0.25.0 🚀 #69
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
|
Changes Unknown when pulling e95a6a9 on greenkeeper-liquid-fire-0.25.0 into * on master*. |
1 similar comment
|
Changes Unknown when pulling e95a6a9 on greenkeeper-liquid-fire-0.25.0 into * on master*. |
|
Changes Unknown when pulling 68b6fa8 on greenkeeper-liquid-fire-0.25.0 into * on master*. |
|
👍 |
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.
PATCH
Hello lovely humans,
liquid-fire just published its new version 0.25.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 liquid-fire.
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!
🌴
The new version differs by 23 commits .
bf10338releasing 0.25.0d567531changelog11373d7beta allowed to fail for the momentd33af55canary has glimmer2 now, so dropping alphabdaa7b9Merge pull request #493 from kellyselden/patch-1381108cadd travis badge1565161Merge pull request #491 from kellyselden/sinoneca37cfreplace vendor/sinon with ember-sinon3829873Update ember-try.js27eba9dMerge branch 'update-qunit'9415724Updating tests for compatibility with newest ember-cli-qunit14cab61Merge pull request #487 from cibernox/fix_memory_leak16b16e9Fix memory leak03a9009Merge pull request #486 from GavinJoyce/gj/update-ember-cli-htmlbars-inline-precompile56b245eupdate ember-cli-htmlbars-inline-precompile to remove warningsThere are 23 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? ⚡
greenkeeper upgrade