Tree: 011e5c005b

cached-config-operations

main

revert-7033-patch-1

test_dylint

0.10.0

0.11.0

0.12.0

0.13.0

0.9.0

1.0.0

1.1.0

1.10.0

1.11.0

1.12.0

1.13.0

1.13.1

1.14

1.14.1

1.14.2

1.15.0

1.15.1

1.16.0

1.16.1

1.16.2

1.16.3

1.17.0

1.18.0

1.19.0

1.2.0

1.20.0

1.21.0

1.22.0

1.22.1

1.22.2

1.23.0

1.23.1

1.24.0

1.25.0

1.25.1

1.25.2

1.26.0

1.27.0

1.28.0

1.28.1

1.29.0

1.29.1

1.29.2

1.3.0

1.30.0

1.30.1

1.30.2

1.30.3

1.30.4

1.30.5

1.31.0

1.32.0

1.32.1

1.32.2

1.32.3

1.32.4

1.32.5

1.32.6

1.32.7

1.33.0

1.33.1

1.33.2

1.34.0

1.34.1

1.34.2

1.34.3

1.35.0

1.35.1

1.35.2

1.35.3

1.35.4

1.35.5

1.35.6

1.35.7

1.35.8

1.36.0

1.37.0

1.4.0

1.5.0

1.6.0

1.6.1

1.7.0

1.8.0

1.9.0

1.9.1

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '011e5c005b'

${ noResults }

Commit Graph

2 Commits (011e5c005bcbb62bbe0ad3aa593d9ac0935f81f3)

Author	SHA1	Message	Date
tom27052006	b571efcadd	Migrate legacy Manager members to the Custom type Before this PR every member created with the Custom role was stored as Manager (3) and masqueraded as Custom (4) in API responses. With the masquerade removed, those members would suddenly surface as type 3, which current clients no longer support and the admin panel cannot render. Convert them to the now-persisted Custom type; access_all is preserved and the new manage_* flags stay false, matching the exact capabilities and appearance these members had before. The down migration converts Custom members back to Manager so older server versions (which cannot load type 4) keep working after a rollback.	2 weeks ago
tom27052006	1f6d457533	Add custom role permissions: Manage Users, Groups, Policies	3 weeks ago