V2.3.1 docs update

.github/workflows/deploy.yml

@@ -12,7 +12,7 @@ jobs:
         run: |
           mkdir build
           chmod 777 build
-          docker run --rm -v $PWD:/opt -w /opt -e USER_ID=$UID ddidier/sphinx-doc:2.2.1-1 sphinx-build -b html source build
+          docker run --rm -v $PWD:/opt -w /opt -e USER_ID=$UID ddidier/sphinx-doc:7.1.2-1 sphinx-build -b html source build
 
       - name: Install AWS Cli
         run: pip install awscli

README.md

@@ -21,18 +21,18 @@ Comments, pull requests and general feedback is welcome from anyone.
 
 The 3-D Secure v2 specification is defined by EMVCo, their list of 3-D Secure v2
 documentation can be found [on their documentation
-page](https://www.emvco.com/document-search/?action=search_documents&publish_date=&emvco_document_version=&emvco_document_book=&px_search=&emvco_document_technology%5B%5D=3-d-secure).
+page](https://www.emvco.com/specifications/?tax%5Bspecifications_categories%5D%5B32%5D%5B%5D=84&tax%5Bspecifications_categories%5D%5B33%5D%5B%5D=447).
 
-Specifically, the primary documentation can be found in [EMV® 3-D Secure
-Protocol and Core Functions Specification.](https://www.emvco.com/wp-content/uploads/documents/EMVCo_3DS_Spec_v220_122018.pdf)
+Specifically, the primary documentation can be found in named "EMV® 3-D Secure
+Protocol and Core Functions Specification".
 
 The spec is currently at version 2.2.0.
 
 ## Generate documentation locally
 
 The documentation is currently generated by Sphinx. It can be generated locally with:
 
-    docker run --rm -v $PWD:/opt -w /opt -e USER_ID=$UID ddidier/sphinx-doc:2.2.1-1 sphinx-build -b html source build
+    docker run --rm -v $PWD:/opt -w /opt -e USER_ID=$UID ddidier/sphinx-doc:7.1.2-1 sphinx-build -b html source build
 
 The generated documentation is then rooted in `build/index.html`.
 

live.py

@@ -2,5 +2,5 @@
 
 from livereload import Server, shell
 server = Server()
-server.watch('build/html/*.html')
-server.serve(root="build/html", open_url_delay=4)
+server.watch('build/*.html')
+server.serve(root="build", open_url_delay=4)

source/3dsmethod.rst

@@ -17,7 +17,7 @@ If `3DS Method URL`_ is included in the :ref:`preauth-usage` response, the
 3DS method *must* be invoked as explained in this guide.
 
 If ``threeDSMethodURL`` *is not* included in the ``/preauth`` response (ref.
-:ref:`2.1.0 <preauth-response-210>`, :ref:`2.1.0 <preauth-response-220>`),
+:ref:`2.1.0 <preauth-response-210>`, :ref:`2.2.0 <preauth-response-220>`, :ref:`2.3.1 <preauth-response-231>`),
 continue with the :ref:`auth-usage` and set `3DS Completion indicator
 <specification_210.html#attr-AReq-threeDSCompInd>`_ to ``"U"``, to indicate that the
 3DS Method was not available.