Closed greenkeeper[bot] closed 5 years ago
devDependency
ember-cli-mirage was updated from 0.4.1
to 0.4.11
.Update to this version instead π
Bug fixes from 0.4.10, and some new deprecations around previously undocumented behavior.
Update notes
Changes
The new version differs by 5 commits.
64599b6
v0.4.11
8999b24
fix: normalizedRequestAttrs takes a dasherized model name
3d30014
fix: revert 4.10 factory lookup behavior, add warning
ab74691
[closes #1370] Fix falsy responses
acf8ed0
TravisCI: Remove deprecated sudo: false
option
See the full diff
devDependency
ember-cli-mirage was updated from 0.4.1
to 0.4.12
.Update to this version instead π
Improve automatic response type setting.
Update notes
Changes
devDependency
ember-cli-mirage was updated from 0.4.1
to 0.4.13
.Update to this version instead π
Update notes:
#1466 changed some existing behavior that I expect almost no one to be relying upon, but I could be wrong.
For no particular reason, when we originally coded the Db we had it sort new records by the id
field.
This means if you had fixture files like
[
{ id: 2, name: 'Yehuda' },
{ id: 1, name: 'Tom' }
]
they would end up in Mirage's Db as [ { id: 1, name: 'Tom' }, { id: 2, name: 'Yehuda' } ]
.
We've changed this behavior so records are just added to the Db in the order they were at insertion time.
The only way this could affect your app or tests is if you are doing something like return schema.users.all()
, and you're relying on the order of that response, and the source data is unsorted. (In general, if you're relying on an order, it's best practice for your query and/or route handler to specify that sort order with e.g. schema.users.sort((a, b) => b.title < a.title })
).
I expect this undocumented behavior to not be something anyone is relying on. Please let me know if I'm wrong!
The new version differs by 50 commits.
848f5f0
v0.4.13
be23f53
docs: clarify default server-side nested includes
ffc437c
docs: clarify how to override timing in tests
3da8d67
docs: add note for prettier users
044a831
doc: fix app/mirage references
17e30fb
doc: update normalizedRequestAttrs
20d9d84
Fix: db doesn't automatically sort new records
603ca7f
Update ember-cli-addon-docs
0574fc1
Add simple homepage copy
ba2d539
Merge pull request #1460 from carlbennettnz/patch-2
e053bdd
Set the dummy app's <title> to 'EmberCLI Mirage'
743d67f
Remove logs
8a327bc
Try different redirect logic
c2cbef0
Add redirects to old docs sites
3c6fd35
Empty rootUrl
There are 50 commits in total.
See the full diff
devDependency
ember-cli-mirage was updated from 0.4.1
to 0.4.14
.devDependency
ember-cli-mirage was updated from 0.4.1
to 0.4.15
.Update to this version instead π
View all commits: v0.4.14...master
The new version differs by 34 commits.
bf4ac5a
v0.4.15
9996c02
Merge pull request #1518 from samselikoff/dependabot/npm_and_yarn/stringstream-0.0.6
d406693
Merge pull request #1516 from samselikoff/dependabot/npm_and_yarn/sshpk-1.16.1
ad5bc12
Merge pull request #1515 from samselikoff/dependabot/npm_and_yarn/mixin-deep-1.3.1
437c140
Merge pull request #1513 from samselikoff/dependabot/npm_and_yarn/merge-1.2.1
2139b3a
Merge pull request #1511 from samselikoff/dependabot/npm_and_yarn/handlebars-4.1.0
eda52f8
Merge pull request #1509 from samselikoff/dependabot/npm_and_yarn/extend-3.0.2
f0f897d
Merge pull request #1508 from samselikoff/dependabot/npm_and_yarn/atob-2.1.2
b97914b
build(deps): [security] bump stringstream from 0.0.5 to 0.0.6
af0d7f6
build(deps): [security] bump sshpk from 1.13.1 to 1.16.1
f3a91fa
build(deps): [security] bump mixin-deep from 1.3.0 to 1.3.1
efe8582
build(deps): [security] bump merge from 1.2.0 to 1.2.1
c654d4e
build(deps): [security] bump handlebars from 4.0.11 to 4.1.0
4c762b0
build(deps): [security] bump extend from 3.0.1 to 3.0.2
a22c64a
build(deps): [security] bump atob from 2.0.3 to 2.1.2
There are 34 commits in total.
See the full diff
devDependency
ember-cli-mirage was updated from 0.4.1
to 1.0.0
.devDependency
ember-cli-mirage was updated from 0.4.1
to 1.1.0
.
The devDependency ember-cli-mirage was updated from
0.4.1
to0.4.10
.This version 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.
Find out more about this release.
FAQ and help
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).Your Greenkeeper bot :palm_tree: