actionhero just published its new version 14.0.10.
State
Update :rocket:
Dependency
actionhero
New version
14.0.10
Type
dependency
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 actionhero.
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.
Now every connection type/server will default to connection.fingerprint === connection.id unless otherwise specified (AKA: The Web Server). This will ensure that authentication schemes you build should work for all server types.
The example status action which will ship with a newly generated actionhero project has been enhanced to report on memory consumption, requeue queue length, and the node.js process' event loop delay.
This status action is likely not to be appropriate for all deployments, but should serve a good example.
Hello lovely humans,
actionhero just published its new version 14.0.10.
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 actionhero. 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 :sparkles:
You rock!
:palm_tree:
GitHub Release
Fingerprints
connection.fingerprint === connection.id
unless otherwise specified (AKA: The Web Server). This will ensure that authentication schemes you build should work for all server types.Status Action
Packages
should
updated to version^10.0.0
Bugs
The new version differs by 19 commits .
11b6006
return resque queue length
2fcef82
v14.0.10
17a8f9a
Merge pull request #900 from evantahler/fingerprint
0dab5f2
change test output to dots in full suite
ef0b36a
connection.fingerprint = connection.id as a default
b299b8f
spec helper should have fingerprint
d60ab44
fixup event loop delay
3e4f89c
Merge pull request #897 from evantahler/greenkeeper-should-10.0.0
f507f3c
allow more time for status benchmark
34f7813
test for status
f95ba37
chore(package): update should to version 10.0.0
d0ec151
Merge pull request #895 from evantahler/better_status
def9c9d
check on itterations
6552320
do less status actions in the benchmark
3a908ea
variable problem strings
There are 19 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade