Skip to content

fix(deps): update entur packages (major) - #577

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/major-entur-packages
Open

fix(deps): update entur packages (major)#577
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/major-entur-packages

Conversation

@renovate

@renovate renovate Bot commented Aug 2, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@entur/form (source) 9.3.810.1.1 age confidence
@entur/icons (source) 9.0.410.0.3 age confidence
@entur/table (source) 4.10.165.0.4 age confidence

Release Notes

entur/design-system (@​entur/form)

v10.1.1

Compare Source

Note: Version bump only for package @​entur/form

v10.1.0

Compare Source

Bug Fixes
  • form, datepicker: announce feedback text to screen readers by default (10783dd)

    The live region is now rendered empty on mount and filled when a message
    appears, so screen readers pick up validation messages reliably.

    Messages default to role="status". Pass ariaAlertOnFeedback="alert" for
    messages that must interrupt what the screen reader is saying.

    Status icons are hidden from screen readers, so the feedback text needs to
    be understandable on its own.

    Note: datepicker feedback with variant negative or warning previously got
    role="alert" and now defaults to role="status".

  • form/feedback text: restore the symbol inside the error icon (4abb000)

    The inner circle of the error and negative icon referenced a custom
    property that does not exist, so the symbol lost its fill and blended
    into the icon background.

  • form/text field, form/text area: set aria-invalid for the negative variant (a932ec3)

    aria-invalid only checked the deprecated variant="error", so fields using
    variant="negative" were never marked invalid for screen readers.

Features
  • form/text area: forward ariaAlertOnFeedback so feedback is announced (440f401)

    TextArea never passed the prop on to BaseFormControl, so its feedback text
    was never announced to screen readers.

  • form: control how feedback text is announced with ariaAlertOnFeedback and feedbackProps (f555018)

    ariaAlertOnFeedback now defaults to 'status', so the feedback text is
    announced politely without setting any props. Pass true or 'alert' for
    role="alert" on messages that must interrupt the screen reader, or false to
    drop the live region entirely.

    feedbackProps forwards extra props to the feedback text. Your own role or
    aria-live there wins over ariaAlertOnFeedback.

10.0.2 (2026-08-13)

Note: Version bump only for package @​entur/form

10.0.1 (2026-08-06)

Bug Fixes
  • form/text area: keep the label legible on any background (5309457)

    The label no longer paints its own background patch. Text scrolling under it
    fades out instead, so the label reads correctly in light mode, dark mode,
    inside Contrast and on custom background colours.

v10.0.2

Compare Source

Bug Fixes
  • form, datepicker: announce feedback text to screen readers by default (10783dd)

    The live region is now rendered empty on mount and filled when a message
    appears, so screen readers pick up validation messages reliably.

    Messages default to role="status". Pass ariaAlertOnFeedback="alert" for
    messages that must interrupt what the screen reader is saying.

    Status icons are hidden from screen readers, so the feedback text needs to
    be understandable on its own.

    Note: datepicker feedback with variant negative or warning previously got
    role="alert" and now defaults to role="status".

  • form/feedback text: restore the symbol inside the error icon (4abb000)

    The inner circle of the error and negative icon referenced a custom
    property that does not exist, so the symbol lost its fill and blended
    into the icon background.

  • form/text field, form/text area: set aria-invalid for the negative variant (a932ec3)

    aria-invalid only checked the deprecated variant="error", so fields using
    variant="negative" were never marked invalid for screen readers.

Features
  • form/text area: forward ariaAlertOnFeedback so feedback is announced (440f401)

    TextArea never passed the prop on to BaseFormControl, so its feedback text
    was never announced to screen readers.

  • form: control how feedback text is announced with ariaAlertOnFeedback and feedbackProps (f555018)

    ariaAlertOnFeedback now defaults to 'status', so the feedback text is
    announced politely without setting any props. Pass true or 'alert' for
    role="alert" on messages that must interrupt the screen reader, or false to
    drop the live region entirely.

    feedbackProps forwards extra props to the feedback text. Your own role or
    aria-live there wins over ariaAlertOnFeedback.

10.0.2 (2026-08-13)

Note: Version bump only for package @​entur/form

10.0.1 (2026-08-06)

Bug Fixes
  • form/text area: keep the label legible on any background (5309457)

    The label no longer paints its own background patch. Text scrolling under it
    fades out instead, so the label reads correctly in light mode, dark mode,
    inside Contrast and on custom background colours.

v10.0.1

Compare Source

Bug Fixes
  • form, datepicker: announce feedback text to screen readers by default (10783dd)

    The live region is now rendered empty on mount and filled when a message
    appears, so screen readers pick up validation messages reliably.

    Messages default to role="status". Pass ariaAlertOnFeedback="alert" for
    messages that must interrupt what the screen reader is saying.

    Status icons are hidden from screen readers, so the feedback text needs to
    be understandable on its own.

    Note: datepicker feedback with variant negative or warning previously got
    role="alert" and now defaults to role="status".

  • form/feedback text: restore the symbol inside the error icon (4abb000)

    The inner circle of the error and negative icon referenced a custom
    property that does not exist, so the symbol lost its fill and blended
    into the icon background.

  • form/text field, form/text area: set aria-invalid for the negative variant (a932ec3)

    aria-invalid only checked the deprecated variant="error", so fields using
    variant="negative" were never marked invalid for screen readers.

Features
  • form/text area: forward ariaAlertOnFeedback so feedback is announced (440f401)

    TextArea never passed the prop on to BaseFormControl, so its feedback text
    was never announced to screen readers.

  • form: control how feedback text is announced with ariaAlertOnFeedback and feedbackProps (f555018)

    ariaAlertOnFeedback now defaults to 'status', so the feedback text is
    announced politely without setting any props. Pass true or 'alert' for
    role="alert" on messages that must interrupt the screen reader, or false to
    drop the live region entirely.

    feedbackProps forwards extra props to the feedback text. Your own role or
    aria-live there wins over ariaAlertOnFeedback.

10.0.2 (2026-08-13)

Note: Version bump only for package @​entur/form

10.0.1 (2026-08-06)

Bug Fixes
  • form/text area: keep the label legible on any background (5309457)

    The label no longer paints its own background patch. Text scrolling under it
    fades out instead, so the label reads correctly in light mode, dark mode,
    inside Contrast and on custom background colours.

v10.0.0

Compare Source

Bug Fixes
  • form, datepicker: announce feedback text to screen readers by default (10783dd)

    The live region is now rendered empty on mount and filled when a message
    appears, so screen readers pick up validation messages reliably.

    Messages default to role="status". Pass ariaAlertOnFeedback="alert" for
    messages that must interrupt what the screen reader is saying.

    Status icons are hidden from screen readers, so the feedback text needs to
    be understandable on its own.

    Note: datepicker feedback with variant negative or warning previously got
    role="alert" and now defaults to role="status".

  • form/feedback text: restore the symbol inside the error icon (4abb000)

    The inner circle of the error and negative icon referenced a custom
    property that does not exist, so the symbol lost its fill and blended
    into the icon background.

  • form/text field, form/text area: set aria-invalid for the negative variant (a932ec3)

    aria-invalid only checked the deprecated variant="error", so fields using
    variant="negative" were never marked invalid for screen readers.

Features
  • form/text area: forward ariaAlertOnFeedback so feedback is announced (440f401)

    TextArea never passed the prop on to BaseFormControl, so its feedback text
    was never announced to screen readers.

  • form: control how feedback text is announced with ariaAlertOnFeedback and feedbackProps (f555018)

    ariaAlertOnFeedback now defaults to 'status', so the feedback text is
    announced politely without setting any props. Pass true or 'alert' for
    role="alert" on messages that must interrupt the screen reader, or false to
    drop the live region entirely.

    feedbackProps forwards extra props to the feedback text. Your own role or
    aria-live there wins over ariaAlertOnFeedback.

10.0.2 (2026-08-13)

Note: Version bump only for package @​entur/form

10.0.1 (2026-08-06)

Bug Fixes
  • form/text area: keep the label legible on any background (5309457)

    The label no longer paints its own background patch. Text scrolling under it
    fades out instead, so the label reads correctly in light mode, dark mode,
    inside Contrast and on custom background colours.

entur/design-system (@​entur/icons)

v10.0.3

Compare Source

Note: Version bump only for package @​entur/icons

v10.0.2

Compare Source

Bug Fixes
  • icons: keep inline icon alignment independent of the app's CSS reset (2bffb5d)

    Inline icons now state baseline alignment themselves. In apps whose reset
    centers svg elements — Tailwind Preflight, several normalize variants —
    the 0.2em nudge used to double-correct and pushed the icon about 4px below
    the text, most visibly on the BreadcrumbItem separator.

v10.0.1

Compare Source

Note: Version bump only for package @​entur/icons

v10.0.0

Compare Source

Features
  • icons: add exports field for ESM-compatible module resolution (3b50337)

    Consumers no longer need bundler aliases to resolve ESM entry points.
    Declares explicit exports map with entries for main entrypoint,
    ./styles (CSS), ./dist/styles.css (compat), and ./package.json.
    Deep dist/ imports not listed will stop resolving.

  • icons: require React 18 as minimum peer dependency (13d4e88)

BREAKING CHANGES
  • icons: undocumented deep imports into dist/ may break.
  • icons: require React 18 as minimum peer dependency

9.0.4 (2026-07-03)

Note: Version bump only for package @​entur/icons

9.0.3 (2026-06-22)

Bug Fixes
  • icons: reduce CSS specificity of icon contrast selectors (2a3053b)

    Wrap .eds-contrast selectors in :where() to lower specificity from
    (0,2,0) to (0,1,0), preventing icon contrast styles from overriding
    component styles that depend on icons.

    NB: Contrast mode selectors now have lower specificity. Consumers with
    custom overrides targeting .eds-contrast .eds-icon__* may see changed
    cascade behavior.

9.0.2 (2026-06-08)

Bug Fixes
  • icons: rename NorWay partner icon to avoid collision with Norway flag (a5e1c3a)

    NorWay.svg and Norway.svg both resolved to NorwayIcon, causing consumers
    to get the bus company logo instead of the Norwegian flag.

9.0.1 (2026-06-08)

Bug Fixes
  • icons: correct viewBox padding for oversized icons (722c7fd)

    Icons had smaller viewBox than 16×16 canvas, causing them to render
    larger than other icons. Fixed by setting viewBox to 16×16 and shifting
    path coordinates to center the content with proper padding.

  • icons: preserve original colors for flag and logo icons (df099c9)

    Flag and Entur logo icons were incorrectly rendered in solid blue
    instead of their original multicolor designs.

entur/design-system (@​entur/table)

v5.0.4

Compare Source

Note: Version bump only for package @​entur/table

v5.0.3

Compare Source

Note: Version bump only for package @​entur/table

v5.0.2

Compare Source

Note: Version bump only for package @​entur/table

v5.0.1

Compare Source

Note: Version bump only for package @​entur/table

v5.0.0

Compare Source

Bug Fixes
  • table: remove React.FC in favor of typed function parameters (24e2193)

    React.FC no longer provides implicit children typing in React 18.
    Move type annotations directly to function parameters.
    Add explicit children prop to SortableHeaderCellButtonProps.

Features
  • table: add exports field for ESM-compatible module resolution (57ca3d4)

    Consumers no longer need bundler aliases to resolve ESM entry points.
    Declares explicit exports map with entries for main entrypoint,
    ./styles (CSS), ./dist/styles.css (compat), and ./package.json.
    Deep dist/ imports not listed will stop resolving.

  • table: require React 18 as minimum peer dependency (aed2ecd)

BREAKING CHANGES
  • table: undocumented deep imports into dist/ may break.
  • table: require React 18 as minimum peer dependency

4.10.16 (2026-07-03)

Note: Version bump only for package @​entur/table

4.10.15 (2026-06-22)

Note: Version bump only for package @​entur/table

4.10.14 (2026-06-08)

Note: Version bump only for package @​entur/table

4.10.13 (2026-06-08)

Note: Version bump only for package @​entur/table

4.10.12 (2026-06-05)

Note: Version bump only for package @​entur/table

4.10.11 (2026-05-13)

Note: Version bump only for package @​entur/table

4.10.10 (2026-04-16)

Note: Version bump only for package @​entur/table

4.10.8 (2026-03-16)

Note: Version bump only for package @​entur/table

4.10.6 (2026-02-20)

Note: Version bump only for package @​entur/table

4.10.5 (2026-02-05)

Note: Version bump only for package @​entur/table

4.10.4 (2026-01-28)

Note: Version bump only for package @​entur/table

4.10.3 (2026-01-23)

Note: Version bump only for package @​entur/table

4.10.2 (2026-01-23)

Note: Version bump only for package @​entur/table


Configuration

📅 Schedule: (in timezone Europe/Oslo)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@github-actions

github-actions Bot commented Aug 2, 2026

Copy link
Copy Markdown

Preview for this PR in dev (updated for commit 1b37b8e):

https://ent-shamash-dev--preview-577-renovate-major-entur-pack-spazj35z.web.app
(Expires Mon, 14 Sep 2026 19:33:56 GMT)

@renovate
renovate Bot force-pushed the renovate/major-entur-packages branch 2 times, most recently from 7fa82da to dd90e7d Compare August 12, 2026 02:51
@renovate
renovate Bot force-pushed the renovate/major-entur-packages branch 2 times, most recently from dd90e7d to 5c92f14 Compare August 13, 2026 15:37
@renovate
renovate Bot force-pushed the renovate/major-entur-packages branch from 5c92f14 to 1528a1a Compare August 20, 2026 12:04
@renovate
renovate Bot force-pushed the renovate/major-entur-packages branch from 1528a1a to f82162a Compare August 20, 2026 17:04
@renovate
renovate Bot force-pushed the renovate/major-entur-packages branch from f82162a to afd2b63 Compare August 26, 2026 10:43
@renovate
renovate Bot force-pushed the renovate/major-entur-packages branch from afd2b63 to b1180e9 Compare August 28, 2026 18:47
@renovate
renovate Bot force-pushed the renovate/major-entur-packages branch from b1180e9 to 1b37b8e Compare September 7, 2026 19:31
@sonarqubecloud

sonarqubecloud Bot commented Sep 7, 2026

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants