Django-object-actions

Latest version: v4.2.0

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

Scan your dependencies

Page 1 of 5

4.2.0

Chore

* chore(deps): refresh dev dependencies (158)

Also moves Coverage config to `pyproject.toml` to eliminate another top
level project file ([`7d439b6`](https://github.com/crccheck/django-object-actions/commit/7d439b6910c2c30cd692bdb8819fe714f1b584a7))

* chore(ci): add Django 4.2 to the build matrix (154) ([`e73b4d0`](https://github.com/crccheck/django-object-actions/commit/e73b4d0d8921d566a880612f1622df87c99d062b))

* chore: fix formatting in example app (155)

Ran black on to comply with format from 23.x version ([`9bd288f`](https://github.com/crccheck/django-object-actions/commit/9bd288ffc6768bcf39ec27abde024b7be0ee90c9))

* 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`](https://github.com/crccheck/django-object-actions/commit/3e42b3be4fdced017f23234b5da2c17373fbc50b))

* 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 &39;packaging&39;`


https://github.com/python-semantic-release/python-semantic-release/issues/489

closes 144 ([`53417a0`](https://github.com/crccheck/django-object-actions/commit/53417a01bc78a9a7bb59f4599154d180914f064b))

Documentation

* docs: update README style (157)

To reduce future diffs from autoformat ([`f92464e`](https://github.com/crccheck/django-object-actions/commit/f92464e43e195dc3dede7f1102cf02e08c2845df))

Feature

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

Just upgrading to stay current. Need to use &34;feat&34; 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`](https://github.com/crccheck/django-object-actions/commit/6af5f367deb0f6787459058edbfdc92c1108be4e))

Fix

* fix(ci): maybe this will fix Semantic Release (161) ([`1595348`](https://github.com/crccheck/django-object-actions/commit/1595348d00235752857fef55f9fbbc8b854659d9))

* 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`](https://github.com/crccheck/django-object-actions/commit/70d2c8110e3c087366a67c4499fa0895035fbdfd))

4.1.0

Chore

* chore(ci): add Python 3.11 and Django 4.1 to CI (143)

Just some housekeeping and local dev tweaks. ([`10e4743`](https://github.com/crccheck/django-object-actions/commit/10e4743ad3df72a85f7f11844d22ddbe091398cf))

Feature

* feat: provide action decorator to pass label, description and atts to the admin method (141)

Add an `action` decorator that behave&39;s like Django&39;s `admin.action` decorator[^1] to clean up customizing object actions.

[closes 115](https://github.com/crccheck/django-object-actions/issues/115)

Also relates to 107

[^1]: https://docs.djangoproject.com/en/stable/ref/contrib/admin/actions/#django.contrib.admin.action ([`5638f99`](https://github.com/crccheck/django-object-actions/commit/5638f999d32ea7f6de60b895d23ce89624120769))

Fix

* fix: fix link to ci.yml in README (139)

Fix README link to ci.yml ([`700dd9b`](https://github.com/crccheck/django-object-actions/commit/700dd9b848aea67c759dca61cd815a27b6b16fd1))

4.0.0

Breaking

* feat!: drop Python 3.6 support (135)

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&39;s drop it while we&39;re dropping support for other old stuff. ([`8deebed`](https://github.com/crccheck/django-object-actions/commit/8deebedda55d0e5d466969c7f27a9c60e680e5e8))

Chore

* chore(deps): refresh dev deps and refactor CI (132)

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

Documentation

* docs: add Django4.0 to CI (133)

* upgrade some more deps

* add django 4.0 to ci

* cleanup ci for Black

* fix poetry&39;s python version conflicts with CI version ([`20e2418`](https://github.com/crccheck/django-object-actions/commit/20e2418e6ada4651b3e6d51b5d10c545d8a6c863))

Fix

* fix: cleanup Django compatibility shims for <2.0 (126) ([`88cfb3b`](https://github.com/crccheck/django-object-actions/commit/88cfb3b2e06b17762639da7f48259eeae343942f))

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&39;t support Django 3.0 anymore with the release of Django 3.2 ([`e473bc3`](https://github.com/crccheck/django-object-actions/commit/e473bc32777496d6e98e045b51f9d901384f4193))

Refactor

* refactor: Use django.urls.re_path instead of deprecated django.conf.urls.url (112)

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

3.1.0

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

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)

Page 1 of 5

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.