Open greenkeeper[bot] opened 7 years ago
Update to this version instead 🚀
The new version differs by 5 commits ahead by 5, behind by 2.
fef4b14
Chore: Release 1.0.0 🎉 (#820)
2093fff
Chore: remove support for node 0.12 and some unused deps (#825)
5fbaa1d
Chore: remove filed
as unused dependency (#821)
c9d0a91
refactor(*): remove dashboard and clientlib from deployd core module (#783)
626d4ad
refactor: remove dpd cli from deployd core module (#776)
See the full diff
Update to this version instead 🚀
The new version differs by 7 commits.
a85f936
Bump to v1.1.0
7a31f90
Merge branch 'master' of github.com:deployd/deployd
aafd3fc
Update readme with some best practices (#833)
4d22465
Allow specifying resources in subdirectories/namespaces. (eg. namespace/hello) (#832)
acfa194
Merge branch 'master' of github.com:deployd/deployd
4331b3c
fix(tests): run tests on random mongo port and update for new mocha/npm (#831)
c057bca
fix(tests): run tests on random mongo port and update for new mocha/npm versions
See the full diff
Update to this version instead 🚀
The new version differs by 4 commits ahead by 4, behind by 4.
d9c31fa
chore(release): 1.1.1
4435a57
fix(internal-resources): namespaced resources could not be moved/renamed into other namespaces (#837)
93f4c0e
fix(tests): improve a minor race condition in a test (#835)
c4397a5
Chore: Release 1.1.0 (#834)
See the full diff
dependency
deployd was updated from 0.8.9
to 1.1.3
.Update to this version instead 🚀
The new version differs by 5 commits ahead by 5, behind by 1.
684b596
chore(release): 1.1.3
e351a03
chore: update and pin dependencies (#874)
df72ffe
Doc: add maintainance warning on README (#872)
e838a3e
Fix big numbers being parsed into integers when it wasn't safe to do so (#873)
ffea84b
chore(release): 1.1.2 (#854)
See the full diff
dependency
deployd was updated from 0.8.9
to 1.2.0
.
Version 0.8.10 of deployd just got published.
The version 0.8.10 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 deployd. 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 14 commits.
5932bfa
Chore: prepare release of 0.8.10
1514b8d
Fix: Force mime version v1.4.0 (#823)
ce04dde
fix: add socketIo check (#802)
5e2c781
fix(internal-client): add req.resume() (#785)
a9fdc4c
fix(collection): protect and hide should not modify
this
(#782)4f3f7ce
Chore: Test on TravisCI with node 7 (#784)
04bb24a
fix: server.attach() did not enable socket clustering (#777)
6a9ac0f
Chore: Add template for issues and PR (#780)
8e6e387
Chore: Remove windows installer from readme (#772)
5f78c08
correct extreme uses of hide() and protect() (#708)
4604626
Added require to the script context (#757)
01cb6c8
Doc: Improve contribution documentation (#760)
08dab9c
feat(collection): Add Date type (#759)
6803934
chore: Update bluebird to v3.4.3 (#752)
See the full diff
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: