Add a fallback for Pages to behave as in pre-1.3
#61
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
goerz
force-pushed
the
mg/59-pages-fallback
branch
from
0279cad
to
c1760c2
Compare
|
@kellertuer Does this fallback and the new |
goerz
force-pushed
the
mg/59-pages-fallback
branch
3 times, most recently
from
25479fe
to
bbecb3f
Compare
|
Nice, makes the switch smoother :) |
goerz
force-pushed
the
mg/59-pages-fallback
branch
from
bbecb3f
to
059579a
Compare
goerz
force-pushed
the
mg/59-pages-fallback
branch
from
059579a
to
fa42ef5
Compare
|
I'm going to release this immediately as 1.3.1, since it modifies behavior. Other "cleanup" from the 1.3.0, such as additional warnings, are less critical, and will be released as 1.3.2 later on. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The names in
Pagesin a@bibliographyblock can now again be relative to thedocs/srcdirectory, which was the1.2.xbehavior. A warning will be emitted that these should be updated.This PR also extends the "upgrade instructions" for the
1.3.0release in NEWS.md (which should have been in the original release)Closes #59