Bump github.com/nats-io/gnatsd from 1.2.0 to 1.4.1
Bumps github.com/nats-io/gnatsd from 1.2.0 to 1.4.1.
Release notes
Sourced from github.com/nats-io/gnatsd's releases.
Release v1.4.1
Changelog
Go Version
- 1.11.5: Both release executables and Docker images are built with this Go release.
Fixed
- Possible delay in flushing data (#901)
Complete Changes
https://github.com/nats-io/gnatsd/compare/v1.4.0...v1.4.1
Release v1.4.0
Changelog
Go Version
- 1.11.4: Both release executables and Docker images are built with this Go release.
Added
- Warning if passwords are stored in plain text in config. Redact password from
CONNECTtrace.- Support for cluster permissions reload (#753)
- Support a path as argument to
--signal. Thanks to pires for the contribution (#838)RemoteAddress()to theCustomClientAuthenticationinterface. Thanks to ripienaar for the contribution (#837)Changed
- Cluster permissions moved out of cluster's authorization (#747)
Fixed
- Ports file on Windows (#733)
- Memory usage for failed TLS connections (#872)
- Issue with configuration reload for some boolean parameters, such as
logtime. Thanks to sazo for the report (#874, #879)- Reduced risk of slow consumer in fan in scenarios (#876)
Complete Changes
https://github.com/nats-io/gnatsd/compare/v1.3.0...v1.4.0
Release v1.3.0
Changelog
Go Version
- 1.11: Both release executables and Docker images are built with this Go release.
Added
... (truncated)
Commits
3e64f0bMerge pull request #902 from nats-io/release_1_4_1441edf4Prepare for release 1.4.18e88372Merge pull request #901 from nats-io/fix_writeloop_signal_for_1_4_0bc8db76[FIXED] Possible delay in flushing datace2df36Update version and READMEf9bb160Replace megacheck with staticcheck4d48a17[FIXED] Reduced risk of slow consumer in fan in scenarios9ef7958[FIXED] Logtime reset to true on config reload2652e26[FIXED] Memory usage for failed TLS connections92770c6[ADDED] Connection remote address to CustomClientAuthentication- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Note: This repo was added to Dependabot recently, so you'll receive a maximum of 5 PRs for your first few update runs. Once an update run creates fewer than 5 PRs we'll remove that limit.
You can always request more updates by clicking Bump now in your Dependabot dashboard.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge@dependabot reopenwill reopen this PR if it is closed@dependabot ignore this [patch|minor|major] versionwill close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)@dependabot use these labelswill set the current labels as the default for future PRs for this repo and language@dependabot use these reviewerswill set the current reviewers as the default for future PRs for this repo and language@dependabot use these assigneeswill set the current assignees as the default for future PRs for this repo and language@dependabot use this milestonewill set the current milestone as the default for future PRs for this repo and language@dependabot badge mewill comment on this PR with code to add a "Dependabot enabled" badge to your readme
Additionally, you can set the following in your Dependabot dashboard:
- Update frequency (including time of day and day of week)
- Automerge options (never/patch/minor, and dev/runtime dependencies)
- Pull request limits (per update run and/or open at any time)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)
Finally, you can contact us by mentioning @dependabot.
Dependabot tried to update this pull request, but something went wrong. The most likely cause is #270, which may be blocking Dependabot from updating your dependency files.
Dependabot tried to update this pull request, but something went wrong. The most likely cause is #270, which may be blocking Dependabot from updating your dependency files.
Dependabot tried to update this pull request, but something went wrong. The most likely cause is #270, which may be blocking Dependabot from updating your dependency files.
Dependabot tried to update this pull request, but something went wrong. The most likely cause is #270, which may be blocking Dependabot from updating your dependency files.
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.