Bug Fixes
- Support repository owner names containing dots
([`a6c4da4`](https://github.com/python-semantic-release/python-semantic-release/commit/a6c4da4c0e6bd8a37f64544f7813fa027f5054ed))
Fixes 179
- **github**: Use application/octet-stream for .whl files
([`90a7e47`](https://github.com/python-semantic-release/python-semantic-release/commit/90a7e476a04d26babc88002e9035cad2ed485b07))
application/octet-stream is more generic, but it is better than using a non-official MIME type.
Features
- Upload distribution files to GitHub Releases
([177](https://github.com/python-semantic-release/python-semantic-release/pull/177),
[`e427658`](https://github.com/python-semantic-release/python-semantic-release/commit/e427658e33abf518191498c3142a0f18d3150e07))
* refactor(github): create upload_asset function
Create a function to call the asset upload API. This will soon be used to upload assets specified by
the user.
* refactor(github): infer Content-Type from file extension
Infer the Content-Type header based on the file extension instead of setting it manually.
* refactor(pypi): move building of dists to cli.py
Refactor to have the building/removal of distributions in cli.py instead of within the
upload_to_pypi function. This makes way for uploading to other locations, such as GitHub Releases,
too.
* feat(github): upload dists to release
Upload Python wheels to the GitHub release. Configured with the option upload_to_release, on by
default if using GitHub.
* docs: document upload_to_release config option
* test(github): add tests for Github.upload_dists
* fix(github): fix upload of .whl files
Fix uploading of .whl files due to a missing MIME type (defined custom type as
application/x-wheel+zip). Additionally, continue with other uploads even if one fails.
* refactor(cli): additional output during publish
Add some additional output during the publish command.
* refactor(github): move api calls to separate methods
Move each type of GitHub API request into its own method to improve readability.
Re-implementation of 172
* fix: post changelog after PyPI upload
Post the changelog in-between uploading to PyPI and uploading to GitHub Releases. This is so that if
the PyPI upload fails, GitHub users will not be notified. GitHub uploads still need to be
processed after creating the changelog as the release notes must be published to upload assets to
them.