fold-ng 0.3.0 → 0.5.1

package/CHANGELOG.md

@@ -8,6 +8,378 @@ All notable changes to **fold-ng** are documented here. The format follows
 
 _Nothing yet._
 
+## [0.5.1] - 2026-07-27
+
+First published 0.5.x — same tree as the (unpublished, e2e-gated) v0.5.0 tag with the release e2e locator scoped to the first control.
+
+## [0.5.0] - 2026-07-27
+
+### Added
+
+- **`fold-view-toggle` — a segmented single-select.** A compact Cards / Table
+  (or density, chart-mode…) switch, generic and zero-domain: pass `options`
+  (`{ value, icon?, label?, ariaLabel?, disabled? }`) and bind `[(value)]`. It's a
+  real `role="radiogroup"` of `role="radio"` segments — roving tabindex, arrow-key
+  selection, `Home`/`End`, disabled-skip — not two independent toggles. `size`
+  (`sm`/`md`), `iconOnly`, `activeStyle` (`raised` chip or `accent` brand tint),
+  `forced-colors`-aware. New gallery `/view-toggle` page.
+
+- **`fold-password-field` + `revealable` on `fold-input`.** A password input with
+  a **live requirements checklist** — a dot per rule that turns on as the value
+  satisfies it — built in two layers. `fold-input` gains a reusable `revealable`
+  (a show/hide eye toggle on a `type="password"` input); `fold-password-field`
+  composes it with the checklist. Rules are **injected**, not hard-coded: a
+  `FoldPasswordRule` is `{ label, test }`, so a `RegExp` (`foldRegexRule`), a
+  `zod` `safeParse`, a length check or anything drops in — `rules` defaults to a
+  sensible policy (`foldDefaultPasswordRules`). `validChange` emits when every
+  rule passes; Signal-Forms-native; the checklist is an `aria-live` list that
+  labels each row met / not met. The checklist is **redesignable**: project into
+  the `[rules]` slot and drive your own markup off the exported live state
+  (`#pw="foldPasswordField"` → `pw.checklist()`), with the default list as the
+  fallback. The built-in row marker is a `dot` (filling in) or a `check` tick
+  (`marker="check"`). New gallery `/password` page.
+
+- **`fold-popover` + `fold-dropdown` — anchored floating layer & actions menu.**
+  fold's first floating primitive. `fold-popover` renders projected content in
+  the native **top layer** (the `popover` attribute — escapes `overflow: hidden`
+  and every `z-index`), anchored to a projected `[foldPopoverTrigger]` by a
+  **dependency-free flip/shift engine** (`computePlacement`, exported and
+  unit-tested in isolation — no Floating UI). Controlled via `[(open)]`;
+  dismissal (outside-click + `Escape`) and focus-return are built in, and the
+  trigger gets `aria-haspopup`/`aria-expanded`/`aria-controls` wired
+  automatically. `fold-dropdown` (+ `fold-dropdown-item`) is the actions menu on
+  top: `role="menu"`, ↑/↓ roving tabindex, `Home`/`End`, type-ahead, opens onto
+  its first enabled item, closes returning focus to the trigger. New gallery
+  `/popover` page.
+
+  Hardened to a competitor benchmark (Floating UI / Radix): the placement engine
+  now does **flip → size → shift** — it picks the best-fitting side (preferred →
+  opposite → roomiest) and reports the available space so a tall panel gets a
+  `max-height` and **scrolls inside the viewport** instead of overflowing;
+  **autoUpdate** tracks the trigger + panel via `ResizeObserver` (not just
+  scroll/resize) so the anchor never drifts; an optional **`arrow`** points at
+  the trigger; **enter + exit transitions** are native CSS (`@starting-style` +
+  `transition-behavior: allow-discrete`, no JS timers); and the dropdown's
+  type-ahead is **multi-letter** (buffered); `fallbackPlacements` makes the flip
+  chain configurable; the `autoUpdate` helper is exported. Nested/sub-menus and
+  cursor-anchored context menus are tracked for a later pass.
+
+  Added a **Playwright interaction suite** (`pnpm test:e2e`, real Chromium) for
+  what jsdom can't reach — native top-layer open, box sizing, keyboard/focus.
+  It caught two focus bugs now fixed: the dropdown focused its first item
+  _before_ the popover had shown the panel (so keydowns missed the menu), and
+  focus-return targeted a non-focusable wrapper trigger (e.g. `fold-button-icon`)
+  instead of its inner control — the popover now resolves the focusable element
+  for both focus and the aria wiring.
+
+- **`fold-listbox` (+ `fold-option`) — a styleable single-select.** The richer
+  sibling of `fold-select` (which wraps a native `<select>`): reach for it when
+  options need custom rendering the OS popup can't give — an icon, a second line,
+  a status dot. Built on `fold-popover`, so it inherits the native top layer,
+  flip/shift positioning, outside-click + `Escape` dismissal and focus return.
+  On top it implements the ARIA select pattern — a `role="listbox"` that holds
+  focus and drives `aria-activedescendant` — with full keyboard (↑/↓, `Home`/
+  `End`, multi-letter type-ahead, `Enter`), a disabled-row skip, and a pure-CSS
+  selected check. Signal-Forms-native (`FormValueControl<string>`, so `[formField]`
+  and `[(value)]` both work) and shares `fold-input`'s box chrome (sizes, `panel`
+  variant). Options are dumb + presentational — each derives its own selected /
+  active state from the parent by `computed`, so nothing is pushed in during
+  change detection. New gallery `/listbox` page and a Playwright suite. Option
+  groups and a filter/combobox variant are tracked for later.
+
+- **`fold-multiselect` — the multi-select sibling.** Same styleable popover +
+  `fold-option` rows, but the value is a set (`readonly string[]`): activating a
+  row **toggles** its membership and the panel **stays open**. It's a separate
+  component, not a `multiple` flag, because the Signal-Forms value type genuinely
+  differs from single-select's `string` — keeping `[formField]` / `[(value)]`
+  honestly typed (no `any`). `role="listbox"` + `aria-multiselectable`, the same
+  keyboard core (`Enter`/`Space` toggle), each selected row keeps its check, and
+  the trigger summarises the picks. The keyboard/roving/type-ahead core and the
+  option↔owner contract are now **shared** between the two components (a
+  `FOLD_LISTBOX_OWNER` token instead of a concrete injection, which also removed
+  a circular import). New `/listbox` demo section + a Playwright suite.
+
+- **`fold-inline-confirm` — in-place destructive-action guard.** Extracted from
+  SH3PHERD's shared inline-confirm (which replaced four ad-hoc patterns) and
+  rebuilt to fold conventions. The host projects a real focusable trigger
+  (`foldButton` / `fold-button-icon`); on activation it is swapped, in the same
+  slot, for a confirm/cancel row — no modal, no layout jump. Three families:
+  **simple** (`confirmed` emits `""`), **type-to-confirm** (`[match]` — the
+  button unlocks once the text matches, case-insensitive + trimmed), and
+  **secret** (`password` — a masked field that confirms when non-empty and emits
+  the typed value, since a password can only be verified server-side). `Escape`
+  cancels; `Enter` confirms. Fully i18n via `provideFoldInlineConfirmLabels()`
+  (English default) or a per-instance `labels` input. Composed of `fold-button`,
+  `fold-button-icon` and `fold-input`. New gallery `/inline-confirm` page.
+
+  Hardened against a competitor benchmark (Radix `AlertDialog` / React-Aria):
+  the warning `message` is wired to the confirm button via `aria-describedby`
+  (so it is announced on focus, not stranded on the group); focus reliably
+  returns to the trigger on close (the previous attempt read the trigger before
+  it re-rendered and no-op'd); the trigger no longer double-fires on `Enter`.
+  New API: `confirmIcon` (leading icon on the confirm button) and `cancelIcon`
+  now takes an **icon name of your choice** (was a fixed `×`); a two-way
+  `[(open)]` model plus `keepOpenOnConfirm` give a controlled async story —
+  keep the affordance open, show `loading`, close it when the request settles.
+  16 spec blocks.
+
+- **Slider hardcore pass — `fold-slider` + `fold-range-slider`.** `fold-slider`
+  now implements `FormValueControl<number>` (bind `[formField]`, or `[(value)]`);
+  the visible label is a real `<label for>` (else `ariaLabel`); a `valueText`
+  override is announced via `aria-valuetext`; `hint` + touched-gated `errors`.
+  `fold-range-slider` gets a `model()` value (`[(value)]` parity), `disabled`,
+  and i18n thumb labels (`minLabel` / `maxLabel`, English default) resolving the
+  hardcoded aria suffixes; it's a labelled `role="group"` with formatted
+  `aria-valuetext` per thumb (duration reads `mm:ss`). Both share a hardened
+  thumb — a focus-visible ring (was invisible on keyboard focus),
+  `prefers-reduced-motion`, `forced-colors`, and tokenised motion. New gallery
+  `/slider` page; README rows; specs 12 → 20.
+
+- **`fold-paginator` hardcore pass.** Fully i18n — every string
+  (`Pagination`/prev/next/page/size/range/empty) is now overridable via
+  `provideFoldPaginatorLabels()` (English default) or a per-instance `labels`
+  input, resolving the last hardcoded-French portability blocker. Plus:
+  keyboard focus is preserved after a page change (moves to the active page, or
+  the prev/next arrow while it stays enabled — never dropped to `<body>`); the
+  visible range + active button clamp an out-of-range `currentPage` (a lagging
+  parent can't render a garbage range); the current `pageSize` is always in the
+  selector's options (the `<select>` can't show a phantom value); `disabled` is a
+  `booleanAttribute`; `siblingCount` is floored + zero-bounded. `@selector` + a
+  gallery `/paginator` page; specs cover DOM clicks, i18n, focus and the edges.
+
+- **`fold-checkbox` — the boolean form control.** A native
+  `<input type="checkbox">` (keyboard, focus, the `checkbox` role, form
+  submission and `indeterminate` all native) visually replaced by a tokenised
+  box + check/dash mark. Signal-forms native via `FormCheckboxControl` (bind
+  `[formField]`), or standalone `[(checked)]`; plus `indeterminate`, `label` /
+  `ariaLabel`, `hint` + touched-gated `errors`, `required`, `size` (`sm`/`md`),
+  `disabled`. Accessible by construction (visible label wraps the control, or a
+  required `ariaLabel` — dev-warns when neither is set), with a focus-visible
+  ring, `prefers-reduced-motion` and `forced-colors` handled. `fold-data-table`'s
+  selection column now uses it.
+
+- **`fold-data-table` — controlled row selection.** `selectable` renders a
+  checkbox column plus a header select-all with an indeterminate state over the
+  current rows; the parent owns the set via `selected` (a `Set` of row keys) and
+  `selectionChange` (emits the next set — the table never mutates). Selected rows
+  carry an accent tint + `aria-selected`, and a `selectionLabel` names each
+  checkbox. Toggling a checkbox never triggers `rowClick`.
+- **`fold-data-table` — `mobileLayout` (parent owns the small-screen shape).**
+  `scroll` (default — stay tabular, scroll horizontally; the table imposes no
+  card), `auto-cards` (each row stacks into a label/value card), or `custom` —
+  the parent supplies `<ng-template foldRowCard let-row>` (new
+  `FoldDataTableRowCardDirective`) and the table renders _that_ per row on mobile
+  instead of an imposed card. The table owns the chrome, not the content.
+- **`fold-data-table` — a `loading` state.** A fetching table now shows a
+  centred `fold-spinner` instead of the empty state, so an in-flight roster
+  reads as "loading", never as "no data".
+- **`fold-data-table` — an optional toolbar/title bar.** Project content with
+  `[foldToolbar]` (a title, a live count, a bulk-action bar that appears once
+  rows are selected) and it renders as a visible band above the column header —
+  the same content-projection idiom as `fold-card`'s `[cardHeader]`, collapsing
+  to nothing when the parent projects nothing. It stays put while the body
+  scrolls (the table now has an inner scroll region). `toolbarSurface` lends the
+  table a level —
+  `default` / `sunken` / `raised` / `accent` — mapped only to fold surface
+  tokens (no hard-coded colour); `accent` reuses the shared
+  `[data-surface="accent"]` machinery, so the bar's content auto-inverts to the
+  on-accent palette per theme.
+- **`fold-data-table` — an accessible `caption`.** A new `caption` input renders
+  a visually-hidden `<caption>` that names the table for assistive tech
+  (distinct from the visible `foldToolbar` title).
+- **`fold-data-table` — `stickyFirst` + `density`.** `stickyFirst` pins the
+  checkbox + identity columns while the body scrolls horizontally (opaque-backed
+  so tints don't bleed); `density="compact"` tightens the row padding.
+- **`fold-data-table` — column `align: "center"` and `truncate`.** `center`
+  joins `right`; `truncate` clips a column to one ellipsised line (pair with
+  `width`).
+- **`data-table` gallery page.** Added `/data-table` to the demo (live sort, row
+  select, keyboard nav, the loading + empty states, a custom mobile card, and a
+  playground for every flag).
+- **Select family — generic value + a data-driven `[options]` API.**
+  `fold-listbox` / `fold-multiselect` / `fold-option` are now generic over the
+  option value `T` (was `string`-only): `value` is `T | null` (single) /
+  `readonly T[]` (multi), and a `compareWith` input (default `Object.is`) matches
+  **object** values by identity — string/number/enum need nothing. On top of
+  projected `<fold-option>`, a `[options]="FoldSelectOption<T>[]"` array API links
+  the value type to the options at compile time (rich rows via a projected
+  `<ng-template #option let-o>`). The type stays honest end-to-end (`T` public,
+  the owner token erased to `unknown`, no `any`/`as`).
+- **`fold-data-table` — i18n label token.** `provideFoldDataTableLabels` +
+  `FoldDataTableLabels` + a `labels` input (same shape as the paginator), so the
+  select-all/select-row/sort/loading accessible strings are overridable per
+  locale instead of hardcoded English.
+- **`/changelog` — the CHANGELOG as a designed timeline.** A new gallery page
+  renders `CHANGELOG.md` as a vertical `fold-timeline` (one card per release,
+  category-count badges, breaking flagged) — parsed at build into a typed,
+  SSR-safe data file (runs pre-tokenised, no runtime markdown, no `innerHTML`).
+- **`/lab` — an "in dev" index.** A dedicated menu of exactly the components not
+  yet on npm, each linking to its page with the version it ships in. Both the
+  list and the `dev` rail badges are derived from each nav item's `since` vs the
+  published version, so they clear themselves the moment a release is cut.
+- **`pnpm eta` — a read-only release preview.** Prints the next version, the
+  derived bump level, and the reasons, straight from the CHANGELOG's
+  `[Unreleased]` section — no side effects.
+
+### Fixed
+
+- **0.5 review-hardening pass** (multi-agent review of the release). `fold-data-table`
+  accessible strings are now i18n-overridable (were hardcoded); `fold-password-field`'s
+  requirements checklist actually **announces** rule flips (the `aria-live` region
+  now carries the met/not-met word as text, not just an attribute) and forwards
+  the reveal labels; a `forced-colors` + `prefers-reduced-motion` sweep across
+  `fold-data-table`, `fold-paginator`, the `fold-input` reveal button, `fold-view-toggle`
+  and the select-family trigger; `fold-view-toggle`'s roving tab stop never lands
+  on a disabled segment (+ a dev warning for a missing `ariaLabel`);
+  `fold-inline-confirm`'s Escape is guarded while `loading`; `fold-dropdown`
+  excludes Space from type-ahead; slider spacing tokenised.
+
+- **Select family — a review-driven hardening pass** (`fold-listbox` /
+  `fold-multiselect` / `fold-popover`). Closing focus no longer traps: the
+  popover only pulls focus back to the trigger when it's still inside the closing
+  panel (Escape / pick) or nowhere — a `Tab` out now **advances** to the next
+  field like a native `<select>`. Dismissing the popup (Escape, outside-click,
+  Tab, or a pick) now marks the field **touched**, so a `required` select that's
+  opened and abandoned surfaces its error (blur parity). The trigger's
+  `aria-controls` points at the real `role="listbox"` (new `ariaControls` on
+  `fold-popover`), the active-row highlight and selected check get a
+  `forced-colors` treatment, and `fold-multiselect` membership is a `Set`
+  (O(1), not O(n²) across a long list) with the trigger summary collapsing to
+  "…, +N". Dev-mode now warns when a control holds a value with no matching
+  `<fold-option>`. New: `allowClear` on `fold-listbox` (a clear × once a value is
+  picked) and closed-trigger type-ahead (type to pick without opening).
+
+- **`fold-popover` panels are now opaque.** The panel used `surface-raised` — a
+  ~5% tint meant to _sit on_ an opaque surface — so on the top layer the page
+  bled through (visible while scrolling a long `fold-listbox`). It now composites
+  that tint over an opaque `surface-card` base. The popover also publishes its
+  trigger width as `--fold-popover-anchor-width`, and `fold-listbox` reads it for
+  a `min-width` — so the panel is never narrower than the trigger (a coherent
+  select look).
+
+- **Heading inputs no longer leak a native `title` tooltip.** A static
+  `title="…"` on a component that has a `title` input both seeds the input _and_
+  stays on the host as a real HTML attribute — so `fold-page-layout`,
+  `fold-page-section`, `fold-element-title`, `fold-context-card`,
+  `fold-empty-state` and `fold-panel-header` rendered their heading a second time
+  as a browser tooltip on hover. The reflected attribute is now stripped
+  (`host: { '[attr.title]': 'null' }`); `fold-icon` keeps its `title` on purpose
+  (it maps to `aria-label`).
+
+### Changed
+
+- **Form-control box metrics are single-sourced** (`_field-box.scss`). The size
+  and `panel` dimensions shared by the native inputs (`input-shell`) and the
+  select-family triggers (`_listbox-shell`) now live in one Sass mixin, so a
+  metric redesign lands in both instead of drifting.
+
+- **CI + release gates now run the Playwright browser tier.** The `test:e2e`
+  suite (native popover top layer, focus, positioning — behaviour jsdom can't
+  reach) is wired into both `ci.yml` (inside the single required `ci` job) and
+  `release.yml`, so a PR or a tag can't go green on a broken overlay.
+
+- **The release bump is derived from the CHANGELOG.** `pnpm release` with no
+  argument now reads `[Unreleased]` and derives patch/minor/major (0.x-aware:
+  breaking → minor, features → minor, else patch) — the changelog you curate
+  defines the version. An explicit level still overrides. Parser + derivation
+  live in a shared `scripts/lib/changelog.mjs`, reused by the release flow, the
+  `pnpm eta` preview, and the `/changelog` page.
+
+- **`fold-data-table` — clickable rows are a roving-tabindex group.** They now
+  answer Space as well as Enter (page-scroll suppressed) and Arrow Up/Down +
+  Home/End move focus between rows with a single tab stop — the ARIA grid
+  keyboard pattern, not a wall of tab stops.
+- **`fold-data-table` — sort indicators are now `fold-icon`s** (`expand-all` when
+  idle, `chevron-up` / `chevron-down` when active) rather than text glyphs, so
+  the direction cue is theme-aware, pixel-aligned, and consistent with the rest
+  of the system. The icon is decorative — `aria-sort` on the `<th>` stays the
+  accessible carrier.
+- Transitions now respect `prefers-reduced-motion`.
+- **`fold-data-table` hardening (hardcore-review follow-ups).** Row keydown now
+  fires only when the row itself is focused — keys bubbling from an inner control
+  (a link, a button, the selection checkbox) are no longer stolen or
+  double-handled; the roving tab stop survives the focused row being removed
+  (never strands the group with zero tab stops); the `custom` mobile layout no
+  longer instantiates its card list on desktop; `truncate` warns in dev when its
+  column lacks a `width` to clip against; `aria-colcount` + a "Sort by …" label
+  on the sort control; the checkbox-column width is a single source of truth.
+
+- **BREAKING (`fold-data-table`): the primary column renders as
+  `<th scope="row">`** (was a `<td>`) so screen readers announce each row by its
+  identity cell. Consumers that target the first cell with a `td`-specific
+  selector should switch to the `.folddt-cell` class (present on both the row
+  header and the data cells).
+- **BREAKING (`fold-data-table`): `mobileCards` (boolean) is replaced by
+  `mobileLayout`, and the default flips from cards to scroll.** A narrow-screen
+  table now stays tabular (scrolls) unless asked to stack. `[mobileCards]="true"`
+  (or unset) → `mobileLayout="auto-cards"` to keep the stacked cards;
+  `[mobileCards]="false"` → drop it (`scroll` is the default).
+
+## [0.4.0] - 2026-07-25
+
+### Added
+
+- **Auto-inverting accent surface.** A new `[data-surface="accent"]` region
+  (stamped by `fold-card surface="accent"`, `fold-hero-card surface="accent"`,
+  or the `foldSurface` directive) fills with the brand accent and re-points its
+  **whole content sub-tree** to an on-accent palette — text, borders, band
+  gradation, and even nested buttons / links / icon-tiles read on the accent
+  with no per-component code. It is theme-agnostic and derived (every value a
+  `color-mix` of the captured accent pair), and swaps the brand pair
+  (`primary` ↔ `on-primary`) without a CSS custom-property cycle by capturing on
+  the surface and inverting on descendants. A theme can override any role by
+  nesting a rule for its own `[data-theme=…]` under `[data-surface="accent"]`.
+  `FoldSurfaceName` gains `'accent'`. See `docs/surfaces.md`.
+- **On-accent contrast contract.** A contract test derives the on-accent text
+  ramp per theme and asserts it clears a documented WCAG floor (the accent is an
+  emphasis surface — AA-large 3:1 — or the theme must override the ramp). No
+  eyeballing.
+- **`fold-card` — an accessible interactive contract.** `interactive` cards are
+  now real controls: `role="button"`, `tabindex`, `Enter`/`Space` activation, an
+  `(activated)` output, an `ariaLabel` input, a visible focus ring, and
+  `prefers-reduced-motion` respected. The projected bands are neutral `<div>`s
+  (not `<header>`/`<footer>`), so a card is a single control with no nested
+  landmarks.
+- **`fold-link` — `target` + `rel` for external links.** A linked `fold-link`
+  takes `target` (e.g. `_blank`) and `rel`; `rel` defaults to a safe
+  `noopener noreferrer` whenever `target="_blank"`, and `(clicked)` now emits the
+  `MouseEvent` (so cmd/middle-click and modifier state are observable).
+- **`titan` theme — brushed titanium.** A fifth `[data-theme]`: a light, warm
+  brushed-steel read. A cool `steel` ground with the header + rails at the page's
+  own tint (a frameless top), bright polished cards floating off it on the shared
+  elevation shadow, and a heat-anodized `titanium` **copper-orange** brand.
+  Borders re-point to a **solid** steel primitive (a palpable machined seam, not
+  the alpha hairline the light themes share); corners soften a step in
+  `scales.css`. In the gallery both rails float as steel plates while the header
+  stays flat. Uniform-polarity, so no chrome override. The token contract (theme
+  parity, no-hex, no dead primitives) stays green.
+
+### Changed
+
+- **BREAKING — `fold-card` band chrome is per-band.** `separators` and
+  `raisedBands` change from booleans to a `FoldCardBandChrome`
+  (`'none' | 'header' | 'footer' | 'both'`), so a header and a footer are dressed
+  independently. Migration: `<fold-card separators>` → `separators="both"`;
+  drop the attribute for `'none'`.
+
+### Fixed
+
+- **`fold-avatar` — a broken image falls back to the initials** instead of the
+  browser's broken-image glyph, and retries when `imageUrl` changes. `ghost`
+  combined with `imageUrl` is no longer a silent no-op — a guest keeps the
+  dashed edge even with a photo.
+- **`fold-avatar` — initials stay legible on every palette fill.** The initials
+  ink is now the higher-contrast of the dark/light pair (was a magic-threshold
+  guess), and a contrast contract asserts every built-in palette fill clears AA
+  (≥ 4.5:1). A status-ring perceivability contract locks the `ring` colours
+  against a WCAG 1.4.11 regression.
+
+### Docs
+
+- **`docs/surfaces.md`** documents the auto-inversion principle and the
+  per-theme override seam; a `/surfaces` gallery page shows the live plain-vs-
+  accent proof. `docs/STRENGTHS.md` captures the top-tier design arguments.
+
 ## [0.3.0] - 2026-07-25
 
 ### Added
@@ -133,7 +505,10 @@ design-token stylesheet.
   `currentColor`; `prefers-reduced-motion` + `forced-colors` are respected;
   strings localise via inputs / providers (`provideFoldPanelLabels`).
 
-[unreleased]: https://github.com/hugoheynard/fold-ng/compare/v0.3.0...HEAD
+[unreleased]: https://github.com/hugoheynard/fold-ng/compare/v0.5.1...HEAD
+[0.5.1]: https://github.com/hugoheynard/fold-ng/releases/tag/v0.5.1
+[0.5.0]: https://github.com/hugoheynard/fold-ng/releases/tag/v0.5.0
+[0.4.0]: https://github.com/hugoheynard/fold-ng/releases/tag/v0.4.0
 [0.3.0]: https://github.com/hugoheynard/fold-ng/releases/tag/v0.3.0
 [0.2.1]: https://github.com/hugoheynard/fold-ng/releases/tag/v0.2.1
 [0.2.0]: https://github.com/hugoheynard/fold-ng/releases/tag/v0.2.0