Update ghcr.io/ergochat/ergo Docker tag to v2.16.0 #216
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.
This PR contains the following updates:
v2.15.0
->v2.16.0
Release Notes
ergochat/ergo (ghcr.io/ergochat/ergo)
v2.16.0
Compare Source
We're pleased to be publishing v2.16.0, a new stable release. This release contains bug fixes and some minor updates.
This release includes changes to the config file format, all of which are fully backwards-compatible and do not require updating the file before upgrading. It includes no changes to the database file format.
Many thanks to @csmith, @delthas, donio, @emersion, @KlaasT, @knolley, @Mailaender, and @prdes for reporting issues and helping test.
Config changes
api
block for configuring the new HTTP API. If this block is absent, the API is disabled (#2231)server.additional-isupport
for publishing arbitrary ISUPPORT tokens (#2220, #2240)server.command-aliases
to configure aliases for server commands (#2229, #2236)roleplay
to customize the NUH's sent forNPC
andSCENE
. Roleplay remains deprecated and disabled by default. (#2237)Security
POST
. If you were relying on this to create IRC sessions via an HTTP client, please open an issue. (#2239)Added
ed25519
-sha256 for DKIM. However, enabling this algorithm is not recommended since mainstream email providers still do not support it. (#1041, #2242)Fixed
CHATHISTORY TARGETS
from MySQL backend reporting incorrect timestamps when the server timezone is not UTC (#2224)draft/isupport
responses (#2253)NS UNREGISTER
not deleting the stored push subscriptions (#2254)NS SAREGISTER
could create clients without applying the default user modes (#2252, #2254, thanks donio!)CHATHISTORY
parameters (#2248, #2249, thanks @prdes!)enforce-utf8
is enabled (the recommended default) (#2228, #2233, thanks @KlaasT!)QUIT
line now respects theserver-time
capability (#2218, #2219)MODE
changes (#2213)Changed
draft/message-redaction
capability is no longer advertised whenallow-individual-delete
is disabled (#2215, #2216, thanks @delthas!)Internal
Configuration
📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.