summaryrefslogtreecommitdiff
path: root/UPDATING
diff options
context:
space:
mode:
authorGabriel M. Dutra <0xdutra@gmail.com>2023-01-29 19:51:56 +0100
committerFernando ApesteguĂ­a <fernape@FreeBSD.org>2023-01-30 09:34:35 +0100
commit789a1ef5adb482188aa3692c889ea8ebdd3a9c65 (patch)
treefd8226276469171841ba9d16698be31f68078ad3 /UPDATING
parent1dd1fb91b0a63c2aa654d8f8ee096b545f8ab2c9 (diff)
downloadfreebsd-ports-789a1ef5adb482188aa3692c889ea8ebdd3a9c65.zip
benchmarks/ddosify: Update to 0.13.0
ChangeLog: https://github.com/ddosify/ddosify/releases/tag/v0.13.0 * Merge remote-tracking branch 'origin/develop' into feat/concat-variables * Update README.md * change captureEnv to snake case * change csv parameters to snake case * change jsonPath to json_path * fix done channel send place in stdoutJson * get profile data from pprof package * inject both typed and concatenated vars * regexp, xpath, header_key * remove unnecessary comment * update benchmark jenkins file * update jenkinsfile * use atomic instead of mutex PR: 269216 Reported by: 0xdutra@gmail.com (maintainer)
Diffstat (limited to 'UPDATING')
-rw-r--r--UPDATING7
1 files changed, 7 insertions, 0 deletions
diff --git a/UPDATING b/UPDATING
index da07f5911da4..cf0c026be62f 100644
--- a/UPDATING
+++ b/UPDATING
@@ -5,6 +5,13 @@ they are unavoidable.
You should get into the habit of checking this file for changes each time
you update your ports collection, before attempting any port upgrades.
+20230129:
+ AFFECTS: users of benchmarks/ddosify
+ AUTHOR: fernape@freebsd.org
+
+ In 0.13.0 some configuration keys have been renamed for consistency. Have a
+ look at https://github.com/ddosify/ddosify/releases/tag/v0.13.0 for details.
+
20230127:
AFFECTS: users of security/openvpn
AUTHOR: mandree@freebsd.org