Describe the bug
When TEMPLATE_LIST_TEST_CASE and TEMPLATE_LIST_TEST_CASE_METHOD were added, the corresponding versions with the CATCH_ prefix were missed.

Expected behavior
CATCH_TEMPLATE_LIST_TEST_CASE and CATCH_TEMPLATE_LIST_TEST_CASE_METHOD should be available.

Additional context

The commit that added TEMPLATE_LIST_TEST_CASE and `TEMPLATE_LIST_TEST_CASE_MET

When running build.ps1 -t Test, the following output describes the failing tests:

1. Failed : NUnit.Framework.Api.FrameworkControllerTests.ExploreTestsAction_FileNotFound_ReturnsNonRunnableSuite
   Expected: String containing "The system cannot find the file specified."
   But was: "Le fichier sp├®cifi├® est introuvable. (Exception from HRESULT: 0x80070002)"
   at NUnit.Framework.Api.Framew

As part of the process of making the Pact docs more user friendly, we'd like to start writing feature documentation once, and providing code examples for each of the languages, rather than everyone having to write the same docs over and over again in each language.

The documentation for the consumer version selectors can be our first opportunity to give this approach a try. I have written the beh

I would like to drop Spring Boot support for 1.5.x. It is EOL https://spring.io/blog/2018/07/30/spring-boot-1-x-eol-aug-1st-2019
I would also add some notes in the docs, that we adhere to the spring boot lifecycle in order to be transparent about dropping support for versions.

As part of the process of making the Pact docs more user friendly, we'd like to start writing feature documentation once, and providing code examples for each of the languages, rather than everyone having to write the same docs over and over again in each language.

The documentation for the consumer version selectors can be our first opportunity to give this approach a try. I have written the beh

Bug Report

After updating to the latest test-tls13-obsolete-curves.py there were ~100 failures due to a new check that extensions are rejected due to a mismatch of the curve with the key share. While that's a good test, it is unrelated to the purpose of this test file. As such one updating to the new version that does not want to comply with the newly introduced requirement, would have to dis