v4.3.0

v4.3.0 (2024-09-10)

Chore

• chore(ci): upgrade python-semantic-release to v9.8.8 (#176)

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 (50a03af)

• chore: update Django/Python test matrix and add classifier for py3.12 (#171) (ad3b898)

• chore: add Django v5 to CI matrix (#166)

https://docs.djangoproject.com/en/5.0/releases/5.0/ (b63aac1)

Documentation

• docs: add Django Modal Actions as a similar package (#173)

Adding new Django Modal Actions package
Deleting Django Object Actions which hasn't had a commit in 3 years (813687e)

Feature

• feat: add a way to make a POST only action (#174)

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. (494d581)

Style

• style: apply Black formatting (#170) (fb3ce5b)

Unknown

• wip to select GET or POST for actions (#168)

Another try at enforcing POST actions. This change is more gradual than
#149 - when library user doesn't change default options the behavior is
exactly the same as before the change, that is:

1. Action buttons send GET requests
2. Action handlers accept GET and POST requests

However, user can change this behavior using methods and button_type
kwargs. For example @action(methods=['POST'], button_type='form')
results in

1. Action button sends POST requests
2. Action handler accepts only POST request

Unfortunately I have this tested only within my project. Also the docs
are missing.

And one more thing - I think it is better to use <input type="submit">
instead of js to submit the form. This js is need to make the buttons
look the same in both versions. With proper CSS (that is beyond my
ability to write ;) ) js is avoidable and we could be using pretty
semantic html submit button. I took the form button template from #149. (1274ae7)

v4.2.0

v4.2.0 (2023-09-08)

Chore

• chore(deps): refresh dev dependencies (#158)

Also moves Coverage config to pyproject.toml to eliminate another top
level project file (7d439b6)

• chore(ci): add Django 4.2 to the build matrix (#154) (e73b4d0)

• chore: fix formatting in example app (#155)

Ran black on to comply with format from 23.x version (9bd288f)

• chore(ci): remove deprecated set-output syntax (#146)

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/ (3e42b3b)

• chore(ci): upgrade python-semantic-release (#145)

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 (53417a0)

Documentation

• docs: update README style (#157)

To reduce future diffs from autoformat (f92464e)

Feature

• feat: test release for new python-semantic-release process (#159)

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 (6af5f36)

Fix

• fix(ci): maybe this will fix Semantic Release (#161) (1595348)

• fix(ci): update [tool.semantic_release] names (#160)

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 (70d2c81)

v4.1.0

What's Changed

• fix: fix link to ci.yml in README by @jgillard in #139
• chore(ci): add Python 3.11 and Django 4.1 to CI by @crccheck in #143
• feat: provide action decorator to pass label, description and atts to the admin method by @Alexerson in #141

New Contributors

• @jgillard made their first contribution in #139
• @Alexerson made their first contribution in #141

Full Changelog: v4.0.0...v4.1.0

v4.0.0

Feature

• Drop Python 3.6 support (#135) (8deebed)

Fix

• Cleanup Django compatibility shims for <2.0 (#126) (88cfb3b)

Breaking

• 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. (8deebed)

Documentation

• Add [email protected] to CI (#133) (20e2418)

v3.1.0

Feature

• ci: Add manual semantic-release (#128) (f43fd11)
• Add Python 3.9 & 3.10 support (28f0ef7)

Fix

• Fix typo in version_variable (#130) (040a802)

v3.0.1

Bug Fixes

• Objects with special symbols in primary key 404-ed (#110) (0c90ce1), closes /github.com/django/django/blob/master/django/contrib/admin/utils.py#L17

v3.0.0

⚠ BREAKING CHANGES

• deps: drop Python 3.4 support in preparation for adding type hints and Django 3.1 support

Features

• deps: Add Django 3.1 support (#109) (2c7170e)
• deps: Drop Python 3.4 support (#108) (68519d4), closes #107
• add Django 3 test support (#106) (4eaf14c)

v2.0.0

⚠ BREAKING CHANGES

• 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.

Features

• Drop Python 2 support (#105) (551d2bb)

v1.1.2

Fix a broken publish

1.1.0

Added

• [4191afd] - feat: Make default labels prettier (#93)

Fixed

• [fb90869] - Return to preserved filters on change_list after object action (#88)