Skip to content

fix(deps): update dependency @adobe/spectrum-wc - #56

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate
Open

fix(deps): update dependency @adobe/spectrum-wc#56
renovate[bot] wants to merge 1 commit into
mainfrom
renovate

Conversation

@renovate

@renovate renovate Bot commented Jun 13, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@adobe/spectrum-wc (source) 2.0.0-beta.0 → 2.0.0-snapshot-test.20260824192735 age confidence
algoliasearch (source) 5.56.0 → 5.57.0 age confidence
esbuild 0.28.1 → 0.28.2 age confidence

Release Notes

adobe/spectrum-web-components (@​adobe/spectrum-wc)

v2.0.0-snapshot-test.20260824192735

Compare Source

v2.0.0-snapshot-test.20260728023631

Compare Source

v2.0.0-next.20260728161641

Compare Source

v2.0.0-beta.2

Minor Changes

  • #​6410 b0c6e37 - Add the 2nd-gen <swc-close-button>, migrated from the Spectrum 1 <sp-close-button>.

    • API: size, disabled, accessible-label, and static-color; omits the legacy variant surface in favor of static-color.
    • Accessibility: renders a real inner <button type="button"> with delegated focus; requires accessible-label for its icon-only name; the cross icon remains decorative.
    • Styling: ships Spectrum 2 sizing and static-color treatments plus the --swc-close-button-* custom-property surface for token-aligned overrides.
    • Docs and tests: includes Storybook docs, consumer migration guidance, unit coverage, and Playwright accessibility and keyboard tests.

  • #​6480 f27f690 - feat(color-handle): Added <swc-color-handle>, the Spectrum 2 migration of sp-color-handle.

    A non-interactive color-picker primitive exposing color, disabled, focused, open, and the new fill property, with a built-in <swc-color-loupe> and an adaptive white-first dual border that meets WCAG 1.4.11 non-text contrast across the color spectrum. The --mod-colorhandle-* custom properties are removed; see the migration guide.

  • #​6486 bf02e76 - feat(live-selection-controller): Added LiveSelectionController, a Lit reactive controller that enforces a selection constraint (single or multiple) on a group of items that each own their own selected state.

    Use it for patterns like accordions and disclosure groups where items manage their own open or selected property and can change that state on their own initiative. Unlike a cache-authoritative controller, it reads item state live from the DOM on each observed event rather than maintaining an internal list, so it stays correct even when items change themselves outside a controller-driven transition.

    The accordion (swc-accordion) now uses LiveSelectionController internally to enforce its exclusive-open constraint; its public API and behavior are unchanged.

  • #​6476 e2a7e4e - fix(tabs): Changed the default keyboard-activation on <swc-tabs> from manual to automatic, aligning with React Spectrum/React Aria Tabs.

    swc-tab-panel content is always present in the light DOM (not lazily mounted), which is the condition the WAI-ARIA APG recommends for automatic activation. Consumers relying on the previous implicit manual default (inherited from 1st-gen sp-tabs' auto = false) should add keyboard-activation="manual" explicitly, particularly if their own panel content is expensive to render or lazy-loaded.

  • #​6501 9592f85 - Spectrum WC — Added a published Custom Elements Manifest for editor, documentation, and integration tooling.

  • #​6488 6eccec9 - feat(progress-bar): Added <swc-progress-bar>, the Spectrum 2 migration of Progress Bar.

    Renames from <sp-progress-bar>: progress becomes value, side-label becomes label-position="side", the label string attribute becomes a label named slot, and --mod-progressbar-* custom properties become --swc-linear-progress-*. The default size is now 'm'.

    New in Spectrum 2: min-value / max-value for arbitrary numeric ranges, static-color="black", value-label, a formatOptions property, accessible-label, and a description slot. over-background is removed in favor of static-color="white", and role="progressbar" plus the aria-value* attributes now live on an internal element rather than the host. See the Progress Bar migration guide for full upgrade steps.

  • #​6494 9e7995a - refactor(tabs): Migrate <swc-tabs> keyboard navigation to FocusgroupNavigationController.

    Arrow-key, Home, and End navigation is now handled by the controller rather than by manually computed deltas in handleKeyDown. The handleKeyDown method retains only Enter/Space activation; all roving-tabindex management is delegated to the controller. In automatic activation mode, focusgroupNavigationActiveChange events with source: 'keyboard' drive selection-follows-focus; events with source: 'refresh' or source: 'programmatic' are intentionally ignored so that mounting or toggling disabled cannot trigger spurious change events.

Patch Changes

  • #​6518 36052f3 - Fix inaccurate API reference tables for several 2nd-gen components by documenting CSS custom properties and JSDoc property descriptions that were missing from the generated Custom Elements Manifest.

    • Added missing @cssprop entries: swc-tabs/swc-tab (5 props), swc-action-button and swc-button (down-state transform, button also gets max-inline-size), swc-illustrated-message (10 props covering illustration sizing/color and heading/description typography).
    • Added missing size/variant property descriptions for swc-button, swc-action-button, swc-close-button, swc-status-light, and swc-badge.
    • Fixed the Tabs docs page rendering only swc-tabs's API table; swc-tab and swc-tab-panel (the other two elements of the three-element component) now get their own API tables too, matching the pattern already used by Accordion.

    No component runtime changes; documentation and Storybook docs-page rendering only.

  • #​6513 41e0483 - fix(color-loupe): Added an adaptive white-first inner border to <swc-color-loupe> so its chrome meets WCAG 1.4.11 non-text contrast (≥3:1) across the color spectrum.

    The inner border's opacity now escalates above its default floor only when the white outer halo can't itself carry 3:1 contrast against the loupe's color. The outer border, shape, and sizing are unchanged, and there is no public API change. This supersedes the prior practical-limits exception, matching the adaptive dual-border approach already shipped for <swc-color-handle>.

  • #​6519 c28d00c - Fix the broken @import in the published global-link.css. The build flattens all stylesheets into dist/ root, but global-link.css shipped with @import url("../link.css") (relative to its source subfolder), which pointed one directory above dist/ and failed to resolve for consumers of @adobe/spectrum-wc/global-link.css. Local @import targets are now rewritten to sibling references (./link.css) during the flatten.

  • #​6457 8c4acae - fix(illustrated-message): Fixed the actions slot content alignment in <swc-illustrated-message>.

    The .swc-IllustratedMessage-content flex container was missing align-items: center, causing slotted actions (e.g. a <swc-button> or <swc-button-group>) to stretch to the container width instead of centering horizontally.

  • #​6506 6049706 - fix(popover): Fixed swc-popover staying dismissed on the next unrelated outside click after a trigger press was dragged off and released elsewhere.

    A pointerdown on the trigger followed by a drag off the trigger and a release elsewhere never dispatches a click, so the internal reopen-guard flag was left stuck true, misattributing the next unrelated outside light-dismiss to that stale press and swallowing the following legitimate trigger click.

  • #​6490 1e053fe - fix(slot-attribute-propagation-controller): Fixed SlotAttributePropagationController permanently skipping re-propagation when a repeated value was recorded before its target slot had resolved, and added support for propagating attributes that are only sometimes present on the host.

    getValue may now return null to remove the propagated attribute from assigned elements instead of setting it to an empty string. The hostUpdated() no-op guard now only records a value as applied once the slot actually resolves, so a slot that resolves after an earlier unsuccessful attempt with the same value is no longer skipped forever.

    SlotAttributePropagationController is also now a public export of @adobe/spectrum-wc-core (@spectrum-web-components/core/controllers/slot-attribute-propagation-controller.js), alongside dedicated tests and a Storybook controller docs page. Existing consumers (<swc-button-group>, <swc-illustrated-message>) are unaffected aside from benefiting from the propagation-guard fix.

  • #​6439 7f0c3e9 - Extract the pending (busy) state into reusable, decoupled 2nd-gen core primitives so any pending-capable component can adopt it.

    • @adobe/spectrum-wc-core: adds PendingController (/controllers/pending-controller) for the pending state (delayed activation, inline-size freeze, derived busy accessible name), the render-only renderPendingSpinner directive (/directives/pending-spinner), and PendingMixin (/mixins) which wires the controller, the pending / pending-label properties, and click suppression. ButtonBase no longer owns pending state.
    • @adobe/spectrum-wc: swc-button and swc-action-button now consume these primitives via PendingMixin. No public API change — pending / pending-label and the busy behavior are unchanged.

  • #​6533 5da5474 - fix(progress-circle): Replaced the animation: none reduced-motion override on <swc-progress-circle>'s indeterminate state with a slowed, single-rotation animation driven by custom properties (--swc-progress-circle-rotate-start, --swc-progress-circle-rotate-end, --swc-progress-circle-dashoffset-30), so prefers-reduced-motion: reduce still conveys progress without the distracting spin.

  • #​6462 2865959 - Refine the 2nd-gen response status pattern API, animation, and docs.

    • Added: Header label roll animation on text changes; update cadence remains consumer-managed.
    • Added: <swc-response-status-step> as a dedicated step element with its own styles and exports.
    • Updated: Conversational AI stories, docs, and regression/a11y coverage for the new API and behaviors.

  • Updated dependencies [36052f3, b0c6e37, f27f690, 41e0483, 9e7995a, 1e053fe, 7f0c3e9, 5da5474, 6049706]:

v2.0.0-beta.1

Minor Changes

  • #​6268 abe7cbd Thanks @​rise-erpelding! - feat(accordion): Add 2nd-gen <swc-accordion> and <swc-accordion-item> with Spectrum 2-oriented behavior. Key changes from 1st-gen <sp-accordion> / <sp-accordion-item>:

    • Core AccordionBase / AccordionItemBase with public API: allow-multiple, level, size, density, quiet, host disabled, item open / disabled, slotted heading (slot="label"), optional slot="actions", and cancellable swc-accordion-item-toggle
    • APG-aligned accessibility: <h*> wrapping a native header <button>, aria-expanded / aria-controls, role="region" + aria-labelledby, closed panels use aria-hidden="true" plus CSS collapse (not HTML hidden; supports calc-size() height animation), disabled items use aria-disabled on the header and inert on the panel (no roving tabindex or arrow-key header navigation)
    • Space on the header calls preventDefault() and toggles without scrolling overflow containers (SWC-1487)
    • Controlled open is frozen while the host or item is disabled (imperative assignment cannot expand or collapse)

    chore(accordion): Add Spectrum 2 deprecation warnings in dev mode on 1st-gen accordion for label, item level, and host focus(), with matching tests.

  • #​6340 57a77bc Thanks @​cdransf! - Added <swc-action-button> with full Spectrum 2 visual fidelity, migrated from the Spectrum 1 <sp-action-button>. See the component docs and migration guide.

    • API: accessible-label replaces label; size includes xs (not on swc-button); quiet and static-color retained as primary visual differentiators; pending / pending-label added (matching swc-button); aria-haspopup / aria-expanded forwarded to the inner <button> for menu-trigger patterns.
    • Breaking changes: toggles, selected, emphasized, and aria-pressed removed (toggle UX moves to swc-toggle-button / swc-toggle-button-group); href and the link API removed (use native <a>); hold-affordance / longpress deferred; label renamed to accessible-label.
    • Accessibility: semantics and focus land on the internal native <button> (delegatesFocus: true); host carries no role="button"; aria-disabled="true" on the inner <button> during pending state; dev-mode warning when icon-only usage is missing accessible-label.
    • Styling: exposes --swc-action-button-* custom properties (replaces --mod-actionbutton-* / --spectrum-actionbutton-*); full Spectrum 2 token coverage across all size × quiet × static-color combinations; Windows High Contrast support.
    • Docs and tests: per-component Storybook docs page, consumer migration guide, and full unit + accessibility test coverage.

  • #​6395 b4740eb Thanks @​Rajdeepc! - - #​6395 acd555a - ButtonGroup — Added <swc-button-group> with full Spectrum 2 visual fidelity. See the component docs and migration guide.

  • #​6454 591fa65 Thanks @​cdransf! - Added an actions slot to <swc-illustrated-message> for placing a <swc-button> or <swc-button-group> below the description. The component automatically propagates its size to every slotted element. Also adds SlotAttributePropagationController, an internal Lit ReactiveController that propagates any host attribute to slotted children; used by IllustratedMessage and ButtonGroup.

  • #​6382 a314298 Thanks @​aramos-adobe! - Link — Added 2nd-gen link styles for native <a href> elements (no swc-link custom element). Default prose and link-list appearance ships with Typography; explicit modifiers live in link.css, with optional global-link.css for application-wide bare-anchor baseline. See the component docs and migration guide. Consumer action: replace <sp-link> with native <a href> and the classes or Typography wrappers documented in the migration guide.

Patch Changes
algolia/algoliasearch-client-javascript (algoliasearch)

v5.57.0

Compare Source

evanw/esbuild (esbuild)

v0.28.2

Compare Source

  • Fix tree shaking bug due to TypeScript import alias (#​4507)

    This release fixes a bug that could cause esbuild to incorrectly tree-shake imports that are used in a TypeScript type alias under certain circumstances. Affected code uses a TypeScript-specific import assignment and looks something like this:

    import Base from './dep.js';
import Alias = Base.SomeType;

  • Fix CSS minification bug involving & (#​4497)

    This release fixes a bug where esbuild's CSS minifier incorrectly removed a & when it was unsafe to do so. Here is an example:

    /* Original code */
.a .b {
  & .b:not(& .c) {
    color: red;
  }
}

/* Old output (with --minify) */
.a .b{.b:not(& .c){color:red}}

/* New output (with --minify) */
.a .b{& .b:not(& .c){color:red}}

    This should match <span class="a"><span class="b"><span class="b">yes</span></span></span> but not <span class="a"><span class="b">no</span></span>. The old output incorrectly matched both.

  • Avoid overwriting input files without --allow-overwrite (#​4484)

    For example: esbuild input.js --outfile=input.js tells esbuild to overwrite input.js with the output of running esbuild on it. This was supposed to already be prevented by default, but it accidentally regressed in version 0.17.0 and apparently didn't have any test coverage. The error message was being printed but the input file was still being overwritten. Oops.

    This release puts the original behavior back. With this release, esbuild should now actually avoid overwriting input files unless --allow-overwrite is explicitly present. This is done by not writing out any files when a build error is encountered.

  • Fix incorrect code generated when using top-level await (#​4498)

    Previously esbuild could generate code containing a syntax error in complex scenarios involving top-level await used in a dependency cycle. The problem was a missing async on one or more module wrapper closures. With this release, esbuild now uses a fixed-point iteration algorithm to correctly annotate all dependencies in the cycle as needing an async module wrapper.

  • Fix a minification bug with lowered logical assignment operators (#​4508)

    This release fixes a bug that could cause esbuild to generate incorrect code for logical assignment operators when lowering them to an older target environment. Specifically the lowering process requires duplicating the left-hand side, but esbuild incorrectly failed to count the duplicate as a new usage when the left-hand side is an identifier. That then caused the minifier to believe that the left-hand side was only used once and could attempt to incorrectly inline an initializer into the first usage. This bug has now been fixed:

    // Original code
function foo() {
  let x
  bar(x ||= {})
}

// Old output (with --minify-syntax --target=es6)
function foo() {
  bar(void 0 || (x = {}));
}

// New output (with --minify-syntax --target=es6)
function foo() {
  let x;
  bar(x || (x = {}));
}

  • Fix a potential deadlock when the JavaScript API is used incorrectly (#​4503, #​4506)

    The JavaScript API runs the native esbuild executable as a long-lived child process and communicates with it over stdin/stdout/stderr. Each API request is asynchronous and the executable stays open as long as it has work to do, which is as long as either stdin is still open (meaning there may be more API requests) or there are currently requests being processed.

    Previously esbuild's tracking of outstanding API requests missed decrementing a reference count in an edge case where esbuild's JavaScript API was used incorrectly and the API request returned an error. This could in some cases cause esbuild's native executable to exit with an error message about a deadlock. This release fixes the reference counting bug.

    This fix was submitted by @​ZuBB.

  • Handle target collisions (#​4509)

    It's possible to specify the same target engine multiple times, such as with --target=chrome1,chrome99. This edge case wasn't anticipated and previously took the last version for the duplicated target engine instead of the minimum version (so chrome99 in this case instead of chrome1). With this release, esbuild will now pick the minimum version between all duplicated target engines.

  • Force .mp3 files to use the audio/mpeg MIME type (#​4485)

    MIME type detection for esbuild's data URLs uses Go's built-in MIME type detection, which is based on the MIME sniffing standard. This works correctly for MP3 files that start with the byte sequence ID3, which is commonly the case. However, it's possible to construct valid MP3 files that do not start with ID3, and that perhaps Go's built-in MIME type detection doesn't implement the "Signature for MP3 without ID3" part of the algorithm. This results in some .mp3 files incorrectly using the application/octet-stream MIME type instead of audio/mpeg. With this release, esbuild will now always use the audio/mpeg MIME type for files ending in .mp3.

  • Add a new TypeScript syntax warning

    TypeScript 7 turned some previously-valid TypeScript syntax into a syntax error because it was confusing. TypeScript 6 accepts 1 + 2 as number * 3 as valid syntax but confusingly converts it to (1 + 2) * 3 instead of the more intuitive conversion to 1 + (2 * 3). This syntax is now an error in TypeScript 7+. With this release, esbuild will now warn about the use of this syntax:

    ▲ [WARNING] Operator "*" should not directly follow a TypeScript type cast after the "+" operator [confusing-typescript-cast]

    example.ts:1:28:
      1 │ console.log(1 + 2 as number * 3)
        ╵                             ^

  This is a syntax error in newer versions of TypeScript because the type cast has unintuitive
  precedence in this case. Surround the inner expression in parentheses to silence this warning:

    example.ts:1:12:
      1 │ console.log(1 + 2 as number * 3)
        │             ~~~~~~~~~~~~~~~
        ╵             (             )

    See microsoft/TypeScript#63527 for more information.

  • Add support for formatting errors for Visual Studio (#​4460)

    Visual Studio has a specific style that it expects log messages to be in for them to show up in the UI when esbuild is run as a custom build step. The current log style that esbuild uses doesn't conform to this specific style.

    With this release, esbuild has a new log style for Visual Studio (and other tools in the MSBuild ecosystem) that can be enabled with --log-style=visualstudio. Here is an example log message in this style:

    $ esbuild example.ts --log-style=visualstudio
/Users/evan/dev/esbuild/example.ts(1,29): warning ES0010: Operator "*" should not directly follow a TypeScript type cast after the "+" operator

    This log style is also available via the JS and Go APIs, and can now be used with the existing formatMessages API.

  • Fix a bug with CSS gamut mapping (#​4488)

    Due to a typo, the fallback colors generated for CSS colors outside of the sRGB gamut weren't correct. This release fixes the generated colors to use the intended algorithm.

    This fix was submitted by @​chatman-media.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • 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.

@aem-code-sync

aem-code-sync Bot commented Jun 13, 2026 •
edited
Loading

Copy link
Copy Markdown

Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch and validate page speed.
In case there are problems, just click a checkbox below to rerun the respective action.

  • Re-run all PSI checks
  • Re-run failed PSI checks
  • Re-sync branch
Commits

@renovate renovate Bot changed the title chore(deps): update dependency esbuild to v0.28.1 fix(deps): update dependency @adobe/spectrum-wc to v2.0.0-snapshot-test.20260728023631 Aug 7, 2026
@renovate renovate Bot changed the title fix(deps): update dependency @adobe/spectrum-wc to v2.0.0-snapshot-test.20260728023631 fix(deps): update dependency @adobe/spectrum-wc Aug 8, 2026
@renovate renovate Bot changed the title fix(deps): update dependency @adobe/spectrum-wc Update dependency @adobe/spectrum-wc Aug 13, 2026
@renovate
renovate Bot force-pushed the renovate branch 2 times, most recently from 425f313 to a19ccb3 Compare August 18, 2026 19:26
@renovate renovate Bot changed the title Update dependency @adobe/spectrum-wc fix(deps): update dependency @adobe/spectrum-wc Aug 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants