--- title: Releases description: Wat er in elke STACKIT-deployment van Basenet is veranderd, nieuwste eerst. sidebar: label: Nederlands hidden: true slug: releases/nl/page/72 --- > English version: [/releases/page/72](/releases/page/72) Elke versie is `YY.C.N`: het jaar, de Linear-cycle en de commit binnen die cycle. De beschrijvingen van de wijzigingen staan in het Engels, zoals ze in de commits zijn geschreven. Tijdens de build gegenereerd door `scripts/release-changelog.mjs`.
5577469

26.6.15

Wijzigingen sinds 26.6.13.

  1. Opgelost insolvency

    Derive the curator and failliet field labels from the insolvency type

    The insolventie matter variant's curator/failliet fields carried a fixed label ("Curator"/"Failliet") regardless of the matter's "Type insolventie" (rechtsgebied).

    BLI-1767BLI-1768#1028520a809

186e931

26.6.13

Geen wijzigingen voor gebruikers sinds 26.6.9.

7b3aaa2

26.6.9

Geen wijzigingen voor gebruikers sinds 26.6.6.

4facbfc

26.6.6

Wijzigingen sinds 26.6.4.

  1. Nieuw ui

    Tabs accepts a custom per-item trigger

    TabItem gains an optional `trigger?: ReactNode | ((item) => ReactNode)`, rendered in place of `label` inside the existing Ark.Trigger button. Additive only: items without `trigger` render exactly as before.

    BLI-1780#10214facbfc

  2. Nieuw ui

    Switch, Checkbox and Radio accept the native form-posting props

    Adds `required`/`form` to Switch, Checkbox and Radio (they already had `name`/`defaultChecked`/`defaultValue`), matching Select.tsx's reference form-posting pattern from PR #991. Each already renders an Ark hidden native input; this just forwards the two missing props to it.

    BLI-1782#1023612ae5a

bd97ef7

26.6.4

Wijzigingen sinds 26.6.2.

  1. Opgelost matters

    Stop the creditors tab reporting denied and invalid queries as 404

    A census of BLI-1774 ("matter 404 bug") could not reproduce a bug at the main matter route — its notFound()/NoAccess handling is deliberately correct.

    BLI-1774#1022bd97ef7

  2. Nieuw capabilities

    Surface each capability's enforced permission in the map and check it

    docs/capability-map.md never rendered permission.action/resourceType, and check-capability-registry.mjs only compared resourceType against the handler's authorization gate(s), not action — both gaps were flagged as "deliberately not done" at the end of BLI-1778.

    BLI-1783#102068d63ec