version 2.4.8v2.4.8

3 files changed, 11 insertions, 9 deletions

diff --git a/doc/html_generated/configuration.html b/doc/html_generated/configuration.html
index 23360263..8c8cbde5 100644
--- a/doc/html_generated/configuration.html
+++ b/doc/html_generated/configuration.html
@@ -36,6 +36,7 @@ Defining something ```globally``` means for every source file of the binary (exe
 - [**```DOCTEST_CONFIG_NO_POSIX_SIGNALS```**](#doctest_config_no_posix_signals)
 - [**```DOCTEST_CONFIG_INCLUDE_TYPE_TRAITS```**](#doctest_config_include_type_traits)
 - [**```DOCTEST_CONFIG_NO_MULTI_LANE_ATOMICS```**](#doctest_config_no_multi_lane_atomics)
+- [**```DOCTEST_CONFIG_EVALUATE_ASSERTS_EVEN_WHEN_DISABLED```**](#doctest_config_evaluate_asserts_even_when_disabled)
 
 For most people the only configuration needed is telling **doctest** which source file should host all the implementation code:
 
@@ -244,6 +245,10 @@ This can be defined both globally and in specific source files only.
 
 This can be used to disable multi lane atomics. Multi lane atomics can speed up highly parallel use of assert statements, but have a small overhead for single threaded applications.
 
+### **```DOCTEST_CONFIG_EVALUATE_ASSERTS_EVEN_WHEN_DISABLED```**
+
+This can be used to evaluate asserts even when **```DOCTEST_CONFIG_DISABLE```** is used - this is useful when they are used in production code within if statements so that the condition continues to be evaluated.
+
 ---------------
 
 [Home](readme.html#reference)
diff --git a/doc/html_generated/features.html b/doc/html_generated/features.html
index 1f048406..34688d70 100644
--- a/doc/html_generated/features.html
+++ b/doc/html_generated/features.html
@@ -19,7 +19,7 @@
 - 0 warnings even with the most aggressive flags (on all tested compilers!!!)
     - ```-Weverything -pedantic``` for **clang**
     - ```-Wall -Wextra -pedantic``` and **>> over 35 <<** other warnings **not** covered by these flags for **GCC**!!! - see [**here**](../../scripts/cmake/common.cmake#L84)
-    - ```/Wall``` for **MSVC** (except for: ```C4514```, ```C4571```, ```C4710```, ```C4711```)
+    - ```/Wall``` for **MSVC**
 - doesn't error on unrecognized [**command line**](commandline.html) options and supports prefixes for interop with client command line parsing
 - can set options [**procedurally**](main.html) and not deal with passing ```argc```/```argv``` from the command line
 - doesn't leave warnings disabled after itself
@@ -29,18 +29,17 @@
 **SOME OF THIS IS OUTDATED**
 
 - Standards compliant **C++11** code - should work with any **C++11** capable compiler (use tag [**1.2.9**](https://github.com/doctest/doctest/tree/1.2.9) for C++98 and older compilers)
-- tested with **GCC**: **4.8**, **4.9**, **5**, **6**, **7**, **8**, **9**, **10**
-- tested with **Clang**: **3.5**, **3.6**, **3.7**, **3.8**, **3.9**, **4**, **5**, **6**, **7**, **8**, **9** (XCode 6+)
-- tested with **MSVC**: **2015**, **2017**, **2019** (also in 32 bit mode)
-- per-commit tested on [**travis**](https://travis-ci.org/doctest/doctest) and [**appveyor**](https://ci.appveyor.com/project/doctest/doctest) CI services
+- tested with **GCC**: **4.8**, **4.9**, **5**, **6**, **7**, **8**, **9**, **10**, **11**
+- tested with **Clang**: **3.5**, **3.6**, **3.7**, **3.8**, **3.9**, **4**, **5**, **6**, **7**, **8**, **9**, **10**, **11**, **12**, **13** (XCode 10+)
+- tested with **MSVC**: **2015**, **2017**, **2019**, **2022** (also in 32 bit mode)
+- per-commit tested on [**GitHub Actions**](https://github.com/doctest/doctest/actions)
     - warnings as errors even on the most aggressive warning levels - see [**here**](../../scripts/cmake/common.cmake#L84)
     - statically analyzed on the CI - [**Cppcheck**](http://cppcheck.sourceforge.net/) / [**Clang-Tidy**](https://clang.llvm.org/extra/clang-tidy/) / [**Coverity Scan**](https://scan.coverity.com/) / [**OCLint**](http://oclint.org/) / [**Visual Studio Analyzer**](https://docs.microsoft.com/en-us/visualstudio/code-quality/analyzing-c-cpp-code-quality-by-using-code-analysis)
     - all tests have their output compared to reference output of a previous known good run
     - all tests built and ran in **Debug**/**Release** modes
     - all tests ran through **valgrind** under **Linux** (sadly [not under OSX](https://github.com/doctest/doctest/issues/11))
     - all tests ran through **address**, **UB** and **thread** sanitizers under **Linux**/**OSX**
-    - tests are ran in more than **150** different configurations on UNIX (Linux + OSX) on **travis** CI
-    - tests are ran in a total of **14** different configurations on Windows on **appveyor** CI
+    - tests are ran in more than **300** different configurations on UNIX (Linux + OSX) & Windows
 
 ## Other features:
 
diff --git a/doc/html_generated/roadmap.html b/doc/html_generated/roadmap.html
index 4b27e3c2..a53622de 100644
--- a/doc/html_generated/roadmap.html
+++ b/doc/html_generated/roadmap.html
@@ -145,8 +145,6 @@ Planned features for future releases - order changes constantly... Also look thr
 ### Things that are very unlikely to enter the roadmap:
 
 - rethink static code analysis suppressions - users shouldn't have to use the same flags for code which uses doctest macros/types
-- move the "react()" part (the one that throws for REQUIRE asserts - or for when "abort-after=<int>" is reached) to a function call in the while() part of the asserts
-- stop using underscores for the beginning of identifiers - the anonymous variables - against the standard...
 - templated fixture test cases
 - test with missed warning flags for GCC
     - https://github.com/Barro/compiler-warnings