Dependency Update Report - 15/5/2025 🤖

[github-actions[bot]]

Dependency Update Report May 15, 2025 🤖📝

Available Update ⚙️

Dependencies

Package Name	Old Version	New Available Version	Type
@axe-core/playwright	4.10.0	4.10.1	Frontend
@nuxt/content	3.0.1	3.5.1	Frontend
@nuxt/devtools	1.7.0	2.4.1	Frontend
@nuxt/eslint	1.2.0	1.3.1	Frontend
@nuxt/eslint-config	1.2.0	1.3.1	Frontend
@nuxt/test-utils	3.15.4	3.18.0	Frontend
@nuxtjs/i18n	9.3.0	9.5.4	Frontend
@nuxtjs/tailwindcss	6.12.2	6.14.0	Frontend
@pinia/nuxt	0.9.0	0.11.0	Frontend
@playwright/test	1.51.1	1.52.0	Frontend
@tiptap/core	2.11.5	2.12.0	Frontend
@tiptap/extension-link	2.11.5	2.12.0	Frontend
@tiptap/extension-mention	2.11.5	2.12.0	Frontend
@tiptap/extension-placeholder	2.11.5	2.12.0	Frontend
@tiptap/pm	2.11.5	2.12.0	Frontend
@tiptap/starter-kit	2.11.5	2.12.0	Frontend
@tiptap/suggestion	2.11.5	2.12.0	Frontend
@tiptap/vue-3	2.11.5	2.12.0	Frontend
@types/node	22.12.0	22.15.18	Frontend
@unocss/reset	65.4.3	66.1.1	Frontend
@vueuse/core	12.5.0	13.2.0	Frontend
@vueuse/math	12.7.0	13.2.0	Frontend
@vueuse/nuxt	12.5.0	13.2.0	Frontend
axe-core	4.10.2	4.10.3	Frontend
axios	1.8.2	1.9.0	Frontend
dompurify	^3.2.4	^3.2.5	Frontend
dotenv	16.4.7	16.5.0	Frontend
eslint	9.22.0	9.26.0	Frontend
eslint-config-prettier	10.1.1	10.1.5	Frontend
eslint-plugin-perfectionist	^4.10.1	^4.13.0	Frontend
eslint-plugin-vue	10.0.0	10.1.0	Frontend
happy-dom	15.11.6	17.4.7	Frontend
maplibre-gl	^5.4.0	^5.5.0	Frontend
nuxt	3.16.1	3.17.3	Frontend
nuxt-mail	5.1.1	6.0.1	Frontend
pinia	2.3.1	3.0.2	Frontend
pinia-plugin-persistedstate	4.2.0	4.3.0	Frontend
playwright-core	1.51.1	1.52.0	Frontend
postcss	8.5.1	8.5.3	Frontend
prettier	3.4.2	3.5.3	Frontend
rollup	4.32.1	4.40.2	Frontend
swiper	11.2.1	11.2.6	Frontend
tailwind-scrollbar	3.1.0	4.0.2	Frontend
tailwindcss	3.4.17	4.1.6	Frontend
typescript	5.7.3	5.8.3	Frontend
unocss	65.4.3	66.1.1	Frontend
uuid	11.0.5	11.1.0	Frontend
vite	6.1.6	6.3.5	Frontend
vitest	3.0.5	3.1.3	Frontend
vue-i18n	10.0.6	11.1.3	Frontend
vue-sonner	1.3.0	1.3.2	Frontend
vue-tsc	2.2.0	2.2.10	Frontend
wait-on	8.0.2	8.0.3	Frontend
zod	3.24.1	3.24.4	Frontend
attrs	24.3.0	25.3.0	Backend
certifi	2024.12.14	2025.4.26	Backend
charset-normalizer	3.4.1	3.4.2	Backend
django	5.1.7	5.2.1	Backend
django-cors-headers	4.6.0	4.7.0	Backend
django-stubs	5.1.1	5.2.0	Backend
django-stubs-ext	5.1.1	5.2.0	Backend
djangorestframework	3.15.2	3.16.0	Backend
djangorestframework-stubs	3.15.2	3.16.0	Backend
jsonschema-specifications	2024.10.1	2025.4.1	Backend
packaging	24.2	25.0	Backend
pillow	11.1.0	11.2.1	Backend
python-dotenv	1.0.1	1.1.0	Backend
referencing	0.35.1	0.36.2	Backend
rpds-py	0.22.3	0.24.0	Backend
types-pyyaml	6.0.12.20241230	6.0.12.20250402	Backend
types-requests	2.32.0.20241016	2.32.0.20250328	Backend
typing-extensions	4.12.2	4.13.2	Backend
urllib3	2.3.0	2.4.0	Backend

Test Results

Mypy Results

usage: mypy [-h] [-v] [-V] [more options; see below]
            [-m MODULE] [-p PACKAGE] [-c PROGRAM_TEXT] [files ...]
mypy: error: Cannot find config file 'mypy.ini'

Django Tests

Found 5 test(s).
Traceback (most recent call last):
  File "/home/runner/work/activist/activist/backend/manage.py", line 31, in <module>
    main()
  File "/home/runner/work/activist/activist/backend/manage.py", line 27, in main
    execute_from_command_line(sys.argv)
  File "/home/runner/work/activist/activist/backend/.venv/lib/python3.11/site-packages/django/core/management/__init__.py", line 442, in execute_from_command_line
    utility.execute()
  File "/home/runner/work/activist/activist/backend/.venv/lib/python3.11/site-packages/django/core/management/__init__.py", line 436, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/home/runner/work/activist/activist/backend/.venv/lib/python3.11/site-packages/django/core/management/commands/test.py", line 24, in run_from_argv
    super().run_from_argv(argv)
  File "/home/runner/work/activist/activist/backend/.venv/lib/python3.11/site-packages/django/core/management/base.py", line 413, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/home/runner/work/activist/activist/backend/.venv/lib/python3.11/site-packages/django/core/management/base.py", line 459, in execute
    output = self.handle(*args, **options)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/runner/work/activist/activist/backend/.venv/lib/python3.11/site-packages/django/core/management/commands/test.py", line 63, in handle
    failures = test_runner.run_tests(test_labels)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/runner/work/activist/activist/backend/.venv/lib/python3.11/site-packages/django/test/runner.py", line 1066, in run_tests
    old_config = self.setup_databases(
                 ^^^^^^^^^^^^^^^^^^^^^
  File "/home/runner/work/activist/activist/backend/.venv/lib/python3.11/site-packages/django/test/runner.py", line 964, in setup_databases
    return _setup_databases(
           ^^^^^^^^^^^^^^^^^
  File "/home/runner/work/activist/activist/backend/.venv/lib/python3.11/site-packages/django/test/utils.py", line 189, in setup_databases
    test_databases, mirrored_aliases = get_unique_databases_and_mirrors(aliases)
                                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/runner/work/activist/activist/backend/.venv/lib/python3.11/site-packages/django/test/utils.py", line 319, in get_unique_databases_and_mirrors
    default_sig = connections[DEFAULT_DB_ALIAS].creation.test_db_signature()
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/runner/work/activist/activist/backend/.venv/lib/python3.11/site-packages/django/db/backends/base/creation.py", line 374, in test_db_signature
    self._get_test_db_name(),
    ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/runner/work/activist/activist/backend/.venv/lib/python3.11/site-packages/django/db/backends/base/creation.py", line 187, in _get_test_db_name
    return TEST_DATABASE_PREFIX + self.connection.settings_dict["NAME"]
           ~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
TypeError: can only concatenate str (not "NoneType") to str

Prettier Results

Checking formatting...
All matched files use Prettier code style!

Type Check Results

CardDiscussionInput.vue(151,5): error TS2322: Type 'Extension<StarterKitOptions, any>' is not assignable to type 'AnyExtension'.
CardDiscussionInput.vue(183,33): error TS2339: Property 'toggleHeading' does not exist on type 'ChainedCommands'.
CardDiscussionInput.vue(187,33): error TS2551: Property 'toggleBold' does not exist on type 'ChainedCommands'. Did you mean 'toggleNode'?
CardDiscussionInput.vue(191,33): error TS2339: Property 'toggleItalic' does not exist on type 'ChainedCommands'.
CardDiscussionInput.vue(195,33): error TS2339: Property 'toggleBlockquote' does not exist on type 'ChainedCommands'.
CardDiscussionInput.vue(226,33): error TS2339: Property 'toggleBulletList' does not exist on type 'ChainedCommands'.
CardDiscussionInput.vue(230,33): error TS2339: Property 'toggleOrderedList' does not exist on type 'ChainedCommands'.
[error] Process exited with non-zero status (2)
[error] Process exited with non-zero status (2)

[andrewtavis]

This is looking great, @Abhi-Bohora! One thing is that it looks like the title of the issue isn't being converted into a date. Would you have a moment to look into that?

[andrewtavis]

Also the mypy tests are not running still 🤔 Aside from that the results are looking good 😊 What do you think, @Abhi-Bohora? :)

[Abhi-Bohora]

@andrewtavis Hello, I have raised an PR I hope that should fix the issue where the date in the title is not being formatted. I believe this was happening because when the Github action runner creates an issue from the file it doesn't execute commands in the title parameter, so our date remained as it is like the text 😊

[Abhi-Bohora]

@andrewtavis I am looking into mypy tests, I will update you 😊

[andrewtavis]

Fix made total sense, @Abhi-Bohora! Thanks for checking into the mypy tests! Really looking forward to this being finalized and getting up and running with it 😊

[Abhi-Bohora]

Hello @andrewtavis I think there is no any mypy.ini file in our backend that's why this mypy tests are not running, I guess? 🤔 I have searched for it, I cannot find it and error is also saying mypy: error: Cannot find config file 'mypy.ini'

[andrewtavis]

Ahhhh, yes! Looks like the original contributor used the wrong command and it slipped through. It should be mypy ./backend --config-file ./backend/pyproject.toml, which is what we use in .github/workflows/pr_ci_backend.yaml. We need the commands from the backend CI check and .github/workflows/pr_ci_frontend.yaml accounted for, as long as they make sense.

Do you want to send along a PR that changes that and do a check of the other commands in the dependency check to make sure that they match their respective PR workflows? We should be good then!

[andrewtavis]

I guess it would also make sense to include the Ruff tests from .github/workflows/pr_ci_backend.yaml and also rename Django tests to Pytest. For .github/workflows/pr_ci_frontend.yaml it'd make sense to run ESLint and Vitest too, and then that'll be all the major tests that we run on PRs 😊

[andrewtavis]

I'm gonna close and run this again, @Abhi-Bohora :)

[andrewtavis]

Hmmmm, there were too many characters in the dependency update 🤔 See here: https://github.com/activist-org/activist/actions/runs/15572349696/job/43850686213. Then we need to really work on this 🤔 I'll reopen this for now and we can take down some of these so we can run it again!

[Abhi-Bohora]

@andrewtavis Hello, ohh, yeah I think there were too many messages generated by our workflow and it exceeds the limit how many characters issue body can fit maybe it was due to last time we did updated the check_dependency_updates.yaml workflow to match the tests from both PR CI frontned and backend in this pr 1293

I think we should isolate this workflow to check only which latest dependencies are available, and other specific backend and frontend related workflow should be ran, separately ? It makes more sense to run backend and frontend check workflow when someone make changes to those specific directory, or in pull request ?? what do you think 🤔

[andrewtavis]

I think that maybe even the way it is now is fine, @Abhi-Bohora, as what it's conveying to me is that we have a ton of dependencies that need to be accounted for. Let's see if we can get the workflow to run by updating things, and if so then maybe when it doesn't run we know that it's a priority?

[andrewtavis]

Ping @sh-ran on this issue here :) Would be great if you could focus on getting some of the backend dependencies updated 😊

[sh-ran]

Hello! @andrewtavis

I was wondering if I should just change the requirements-dev.txt file and send in the PR?

[andrewtavis]

You'd change both .in requirements files and then run the processes to update the .txt files that are listed at the top of the .in files :)

[andrewtavis]

CC @UnknownSean8 for the issue here :) Feel free to look into the frontend while @sh-ran looks into the backend. For both of you, really no stress on this. Just update the easy ones and then we can rerun this once a few dependencies have been updated and the check can be ran :)

[andrewtavis]

@sh-ran did the backend updates in #1331, so we're in good shape. The workflow still doesn't run as now we have the $t vue-i18n issue from #1025 all over the place in the output, which is basically making the output way too big to create a GitHub issue from 🤔