chore(deps): update dependency styled-components to v6.3.7 #666

Merged
renovate merged 1 commit from renovate/styled-components-6.x-lockfile into master 2026-01-16 06:06:33 +01:00
Collaborator

This PR contains the following updates:

Package Type Update Change
styled-components (source) dependencies patch 6.3.66.3.7

Release Notes

styled-components/styled-components (styled-components)

v6.3.7

Compare Source

Patch Changes
  • 51ffa9c: Fix createGlobalStyle compatibility with React StrictMode and RSC

    This fix addresses issues where global styles would disappear or behave incorrectly in React StrictMode and RSC:

    1. Static styles optimization: Static global styles (without props/interpolations) are now only injected once and won't be removed/re-added on every render. This prevents the style flickering that could occur during concurrent rendering.

    2. StrictMode-aware cleanup: Style cleanup now uses queueMicrotask to coordinate with React's effect lifecycle. In StrictMode's simulated unmount/remount cycle, styles are preserved. On real unmount, styles are properly removed.

    3. RSC compatibility: Move useRef inside RSC guard in createGlobalStyle and unify all useContext calls to use consistent !IS_RSC ? pattern.

    4. RSC inline style tag cleanup: Fix bug where server-defined createGlobalStyle rendered in client components would leave behind accumulated SSR-rendered inline <style data-styled-global> tags. The cleanup effect now removes these hoisted style tags when the component unmounts or re-renders with different CSS.

    These changes ensure createGlobalStyle works correctly with:

    • React StrictMode's double-render behavior
    • React 18/19's concurrent rendering features
    • React 19's style hoisting with the precedence attribute
    • React Server Components (server-defined GlobalStyles in client components)
  • 51ffa9c: Restore styled.br.

  • 1f794b7: Add package.json "exports" field for better native ESM integration.


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [styled-components](https://styled-components.com) ([source](https://github.com/styled-components/styled-components)) | dependencies | patch | [`6.3.6` → `6.3.7`](https://renovatebot.com/diffs/npm/styled-components/6.3.6/6.3.7) | --- ### Release Notes <details> <summary>styled-components/styled-components (styled-components)</summary> ### [`v6.3.7`](https://github.com/styled-components/styled-components/releases/tag/styled-components%406.3.7) [Compare Source](https://github.com/styled-components/styled-components/compare/styled-components@6.3.6...styled-components@6.3.7) ##### Patch Changes - [`51ffa9c`](https://github.com/styled-components/styled-components/commit/51ffa9c): Fix createGlobalStyle compatibility with React StrictMode and RSC This fix addresses issues where global styles would disappear or behave incorrectly in React StrictMode and RSC: 1. **Static styles optimization**: Static global styles (without props/interpolations) are now only injected once and won't be removed/re-added on every render. This prevents the style flickering that could occur during concurrent rendering. 2. **StrictMode-aware cleanup**: Style cleanup now uses `queueMicrotask` to coordinate with React's effect lifecycle. In StrictMode's simulated unmount/remount cycle, styles are preserved. On real unmount, styles are properly removed. 3. **RSC compatibility**: Move `useRef` inside RSC guard in `createGlobalStyle` and unify all `useContext` calls to use consistent `!IS_RSC ?` pattern. 4. **RSC inline style tag cleanup**: Fix bug where server-defined `createGlobalStyle` rendered in client components would leave behind accumulated SSR-rendered inline `<style data-styled-global>` tags. The cleanup effect now removes these hoisted style tags when the component unmounts or re-renders with different CSS. These changes ensure `createGlobalStyle` works correctly with: - React StrictMode's double-render behavior - React 18/19's concurrent rendering features - React 19's style hoisting with the `precedence` attribute - React Server Components (server-defined GlobalStyles in client components) - [`51ffa9c`](https://github.com/styled-components/styled-components/commit/51ffa9c): Restore `styled.br`. - [`1f794b7`](https://github.com/styled-components/styled-components/commit/1f794b7): Add package.json "exports" field for better native ESM integration. </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0Mi44Mi4yIiwidXBkYXRlZEluVmVyIjoiNDIuODIuMiIsInRhcmdldEJyYW5jaCI6Im1hc3RlciIsImxhYmVscyI6W119-->
chore(deps): update dependency styled-components to v6.3.7
All checks were successful
ci/woodpecker/push/build Pipeline was successful
ci/woodpecker/push/test Pipeline was successful
ci/woodpecker/push/deploy Pipeline was successful
0f97bfcbcf
renovate scheduled this pull request to auto merge when all checks succeed 2026-01-16 06:04:04 +01:00
renovate merged commit 9250630f33 into master 2026-01-16 06:06:33 +01:00
renovate deleted branch renovate/styled-components-6.x-lockfile 2026-01-16 06:06:33 +01:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
yolokube/dashboard!666
No description provided.