Chore
* chore(ci): run some tests using Poetry build instead of source (129)
To verify that it&39;s getting packaged correctly. In particular, I need to make sure the `.html` files are in the package. ([`c24c299`](https://github.com/crccheck/django-object-actions/commit/c24c299470d055bd1e0cb9256d65b6b0a56ce7f3))
Feature
* feat(ci): add manual semantic-release (128)
I&39;ll switch it to be automated on push to `master` at some point. ([`f43fd11`](https://github.com/crccheck/django-object-actions/commit/f43fd1199a72be013766d437fe54d875e2fdd53f))
* feat: Add Python 3.9 & 3.10 support
* ci: add Python 3.9-310 to the build
* fix: support Python 3.9-3.10 in trove classifiers ([`28f0ef7`](https://github.com/crccheck/django-object-actions/commit/28f0ef7dd62eedbdac9d34ad115245ef8d935c4d))
Fix
* fix: fix typo in version_variable (130)
Fix &34;error: [Errno 2] No such file or directory: &39;django-object-actions/init.py&39;&34; error when creating a release ([`040a802`](https://github.com/crccheck/django-object-actions/commit/040a8029c298d8bb17ffab0b75b9b9ecc3d70de2))
Refactor
* refactor: switch to Poetry for env+dep management (127)
I&39;ve been using Poetry because it takes the hassle out of virtualenv management and has sane defaults that just work for building artifacts and uploading to PyPI.
Because I had to redo how tests were run, I went ahead and removed the Tox testing requirement too and so I had to redo the Github Actions for testing too.
One thing I didn&39;t anticipate is that Github Actions caching doesn&39;t work for Poetry, only with `requirements.txt` and Pipenv https://github.blog/changelog/2021-11-23-github-actions-setup-python-now-supports-dependency-caching/
Verifying the change
I compared `python setup.py build` vs `poetry build` and the only difference was some top level meta differences and Poetry added the `tests` directory which is fine. Both have the `.html` templates which is the important thing. ([`f16cb00`](https://github.com/crccheck/django-object-actions/commit/f16cb0089d172cfa9a84c49121fc434d84e21abe))
Unknown
* Migrate CI to GitHub actions (122)
TravisCI stopped building 7 months ago, migrate to GitHub actions which seems to be the default choice these days. Some comments about this change:
- I tried to keep the build matrix close to how it was but [the build failed](https://github.com/browniebroke/django-object-actions/actions/runs/1431603631) for Django<2, so I've dropped these versions.
- Python 3.5 reached the end of its life on September 13th, 2020, so I&39;ve dropped it as well.
- The build status isn&39;t reported in this PR because it&39;s a new workflow added from a fork, and GitHub doesn&39;t run it for security reasons. You can see the [build results in my fork](https://github.com/browniebroke/django-object-actions/actions).
- I didn&39;t bother trying to add new versions for now, can be done separately. ([`4340c89`](https://github.com/crccheck/django-object-actions/commit/4340c8958492dfd2e6113fcba6fdcdc90be02e8e))