You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/changelog.rst
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,43 +19,43 @@ Version 0.2.4 (unreleased)
19
19
* Rewrite the path handling of the Sphinx extension to handle branch names containing a forward slash properly on Windows and add unittests and Windows CI builds to make sure it doesn't break on future updates. (`#31 <issue31_>`_, `#35 <issue35_>`_)
20
20
21
21
22
-
Version 0.2.3
23
-
-------------
22
+
Version 0.2.3 (2020-05-04)
23
+
--------------------------
24
24
25
25
* Fixed return codes of main() function and exit with non-zero status if no matching refs were found.
26
26
* Added some logging calls to the git module.
27
27
* Fixed bug where local branch was used to check the existence of files on remote branches.
28
28
29
29
30
-
Version 0.2.2
31
-
-------------
30
+
Version 0.2.2 (2020-05-01)
31
+
--------------------------
32
32
33
33
* Added additional checks to determine if a branch or tag contains both the Sphinx source directory and the :file:`conf.py` file. If that's not the case, that branch or tag is skipped automatically and not copied to the temporary directory. (`#9 <issue9_>`_)
34
34
35
35
36
-
Version 0.2.1
37
-
-------------
36
+
Version 0.2.1 (2020-04-19)
37
+
--------------------------
38
38
39
39
* Fixed handling of absolute output paths in `vpathto` and ensure that all generated paths are relative.
40
40
41
41
42
-
Version 0.2.0
43
-
-------------
42
+
Version 0.2.0 (2020-04-19)
43
+
--------------------------
44
44
45
45
* Added a way to override config variables using placeholders that expand to each version's actual value (`#4 <issue4_>`_, `#7 <issue7_>`_).
46
46
47
47
48
48
Version 0.1
49
49
===========
50
50
51
-
Version 0.1.1
52
-
-------------
51
+
Version 0.1.1 (2020-03-12)
52
+
--------------------------
53
53
54
54
* Fixed version number in documentation
55
55
* Fixed issue that caused the wrong configuration directory being used when the ``-c`` argument was not specified on the command line
Copy file name to clipboardExpand all lines: docs/faq.rst
+7-1Lines changed: 7 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,10 +24,16 @@ Then it copies the data for each version into separate temporary directories, bu
24
24
The :file:`conf.py` file from the currently checked out branch will be used to build old versions, so it's not necessary to make changes old branches or tags to add support for ``sphinx-multiversion``.
25
25
This also means that theme improvements, template changes, etc. will automatically be applied to old versions without needing to add commits.
26
26
27
+
27
28
Do I need to make changes to old branches or tags?
No, you don't. ``sphinx-multiversion`` will always use the :file:`conf.py` file from you currently checked out branch.
31
+
No, you don't. ``sphinx-multiversion`` will always use the :file:`conf.py` file from your currently checked out branch.
32
+
33
+
The downside is that this behaviour restricts the kinds of changes you may do to your configuration, because it needs to retain compatibility with old branches.
34
+
For example, if your :file:`conf.py` file hardcodes a path (e.g. for opening a file), but that file does not exist in some older branches that you want to build documentation for, this will cause issues.
35
+
In these cases you will need to add a check if a file actually exists and adapt the path accordingly.
36
+
31
37
32
38
What are the license terms of ``sphinx-multiversion``?
0 commit comments