Skip to content

Commit

Permalink
Merge pull request #655 from lognaturel/cleanup
Browse files Browse the repository at this point in the history
Prepare for point release off of 1.12.x branch
  • Loading branch information
lognaturel committed Sep 16, 2023
2 parents 80ebeb1 + 6fe1e8b commit e233799
Show file tree
Hide file tree
Showing 2 changed files with 11 additions and 5 deletions.
3 changes: 3 additions & 0 deletions CHANGES.txt
Original file line number Diff line number Diff line change
@@ -1,5 +1,8 @@
Pyxform Changelog

v1.12.2, 2023-09-15
* Alias list_name to dataset in entities sheet by @lognaturel in https://github.com/XLSForm/pyxform/pull/654

v1.12.1, 2023-05-16
* Pass through itemset ref case by @lognaturel in https://github.com/XLSForm/pyxform/pull/644

Expand Down
13 changes: 8 additions & 5 deletions README.rst
Original file line number Diff line number Diff line change
@@ -1,8 +1,11 @@
===============
pyxform v1.12.1
===============
========
pyxform
========

|python| |black|
|pypi| |python| |black|

.. |pypi| image:: https://badge.fury.io/py/pyxform.svg
:target: https://badge.fury.io/py/pyxform

.. |python| image:: https://img.shields.io/badge/python-3.7,3.8,3.9-blue.svg
:target: https://www.python.org/downloads
Expand Down Expand Up @@ -124,7 +127,7 @@ Releasing pyxform
3. Draft a new GitHub release with the list of merged PRs. Follow the title and description pattern of the previous release.
4. Checkout a release branch from latest upstream master.
5. Update ``CHANGES.txt`` with the text of the draft release.
6. Update ``README.rst``, ``setup.py``, ``pyxform/__init__.py`` with the new release version number.
6. Update ``setup.py``, ``pyxform/__init__.py`` with the new release version number.
7. Commit, push the branch, and initiate a pull request. Wait for tests to pass, then merge the PR.
8. Tag the release and it will automatically be published

Expand Down

0 comments on commit e233799

Please sign in to comment.