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 (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'

https://github.com/python-semantic-release/python-semantic-release/issues/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)

What's Changed

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

New Contributors

• @jgillard made their first contribution in https://github.com/crccheck/django-object-actions/pull/139
• @Alexerson made their first contribution in https://github.com/crccheck/django-object-actions/pull/141

Full Changelog: https://github.com/crccheck/django-object-actions/compare/v4.0.0...v4.1.0

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

⚠ 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)

⚠ 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)

Fix a broken publish

Added

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

Fixed

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

I didn't get around to everything I listed in #44 as a release blocker for 1.0,
but with Django going 2.0 and dropping backwards compatibility, I decided this
library needs some more stability. In the future look for more removals as
support for older versions of Django keep getting dropped.

https://github.com/crccheck/django-object-actions/compare/v0.10.0...v1.0.0

Added

• [430be02e59] - Add support for Django 2.0 (#85)

Changed

• [a7b183f3c1] - Cleanup random Django version support docs (#86)
• [81af3e7cd5] - Add a redirect example to the README (#82)

• Add support for Django 1.11 (#76 #78)

https://github.com/crccheck/django-object-actions/compare/v0.9.0...v0.10.0

• Fix how the demo site stopped working because of bad settings

• Fix how extra_context set by admins was not passed
• Fix how if you had multiple admins, you always got redirected to the default admin

• Renames objectactions to change_actions
• Removes get_object_actions (see below)
• Adds changelist_actions for creating action tools in the change list view too
• Adds get_change_actions and get_changelist_actions

Breaking changes

• Deleted get_object_actions(request, context, **kwargs). If you used this
  before, use get_change_actions(request, object_id, form_url) instead. To
  get at the original object, instead of context['original'], you can use
  self.model.get(pk=object_id), self.get_object(request, object_id), etc.
  This isn't as convenient as it used to be, but now it uses the officially
  documented way to add extra context to admin views.
  https://docs.djangoproject.com/en/dev/ref/contrib/admin/#other-methods

• Renamed objectactions. In your admin, instead of defining your actions in
  the objectactions attribute, use change_actions.

• Add support for all primary key formats (#75)
• Add support for Django 1.10 (#74)
• Documentation tweaks (#71 #70)

Removed

• Remove support for Django 1.6 (#73)

https://github.com/crccheck/django-object-actions/compare/v0.8.2...v0.9.0

Changes:

• Fixed deprecation warning RemovedInDjango110Warning: django.conf.urls.patterns() is deprecated and will be removed in Django 1.10. #46
• Fixed an issue in 0.6.0 where unnamed admin urls break things #49
• you can now return HttpStreamingResponse from a tool now #50

https://github.com/crccheck/django-object-actions/compare/v0.6.0...v0.7.0

Changes:

• Add Django 1.8 and 1.9
• Remove Django 1.4
• Fixes #40 Where .update did not work for queryset-ish querysets at the cost of a db hit

Known issues:

• #45 Error urls don't have a name

Full changes

• Fix how tools did not work when using UUID primary keys

• Added get_object_actions() method

• fixes a scope bug
• increases test coverage
• adds another way to integrate into projects

• Adds ability to set arbitrary attributes on the buttons's html