mirror of
https://github.com/ergochat/ergo.git
synced 2024-11-15 00:19:29 +01:00
version and changelog updates for 2.9.0-rc1 (#1889)
* version and changelog updates for 2.9.0-rc1 * review fixes to changelog and documentation
This commit is contained in:
parent
c01e686221
commit
2dde9cb464
46
CHANGELOG.md
46
CHANGELOG.md
@ -1,6 +1,52 @@
|
||||
# Changelog
|
||||
All notable changes to Ergo will be documented in this file.
|
||||
|
||||
## [2.9.0-rc1] - 2021-01-02
|
||||
|
||||
We're pleased to be publishing the release candidate for 2.9.0 (the official release should follow in a week or so).
|
||||
|
||||
This release contains mostly bug fixes, with some enhancements to moderation tools.
|
||||
|
||||
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 [@erincerys](https://github.com/erincerys), [@FiskFan1999](https://github.com/FiskFan1999), [@mogad0n](https://github.com/mogad0n), and [@tacerus](https://github.com/tacerus) for contributing patches, and to [@ajaspers](https://github.com/ajaspers), [@emersion](https://github.com/emersion), [@FiskFan1999](https://github.com/FiskFan1999), [@Jobe1986](https://github.com/Jobe1986), [@kylef](https://github.com/kylef), [@mogad0n](https://github.com/mogad0n), [@pcho](https://github.com/pcho), and [@progval](https://github.com/progval) for reporting issues,
|
||||
|
||||
|
||||
### Config changes
|
||||
* Added `lock-file`, which helps protect against accidentally starting multiple instances of Ergo. This is a no-op if unset. The recommended default value is `ircd.lock`, which (like the default datastore path `ircd.db`) is relative to the working directory of the Ergo process. If your `datastore.path` is absolute, this path (if set) should be absolute as well. (#1823)
|
||||
* `+C` (no channel-wide CTCP messages other than ACTION) is now a recommended default channel mode (#1851)
|
||||
* Added `exempt-sasl` boolean to `server.ip-check-script`; if enabled, IP check scripts are run only for connections without SASL, improving performance for registered users (#1888)
|
||||
* `hidden: true` is now the recommended default for operator definitions (#1730)
|
||||
|
||||
### Changed
|
||||
* The semantics of `+R` have been changed. `+R` now only prevents unauthenticated users from joining, so unregistered users who have already joined can still speak. The old semantics are still available via `+RM` (i.e. `+R` together with the `+M` "moderated-registered" mode). (#1858, thanks [@ajaspers](https://github.com/ajaspers)!)
|
||||
* Unauthenticated users matching a `+I` invite exception mask can now join `+R` channels (#1871)
|
||||
* INVITE now exempts the user from `+b` bans (#1876, thanks [@progval](https://github.com/progval)!)
|
||||
* NS SUSPEND now only requires only the `ban` operator capability, as opposed to `accreg` (#1828, #1839, thanks [@mogad0n](https://github.com/mogad0n)!)
|
||||
|
||||
### Added
|
||||
* SHA-256 certificate fingerprints can now be imported from Anope and Atheme (#1864, #1869, thanks [@tacerus](https://github.com/tacerus)!)
|
||||
* IP check scripts can now be run only for users that have not authenticated with SASL by the end of the handshake, improving performance for registered users (#1888)
|
||||
* Logging into an unverified account with SASL sends the new `NOTE AUTHENTICATE VERIFICATION_REQUIRED` [standard reply code](https://ircv3.net/specs/extensions/standard-replies) (#1852, #1853, thanks [@emersion](https://github.com/emersion)!)
|
||||
* CS PURGE now sends a snotice (#1826, thanks [@tacerus](https://github.com/tacerus)!)
|
||||
* The `v` snomask is now used to send notifications about vhost changes initiated by operators (#1844, thanks [@pcho](https://github.com/pcho)!)
|
||||
|
||||
### Fixed
|
||||
* CAP LS and LIST responses after connection registration could be truncated in some cases; this has been fixed (#1872)
|
||||
* Unprivileged users with both a password and a certfp could not remove their password with `NS PASSWD <password> * *` as expected; this has been fixed (#1883, #1884, thanks [@FiskFan1999](https://github.com/FiskFan1999)!)
|
||||
* RELAYMSG identifiers that were not already in their case-normalized form could not be muted with `+b m:`; this has been fixed (#1838, thanks [@mogad0n](https://github.com/mogad0n)!)
|
||||
* CS AMODE changes did not take immediate effect if `force-nick-equals-account` was disabled and the nick did not coincide with the account; this has been fixed (#1860, thanks [@eskimo](https://github.com/eskimo)!)
|
||||
* `315 RPL_ENDOFWHO` now sends the exact, un-normalized mask argument provided by the client (#1831, thanks [@progval](https://github.com/progval)!)
|
||||
* A leading `$` character is now disallowed in new nicknames and account names, to avoid collision with the massmessage syntax (#1857, thanks [@emersion](https://github.com/emersion)!)
|
||||
* The [deprecated](https://github.com/ircdocs/modern-irc/pull/138) `o` parameter of `WHO` now returns an empty list of results, instead of being ignored (#1730, thanks [@kylef](https://github.com/kylef), [@emersion](https://github.com/emersion), [@progval](https://github.com/progval)!)
|
||||
* WHOX queries for channel oplevel now receive `*` instead of `0` (#1866, thanks [@Jobe1986](https://github.com/Jobe1986)!)
|
||||
|
||||
### Internal
|
||||
* Updated list of official release binaries: added Apple M1, OpenBSD x86-64, and Plan 9 x86-64, removed Linux armv7, FreeBSD x86-32, and Windows x86-32. (The removed platforms are still fully supported by Ergo; you can build them from source or ask us for help.) (#1833)
|
||||
* Added an official Linux arm64 Docker image (#1855, thanks [@erincerys](https://github.com/erincerys)!)
|
||||
* Added service management files for OpenSolaris/Illumos (#1846, thanks [@tacerus](https://github.com/tacerus)!)
|
||||
|
||||
|
||||
## [2.8.0] - 2021-11-14
|
||||
|
||||
We're pleased to be publishing Ergo 2.8.0. This release contains many fixes and enhancements, plus one major user-facing feature: user-initiated password resets via e-mail (#734).
|
||||
|
@ -4,7 +4,7 @@
|
||||
# for a config with more "mainstream" behavior.
|
||||
#
|
||||
# If you are setting up a new Ergo server, you should copy this file
|
||||
# to a new one named 'ircd.yaml', then read the whole file to see which
|
||||
# to a new one named 'ircd.yaml', then look through the file to see which
|
||||
# settings you want to customize. If you don't understand a setting, or
|
||||
# aren't sure what behavior you want, most of the defaults are fine
|
||||
# to start with (you can change them later, even on a running server).
|
||||
@ -751,8 +751,8 @@ debug:
|
||||
|
||||
# lock file preventing multiple instances of Ergo from accidentally being
|
||||
# started at once. comment out or set to the empty string ("") to disable.
|
||||
# this path is relative to the working directory; you may want to use an
|
||||
# absolute path instead:
|
||||
# this path is relative to the working directory; if your datastore.path
|
||||
# is absolute, you should use an absolute path here as well.
|
||||
lock-file: "ircd.lock"
|
||||
|
||||
# datastore configuration
|
||||
|
@ -723,8 +723,8 @@ debug:
|
||||
|
||||
# lock file preventing multiple instances of Ergo from accidentally being
|
||||
# started at once. comment out or set to the empty string ("") to disable.
|
||||
# this path is relative to the working directory; you may want to use an
|
||||
# absolute path instead:
|
||||
# this path is relative to the working directory; if your datastore.path
|
||||
# is absolute, you should use an absolute path here as well.
|
||||
lock-file: "ircd.lock"
|
||||
|
||||
# datastore configuration
|
||||
|
Loading…
Reference in New Issue
Block a user