V1.20.0 (#194)
* Corrected Rerun failures - from 4ec74311cd (diff-c3a581865b7c0be4e6b5d5fa60d6aed5)
* Removed ENV
* Removed some comments
* Style matter
* Style
* Reversed rerunfailures to 4.1
* Style
* added comment about issue 77
* Removed rerunfailures version due launch of rerunfailures 6.0
* Version 1.20.0 and version release text
* Changed RST
* Removed extraneous space
This commit is contained in:
parent
75cfd52da1
commit
7b90cee2ef
15
CHANGES.rst
15
CHANGES.rst
|
@ -1,6 +1,21 @@
|
|||
Release Notes
|
||||
-------------
|
||||
|
||||
**1.20.9 (2019-01-12)**
|
||||
|
||||
* Tests running with Pytest 4.0 and Python 3.7
|
||||
|
||||
* Stop filtering out falsy environment values (`#175 <https://github.com/pytest-dev/pytest-html/issues/175>`_)
|
||||
|
||||
* Thanks to `@jknotts <https://github.com/jknotts>`_ for reporting the issue
|
||||
and to `@crazymerlyn <http://github.com/crazymerlyn>`_ for providing a fix
|
||||
|
||||
* Removed extraneous space from anchor tag (`@chardbury <https://github.com/chardbury>`_)
|
||||
|
||||
* Always define __version__ even if get_distribution() fails (`@nicoddemus <https://github.com/nicoddemus>`_)
|
||||
|
||||
* Refactor css config code (`@crazymerlyn <http://github.com/crazymerlyn>`_)
|
||||
|
||||
**1.19.0 (2018-06-01)**
|
||||
|
||||
* Allow collapsed outcomes to be configured by using a query parameter
|
||||
|
|
14
README.rst
14
README.rst
|
@ -267,6 +267,20 @@ Tests can be run locally with `tox`_, for example to execute tests for Python 2.
|
|||
|
||||
.. _`tox`: https://tox.readthedocs.org/en/latest/
|
||||
|
||||
Releasing a new version
|
||||
-----------------------
|
||||
|
||||
Follow these steps to release a new version of the project:
|
||||
|
||||
1. Update your local master with the upstream master (``git pull --rebase upstream master``)
|
||||
2. Create a new branch and update ``CHANGES.rst`` with the new version, today's date, and all changes/new features
|
||||
3. Commit and push the new branch and then create a new pull request
|
||||
4. Wait for tests and reviews and then merge the branch
|
||||
5. Once merged, update your local master again (``git pull --rebase upstream master``)
|
||||
6. Tag the release with the new release version (``git tag v<new tag>``)
|
||||
7. Push the tag (``git push upstream --tags``)
|
||||
8. Done. You can monitor the progress on `Travis <https://travis-ci.org/pytest-dev/pytest-html/>`_
|
||||
|
||||
Resources
|
||||
---------
|
||||
|
||||
|
|
Loading…
Reference in New Issue