Update libcluster 3.3.1 → 3.3.3 (patch) #32
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.
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ libcluster (3.3.1 → 3.3.3) · Repo · Changelog
Commits
See the full diff on Github. The new version differs by 25 commits:
release: 3.3.3
chore: update deps
test: add test to verify gossip strategy starts
docs: add a note about starting epmd w/local epmd strategy
Add new Digital Ocean Droplet strategy to readme (#192)
Improve the moduledocs of Kubernetes related strategies (#185)
Allow Epmd strategy to reconnect after connection failures (#183)
Detect Self Signed Certificate Authority for Kubernetes Strategy (#194)
Fix usage of deprecated Logger.warn/2 (#195)
ci: update build matrix
release v3.3.1
Add Linux reuse port (#187)
chore: update badges
fix: broken test due to logger output changes
fix: remove explicit applications list
ci: update build matrix
fix: remove config folder
chore: fix formatting
Add `namespace` to Doc Example for DNSSRV (#172)
Add_membership should use the supplied if address. (#165)
update documentation for k8s strategy (#169)
Update CHANGELOG with changes multicast address (#171)
fix: source link error (#166)
version 3.3.1
- Use :aes_256_cbc instead of retired :aes_cbc256 cypher name (#161)
✳️ jason (1.3.0 → 1.4.0) · Repo · Changelog
Release Notes
1.4.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 8 commits:
Release 1.4.0
Bump bench deps
Bump CI versions
Bump deps
Use float_to_binary [:short] if available
Bump OTP version in GitHub Actions (#153)
Update README.md (#152)
fix release year (#146)
👉 No CI detected
You don't seem to have any Continuous Integration service set up!
Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.
This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:
* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Github Actions](https://docs.github.com/actions) are all excellent options. * If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github. * If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with `depfu/`.Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands