Skip to content

Conversation

@pyup-bot
Copy link
Collaborator

This PR updates alabaster from 0.7.8 to 0.7.11.

Changelog

0.7.11

* :bug:`73` Clean up some problematic font issues:

- Remove the outright broken Goudy Old Style, plus other mostly Adobe-only
 fonts, from the ``font_family`` config setting; it is now simply ``Georgia,
 serif`` which is what the majority of users were rendering anyways.
- Clear out the default value of ``head_font_family`` (which contained
 ``Garamond``, a nice but also Adobe only font)
- Set ``head_font_family`` so it falls back to the value of ``font_family``
 unless a user has explicitly set it themselves.

.. note::
 You can always go back to the old values by :ref:`explicitly setting
 <theme-options>` ``font_family`` and/or ``head_font_family`` in your
 ``conf.py``'s ``html_theme_options``, e.g.::

     html_theme_options = {
         'description': 'My awesome project',
         'font_family': "goudy old style, minion pro, bell mt, Georgia, Hiragino Mincho Pro, serif",
     }

.. warning::
 Depending on individual viewers' systems, this change *may* be **visually**
 backwards incompatible if you were not already overriding the font
 settings and those users had the fonts in question (which are not default
 on most systems).

 As seen in the note above, you can **always** override the new defaults to
 go back to the old behavior, using your config file.

* :feature:`18 backported` (via :issue:`101`) Add optional *next* and
*previous* links at the top and bottom of page content. Use theme option
``show_relbars`` to enable these. Credit: William Minchin.
* :support:`- backported` Miscellaneous project maintenance updates such as
adding to Travis CI and enforcing the use of ``flake8``.
* :feature:`110 backported` Add ``badge_branch`` option allowing
configurability of which specific Git branch the Travis, Codecov, etc buttons
default to. Credit: ``TitanSnow``.
* :support:`111 backported` Add setuptools-level entrypoint for improved theme
distribution compatibility. Thanks to Aaron Carlisle for the patch.

0.7.10

* :bug:`32` Update styling of various block-level elements such as admonitions
(``.. note::``, ``.. warning::``, etc) and code blocks (``.. code::``) so
they are no longer 'dedented' outside the main column of text they're
embedded in. This is both a stylistic change and a bugfix, since e.g. nesting
code blocks *within* note blocks looks actively broken. Thanks to Takayuki
Shimizukawa for the report.
* :bug:`96` ``admonition_xref`` had a template typo preventing it from
receiving styling; this has been fixed. Credit: Kenzie Togami.
* :bug:`95` Independently ran across
`sphinx-doc/sphinx3276 <https://github.com/sphinx-doc/sphinx/issues/3276>`_,
namely that parameter lists become squashed together if one is running on
Sphinx 1.4.x. While that fix was merged in Sphinx itself, we felt it prudent
to include it in our own stylesheet as well, for immediate relief.

0.7.9

* :feature:`6` (and :issue:`70`, both via :issue:`84`) Make all remaining
hardcoded style colors configurable, plus related cleanup (such as improving
differentiation of some admonition blocks such as ``warn`` and ``note``,
ensuring generic admonitions are left untouched, etc). Credit:
``ShadowKyogre``.
* :feature:`83` Expose Sphinx's toctree ``collapse`` option as the new
``sidebar_collapse`` config option. Credit: Eric Holscher.
* :feature:`80` Add support for ``<link rel="canonical">`` (i.e. canonical
URLs). Thanks to Ben Gamari for the patch.
* :support:`7` Generate real documentation site, both because the README is
just too big now, and so we can `eat our own dog food
<https://en.wikipedia.org/wiki/Eating_your_own_dog_food>`_.
Links

@pyup-bot
Copy link
Collaborator Author

pyup-bot commented Oct 3, 2018

Closing this in favor of #249

@pyup-bot pyup-bot closed this Oct 3, 2018
@StuartJSquires StuartJSquires deleted the pyup-update-alabaster-0.7.8-to-0.7.11 branch October 3, 2018 03:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants