Unable to resolve action python-semantic-release/[email protected], unable to find
version 9.21.0
It is now named python-semantic-release/publish-action
Python 3.7 hasn't been supported in ages, and it's causing errors on CI actions so let's just drop it.
It appears that dropping Python 3.7 is desired anyway!
Updating the project to match my current style and to reduce dependencies.
No code changes needed for Django 5.2 support
https://docs.djangoproject.com/en/5.2/releases/5.2/
Bringing in rules I've had success with elsewhere. More consistent style helps with readability and maintainability. Some of the rules help with code simplicity and with reducing bugs too.
https://docs.djangoproject.com/en/5.0/releases/5.0/
-
Update Django/Python test matrix and add classifier for py3.12 (#171,
ad3b898) -
ci: Upgrade python-semantic-release to v9.8.8 (#176,
50a03af)
There have been a lot of releases since v8.0.8 https://github.com/python-semantic-release/python-semantic-release/blob/master/CHANGELOG.md#v808-2023-08-26
The breaking change was dropping Python 3.7. While this project supports 3.7... that will change the next opportunity
Adding new Django Modal Actions package Deleting Django Object Actions which hasn't had a commit in 3 years
Followup to #168 to get CI to pass again, documents how to make a POST only action, and adds some test coverage.
There are still a few cleanup issues but this should get things moving on POST only actions again.
I missed some updated config changes - https://python-semantic-release.readthedocs.io/en/latest/migrating_from_v7.html#version-toml - https://python-semantic-release.readthedocs.io/en/latest/configuration.html#config-version-variables
Ran black on to comply with format from 23.x version
fixes deprecation warnings in CI: > The set-output command is deprecated and will be disabled
soon. Please upgrade to using Environment Files. For more information see:
https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Hopefully this fixes the broken GitHub Action too
https://github.com/crccheck/django-object-actions/actions/runs/3464471740 error: No module named 'packaging'
python-semantic-release/python-semantic-release#489
closes #144
Also moves Coverage config to pyproject.toml to eliminate another top level project file
To reduce future diffs from autoformat
Just upgrading to stay current. Need to use "feat" to trigger a release.
Docs: - https://python-semantic-release.readthedocs.io/en/latest/migrating_from_v7.html - https://github.com/pypa/gh-action-pypi-publish#usage
Fix README link to ci.yml
Just some housekeeping and local dev tweaks.
Add an @action decorator that behave's like Django's admin.action decorator1 to clean up
customizing object actions.
Also relates to #107
https://docs.djangoproject.com/en/stable/ref/contrib/admin/actions/#django.contrib.admin.action
This updates CI to use https://github.com/fabiocaccamo/create-matrix-action to simplify the config file. Poetry's lock file updated as I reinstalled on a new computer.
- Add [email protected] to CI (#133,
20e2418)
-
upgrade some more deps
-
add django 4.0 to ci
-
cleanup ci for Black
-
fix poetry's python version conflicts with CI version
BREAKING CHANGE: Python 3.6 is past end-of-life and is no longer supported. Keeping it in
pyproject.toml was causing pains trying to install packages. Let's drop it while we're dropping
support for other old stuff.
- Python 3.6 is past end-of-life and is no longer supported. Keeping it in
pyproject.tomlwas causing pains trying to install packages. Let's drop it while we're dropping support for other old stuff.
Fix "error: [Errno 2] No such file or directory: 'django-object-actions/init.py'" error when creating a release
To verify that it's getting packaged correctly. In particular, I need to make sure the .html files
are in the package.
- Add Python 3.9 & 3.10 support
(
28f0ef7)
-
ci: add Python 3.9-310 to the build
-
fix: support Python 3.9-3.10 in trove classifiers
I'll switch it to be automated on push to master at some point.
I'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't anticipate is that Github Actions caching doesn'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/
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.
https://docs.djangoproject.com/en/3.2/releases/3.2/
I really need to drop support for old versions now. Lots of deps are starting to step on each other and drop things. Django itself doesn't support Django 3.0 anymore with the release of Django 3.2
- release: 3.0.2
(
dbcecbf)
Use django.urls.re_path() when available, instead of the deprecated django.conf.urls.url().
re_path()is available since Django 2.0. *url()will be removed in Django 4.0.
for case if object in database has any of special symbols https://github.com/django/django/blob/master/django/contrib/admin/utils.py#L17 clicking on action button causes 404 error, as in SingleObjectMixin there are already parsed kwargs from url, and they are unquoted
made unquoting kwargs
- release: 3.0.1
(
fa48985)
- release: 3.0.0
(
6b61513)
Django 3.0 is out: https://docs.djangoproject.com/en/3.0/releases/3.0/ Let's see if we're compatible. It turns out no code changes are needed huzzah!
Pretty basic, looks like no code changes needed.
https://docs.djangoproject.com/en/3.1/releases/3.1/
BREAKING CHANGE: drop Python 3.4 support in preparation for adding type hints and Django 3.1 support
Prereq for #107
- release: 2.0.0
(
9169f0d)
BREAKING CHANGE: This release drops Python 2 support
Django has dropped Python 2 support ever since Django 2.0 (December 2, 2017). With Django 3.0 coming very soon and Python 2 reaching end of life, it doesn't make sense to continue supporting Python 2.
- This release drops Python 2 support
There's a lot of momentum to using Black. For example, Django will use it
This pulls the bandaid off to avoid mixing lint changes w/ code changes in the future. I opted to not dictate how Black is run because I'm not 100% sure how that should happen. To make sure PRs contributors are following this, I added a lint check in CI.
- release: 1.1.2
(
0cd8a24)
I probably copy pasted something wrong and brought an extra arg into the reverse, so reverse
never found anything and the actions in the changelist never rendered with a href. This makes
the args match the url definition so these buttons work again.
Thanks to @mvbrn for the original fix.
closes #96
-
greenkeeper
-
django-extensions is safe to upgrade now
-
use consistent DJANGO comment to indicate backwards compatibility
-
exclude sqlite from docker too
-
TODO
-
don't email failures
-
greenkeeper
-
add py37 and django2.1 to testing matrix
-
update coveralls to use latest versions
-
make sure to use factoryboy's version of Faker
-
add versions to travisci
-
use Factoryboy's fakersyntax
-
ugh
-
selective coveralls
-
add Django 2.2
-
disable coveralls in CI for nw
-
only build on PRs and master
-
don't commit .sqlite
-
add missing setting
-
fix broken test
-
haha need a script to run tests
With this change the default label changes from some_action to Some action
- More tweaks as I read code
(
936fe08)