Ensure instance-state updates when collections are PUT or DELETE-ed #252
2026-07-07
chore: adapt linter suggestions
All checks were successful
Codespell / Check for spelling errors (push) Successful in 40s
Codespell / Check for spelling errors (pull_request) Successful in 41s
Ruff / Code linting (push) Successful in 52s
Ruff / Code linting (pull_request) Successful in 49s
Type annotation (PR) / check (pull_request) Successful in 1m20s
Test execution / Test-all (push) Successful in 1m25s
chore: fix type-annotation errors
Some checks failed
Codespell / Check for spelling errors (pull_request) Successful in 43s
Codespell / Check for spelling errors (push) Successful in 48s
Ruff / Code linting (push) Failing after 53s
Ruff / Code linting (pull_request) Failing after 51s
Type annotation (PR) / check (pull_request) Successful in 1m21s
Test execution / Test-all (push) Successful in 1m33s
tests: add test for instance-state updates
Some checks failed
Codespell / Check for spelling errors (push) Successful in 41s
Codespell / Check for spelling errors (pull_request) Successful in 41s
Ruff / Code linting (push) Successful in 52s
Ruff / Code linting (pull_request) Successful in 51s
Type annotation (PR) / check (pull_request) Failing after 1m13s
Test execution / Test-all (push) Successful in 1m26s
Add a test that ensures that instance-state is updated when a collection is `PUT` or `DELETE`-ed.
2026-07-06
fix: fix collection deletion
Delete all collection-related objects from instance state, when a collection is deleted via the administration API. This fixes a problem where PUT /collection would not modify, e.g., configurations of authentication sources.