Django-object-actions

Latest version: v4.3.0

Safety actively analyzes 682244 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 5

3.0.2

Chore

* chore(release): 3.0.2 ([`dbcecbf`](https://github.com/crccheck/django-object-actions/commit/dbcecbfe67254f6fff64e670c443a6c1d662a9ff))

* chore: add Django 3.2 to test grid (117)

3.0.1

Chore

* chore(release): 3.0.1 ([`fa48985`](https://github.com/crccheck/django-object-actions/commit/fa48985e5da6acdc327eae72b97edcd387d8afba))

Fix

* fix: Objects with special symbols in primary key 404-ed (110)

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 ([`0c90ce1`](https://github.com/crccheck/django-object-actions/commit/0c90ce12a066baf873037eed415052074430d9d2))

3.0.0

Breaking

* feat(deps): Drop Python 3.4 support (108)

BREAKING CHANGE: drop Python 3.4 support in preparation for adding type hints and Django 3.1 support

Prereq for 107 ([`68519d4`](https://github.com/crccheck/django-object-actions/commit/68519d48fa8dd4d3b203981a52157841e5152774))

Chore

* chore(release): 3.0.0 ([`6b61513`](https://github.com/crccheck/django-object-actions/commit/6b615133608caab492fe13ec3403dab281520186))

Feature

* feat(deps): Add Django 3.1 support (109)

Pretty basic, looks like no code changes needed.

https://docs.djangoproject.com/en/3.1/releases/3.1/ ([`2c7170e`](https://github.com/crccheck/django-object-actions/commit/2c7170e3a73317a9417733a7ddfe0fabab84fe85))

* feat: add Django 3 test support (106)

Django 3.0 is out: https://docs.djangoproject.com/en/3.0/releases/3.0/ Let's see if we&39;re compatible. It turns out no code changes are needed huzzah! ([`4eaf14c`](https://github.com/crccheck/django-object-actions/commit/4eaf14c3caff36d5ab274835d38baef7e66213dc))

2.0.0

Breaking

* feat: Drop Python 2 support (105)

BREAKING CHANGE: This release drops Python 2 support

Django has [dropped Python 2 support](https://docs.djangoproject.com/en/2.2/releases/2.0/#python-compatibility) ever since Django 2.0 (December 2, 2017). With Django 3.0 coming very soon and Python 2 reaching end of life, it doesn&39;t make sense to continue supporting Python 2. ([`551d2bb`](https://github.com/crccheck/django-object-actions/commit/551d2bb2a66c5fd1c157b05c288032124affba41))

Chore

* chore(release): 2.0.0 ([`9169f0d`](https://github.com/crccheck/django-object-actions/commit/9169f0df7298169179407859368f50453ec064f0))

1.1.2

Chore

* chore(release): 1.1.2 ([`0cd8a24`](https://github.com/crccheck/django-object-actions/commit/0cd8a24ac7ae90a169735e4035ce89701f7cff20))

* chore: Use Black to format code (100)

There&39;s a lot of momentum to using [Black](https://github.com/psf/black). For example, [Django will use it](https://github.com/django/deps/blob/master/accepted/0008-black.rst)

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&39;m not 100% sure how that should happen. To make sure PRs contributors are following this, I added a lint check in CI. ([`42055a3`](https://github.com/crccheck/django-object-actions/commit/42055a391044a3d828531cb0ab7ff6abe4f5a659))

Documentation

* docs: add syntax highlighting (102) ([`399affa`](https://github.com/crccheck/django-object-actions/commit/399affa66664a65216c51346e96972eb5ae22499))

Unknown

* change README to Markdown to simplify things (104)

I&39;m not planning on doing a Sphinx site, so let&39;s use Markdown to make the documentation easier to maintain.

Part of 94 ([`2d2a689`](https://github.com/crccheck/django-object-actions/commit/2d2a689a0dd8d829ca84ffaee73b753473175935))

1.1.1

Chore

* chore: bump dev dependencies (95)

* greenkeeper

* django-extensions is safe to upgrade now

* use consistent DJANGO<v> comment to indicate backwards compatibility

* exclude sqlite from docker too

* TODO

* greenkeeper

* don&39;t email failures ([`fceff29`](https://github.com/crccheck/django-object-actions/commit/fceff29fffb1fc962e19a3175cace3e9434cbd74))

* chore: modernize some syntax, add Django 2.2 and Py37 (91)

* greenkeeper

* add py37 and django2.1 to testing matrix

* update coveralls to use latest versions

* make sure to use factoryboy&39;s version of Faker

* add versions to travisci

* use Factoryboy&39;s fakersyntax

* ugh

* selective coveralls

* add Django 2.2

* disable coveralls in CI for nw

* only build on PRs and master

* don&39;t commit .sqlite

* add missing setting

* fix broken test

* haha need a script to run tests ([`ba9eb1b`](https://github.com/crccheck/django-object-actions/commit/ba9eb1b9fba5f6eebfbb605e9002c43bb0b6bfc8))

Fix

* fix: changelist action links had no &39;href&39; (98)

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 ([`8b8aed3`](https://github.com/crccheck/django-object-actions/commit/8b8aed3b131cf60bc8823c703299f50cf84d9dcc))

Unknown

* v1.1.1 (99) ([`1226ca1`](https://github.com/crccheck/django-object-actions/commit/1226ca105e9e13a43a6b8a1562af0993c49a7081))

Page 2 of 5

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.