Skip to content

chore(master): release 26.11.0 - #1890

Open
clevercloud-ci wants to merge 1 commit into
masterfrom
release-please--branches--master--components--components
Open

chore(master): release 26.11.0#1890
clevercloud-ci wants to merge 1 commit into
masterfrom
release-please--branches--master--components--components

Conversation

@clevercloud-ci

@clevercloud-ci clevercloud-ci commented Nov 5, 2026 •
edited
Loading

Copy link
Copy Markdown
Collaborator

🤖 I have created a release beep boop

26.11.0 (2026-11-12)

🚀 Features

  • cc-clipboard: add a secret property to prevent exposing the value in the button title (0afd9ce)

🐛 Bug Fixes

  • cc-addon-header: allow base properties in the loading state type (9363719), closes #1614
  • cc-input-text: do not expose the secret value in the clipboard button title (f80bee5), closes #1514
  • cc-link: do not treat mailto: and tel: links as opening a new window (c343de3), closes #1460
  • cc-logs-loading-progress: make the pause/resume button name more explicit (efc9219), closes #1035
  • cc-map: use dedicated types matching the actual points API (ca5bf1f), closes #1512
  • cc-product-card: keep a multi-word status badge on one line (d6dd7eb)
  • cc-toggle: wrap instead of overflowing when the available width is reduced (6a99cca), closes #1497

This PR was generated with Release Please. See documentation.

@clevercloud-ci
clevercloud-ci force-pushed the release-please--branches--master--components--components branch 4 times, most recently from 03014d1 to 9958bcd Compare November 12, 2026 13:45
@clevercloud-ci clevercloud-ci changed the title chore(master): release 26.10.2 chore(master): release 26.11.0 Nov 12, 2026
@clevercloud-ci
clevercloud-ci force-pushed the release-please--branches--master--components--components branch from 9958bcd to fd9832d Compare November 12, 2026 14:24
@clevercloud-ci
clevercloud-ci force-pushed the release-please--branches--master--components--components branch from fd9832d to 3a23ebd Compare November 12, 2026 15:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment