Merge pull request #2 from metaodi/develop

Release 0.0.3

CHANGELOG.md

@@ -4,6 +4,14 @@ The format is based on [Keep a Changelog](http://keepachangelog.com/) and this p
 
 ## [Unreleased]
 
+## [0.0.3] - 2021-09-14
+### Added
+- Workflows to lint and publish the code
+
+### Fixed
+- Wrong version number in __init__.py
+- Linting errors in code base
+
 ## [0.0.2] - 2021-09-13
 ### Changed
 - Add possiblity to provide a `map_function` to parse custom fields
@@ -26,6 +34,7 @@ The format is based on [Keep a Changelog](http://keepachangelog.com/) and this p
 - `Fixed` for any bug fixes.
 - `Security` to invite users to upgrade in case of vulnerabilities.
 
-[Unreleased]: https://github.com/metaodi/museumpy/compare/v0.0.2...HEAD
+[Unreleased]: https://github.com/metaodi/museumpy/compare/v0.0.3...HEAD
+[0.0.3]: https://github.com/metaodi/museumpy/compare/v0.0.2...v0.0.3
 [0.0.2]: https://github.com/metaodi/museumpy/compare/v0.0.1...v0.0.2
 [0.0.1]: https://github.com/metaodi/museumpy/releases/tag/v0.0.1

CONTRIBUTING.md

@@ -29,7 +29,7 @@ flake8 --install-hook git
 
 ## Create a pull request
 
-1. Choose the `develop` branch as a target for new/changed functionality, `master` should only be targeted for urgent bugfixes.
+1. Choose the `develop` branch as a target for new/changed functionality, `main` should only be targeted for urgent bugfixes.
 2. While it's not strictly required, it's highly recommended to create a new branch on your fork for each pull request.
 3. Push to your fork and [submit a pull request][pr].
 4. Check if the [build ran successfully][ci] and try to improve your code if not.

README.md

@@ -157,6 +157,6 @@ To create a new release, follow these steps (please respect [Semantic Versioning
 
 1. Adapt the version number in `museumpy/__init__.py`
 1. Update the CHANGELOG with the version
-1. Create a pull request to merge `develop` into `master` (make sure the tests pass!)
-1. Create a [new release/tag on GitHub](https://github.com/metaodi/museumpy/releases) (on the master branch)
+1. Create a [pull request to merge `develop` into `main`](https://github.com/metaodi/museumpy/compare/main...develop?expand=1) (make sure the tests pass!)
+1. Create a [new release/tag on GitHub](https://github.com/metaodi/museumpy/releases) (on the main branch)
 1. The [publication on PyPI](https://pypi.python.org/pypi/museumpy) happens via [GitHub Actions](https://github.com/metaodi/museumpy/actions?query=workflow%3A%22Upload+Python+Package%22) on every tagged commit

museumpy/__init__.py

@@ -1,4 +1,4 @@
-__version__ = '0.0.1'
+__version__ = '0.0.3'
 __all__ = ['client', 'errors', 'response', 'xmlparse']
 
 from .errors import MuseumPlusError  # noqa