Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix(deps): update panda-css monorepo to ^0.39.0 - autoclosed #59

Closed
wants to merge 1 commit into from
Closed

fix(deps): update panda-css monorepo to ^0.39.0 - autoclosed #59

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 3, 2024 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@pandacss/config (source) ^0.27.1 -> ^0.39.0 age adoption passing confidence
@pandacss/dev (source) ^0.27.1 -> ^0.39.0 age adoption passing confidence

Release Notes

chakra-ui/panda (@​pandacss/config)

v0.39.0

Compare Source

Patch Changes

v0.38.0

Compare Source

Patch Changes

v0.37.2

Compare Source

Patch Changes

v0.37.1

Compare Source

Patch Changes

v0.37.0

Compare Source

Patch Changes

v0.36.1

Compare Source

Patch Changes

v0.36.0

Compare Source

Minor Changes

  • 2691f16: Add config.themes to easily define and apply a theme on multiple tokens at once, using data attributes and
    CSS variables.

    Can pre-generate multiple themes with token overrides as static CSS, but also dynamically import and inject a theme
    stylesheet at runtime (browser or server).

    Example:

    // panda.config.ts
import { defineConfig } from '@​pandacss/dev'

export default defineConfig({
  // ...
  // main theme
  theme: {
    extend: {
      tokens: {
        colors: {
          text: { value: 'blue' },
        },
      },
      semanticTokens: {
        colors: {
          body: {
            value: {
              base: '{colors.blue.600}',
              _osDark: '{colors.blue.400}',
            },
          },
        },
      },
    },
  },
  // alternative theme variants
  themes: {
    primary: {
      tokens: {
        colors: {
          text: { value: 'red' },
        },
      },
      semanticTokens: {
        colors: {
          muted: { value: '{colors.red.200}' },
          body: {
            value: {
              base: '{colors.red.600}',
              _osDark: '{colors.red.400}',
            },
          },
        },
      },
    },
    secondary: {
      tokens: {
        colors: {
          text: { value: 'blue' },
        },
      },
      semanticTokens: {
        colors: {
          muted: { value: '{colors.blue.200}' },
          body: {
            value: {
              base: '{colors.blue.600}',
              _osDark: '{colors.blue.400}',
            },
          },
        },
      },
    },
  },
})
Pregenerating themes

By default, no additional theme variant is generated, you need to specify the specific themes you want to generate in
staticCss.themes to include them in the CSS output.

// panda.config.ts
import { defineConfig } from '@​pandacss/dev'

export default defineConfig({
  // ...
  staticCss: {
    themes: ['primary', 'secondary'],
  },
})

This will generate the following CSS:

@​layer tokens {
  :where(:root, :host) {
    --colors-text: blue;
    --colors-body: var(--colors-blue-600);
  }

  [data-panda-theme='primary'] {
    --colors-text: red;
    --colors-muted: var(--colors-red-200);
    --colors-body: var(--colors-red-600);
  }

  @​media (prefers-color-scheme: dark) {
    :where(:root, :host) {
      --colors-body: var(--colors-blue-400);
    }

    [data-panda-theme='primary'] {
      --colors-body: var(--colors-red-400);
    }
  }
}

An alternative way of applying a theme is by using the new styled-system/themes entrypoint where you can import the
themes CSS variables and use them in your app.

ℹ️ The styled-system/themes will always contain every themes (tree-shaken if not used), staticCss.themes only
applies to the CSS output.

Each theme has a corresponding JSON file with a similar structure:

{
  "name": "primary",
  "id": "panda-themes-primary",
  "dataAttr": "primary",
  "css": "[data-panda-theme=primary] { ... }"
}

ℹ️ Note that for semantic tokens, you need to use inject the theme styles, see below

Dynamically import a theme using its name:

import { getTheme } from '../styled-system/themes'

const theme = await getTheme('red')
//    ^? {
//     name: "red";
//     id: string;
//     css: string;
// }

Inject the theme styles into the DOM:

import { injectTheme } from '../styled-system/themes'

const theme = await getTheme('red')
injectTheme(document.documentElement, theme) // this returns the injected style element

SSR example with NextJS:

// app/layout.tsx
import { Inter } from 'next/font/google'
import { cookies } from 'next/headers'
import { ThemeName, getTheme } from '../../styled-system/themes'

export default async function RootLayout({ children }: { children: React.ReactNode }) {
  const store = cookies()
  const themeName = store.get('theme')?.value as ThemeName
  const theme = themeName && (await getTheme(themeName))

  return (
    <html lang="en" data-panda-theme={themeName ? themeName : undefined}>
      {themeName && (
        <head>
          <style type="text/css" id={theme.id} dangerouslySetInnerHTML={{ __html: theme.css }} />
        </head>
      )}
      <body>{children}</body>
    </html>
  )
}

// app/page.tsx
import { getTheme, injectTheme } from '../../styled-system/themes'

export default function Home() {
  return (
    <>
      <button
        onClick={async () => {
          const current = document.documentElement.dataset.pandaTheme
          const next = current === 'primary' ? 'secondary' : 'primary'
          const theme = await getTheme(next)
          setCookie('theme', next, 7)
          injectTheme(document.documentElement, theme)
        }}
      >
        swap theme
      </button>
    </>
  )
}

// Set a Cookie
function setCookie(cName: string, cValue: any, expDays: number) {
  let date = new Date()
  date.setTime(date.getTime() + expDays * 24 * 60 * 60 * 1000)
  const expires = 'expires=' + date.toUTCString()
  document.cookie = cName + '=' + cValue + '; ' + expires + '; path=/'
}

Finally, you can create a theme contract to ensure that all themes have the same structure:

import { defineThemeContract } from '@&#8203;pandacss/dev'

const defineTheme = defineThemeContract({
  tokens: {
    colors: {
      red: { value: '' }, // theme implementations must have a red color
    },
  },
})

defineTheme({
  selector: '.theme-secondary',
  tokens: {
    colors: {
      // ^^^^   Property 'red' is missing in type '{}' but required in type '{ red: { value: string; }; }'
      //
      // fixed with
      // red: { value: 'red' },
    },
  },
})
Patch Changes

  • 445c7b6: Fix merging issue when using a preset that has a token with a conflicting value with another (or the user's
    config)

    import { defineConfig } from '@&#8203;pandacss/dev'

const userConfig = defineConfig({
  presets: [
    {
      theme: {
        extend: {
          tokens: {
            colors: {
              black: { value: 'black' },
            },
          },
        },
      },
    },
  ],
  theme: {
    tokens: {
      extend: {
        colors: {
          black: {
            0: { value: 'black' },
            10: { value: 'black/10' },
            20: { value: 'black/20' },
            30: { value: 'black/30' },
          },
        },
      },
    },
  },
})

    When merged with the preset, the config would create nested tokens (black.10, black.20, black.30) inside of the
    initially flat black token.

    This would cause issues as the token engine stops diving deeper after encountering an object with a value property.

    To fix this, we now automatically replace the flat black token using the DEFAULT keyword when resolving the config
    so that the token engine can continue to dive deeper into the object:

    {
  "theme": {
    "tokens": {
      "colors": {
        "black": {
          "0": {
            "value": "black",
          },
          "10": {
            "value": "black/10",
          },
          "20": {
            "value": "black/20",
          },
          "30": {
            "value": "black/30",
          },
-          "value": "black",
+          "DEFAULT": {
+            "value": "black",
+          },
        },
      },
    },
  },
}

  • 861a280: Introduce a new globalVars config option to define type-safe
    CSS variables and custom
    CSS @​property.

    Example:

    import { defineConfig } from '@&#8203;pandacss/dev'

export default defineConfig({
  // ...
  globalVars: {
    '--some-color': 'red',
    '--button-color': {
      syntax: '<color>',
      inherits: false,
      initialValue: 'blue',
    },
  },
})

    Note: Keys defined in globalVars will be available as a value for every utilities, as they're not bound to token
    categories.

    import { css } from '../styled-system/css'

const className = css({
  '--button-color': 'colors.red.300',
  // ^^^^^^^^^^^^  will be suggested

  backgroundColor: 'var(--button-color)',
  //                ^^^^^^^^^^^^^^^^^^  will be suggested
})

  • Updated dependencies [861a280]

  • Updated dependencies [2691f16]

  • Updated dependencies [340f4f1]

  • Updated dependencies [fabdabe]

v0.35.0

Compare Source

Patch Changes

v0.34.3

Compare Source

Patch Changes

v0.34.2

Compare Source

Patch Changes

  • 58388de: Fix a false positive with the validation check that reported Missing token when using a color opacity
    modifier in config tokens or semanticTokens

    import { defineConfig } from '@&#8203;pandacss/dev'

export default defineConfig({
  validation: 'warn',
  conditions: {
    light: '.light &',
    dark: '.dark &',
  },
  theme: {
    tokens: {
      colors: {
        blue: { 500: { value: 'blue' } },
        green: { 500: { value: 'green' } },
      },
      opacity: {
        half: { value: 0.5 },
      },
    },
    semanticTokens: {
      colors: {
        secondary: {
          value: {
            base: 'red',
            _light: '{colors.blue.500/32}',
            _dark: '{colors.green.500/half}',
          },
        },
      },
    },
  },
})

    Would incorrectly report:

v0.34.1

Compare Source

Patch Changes

v0.34.0

Compare Source

Patch Changes

  • 1c63216: Add a config validation check to prevent using spaces in token keys, show better error logs when there's a
    CSS parsing error

  • 9f04427: Fix "missing token" warning when using DEFAULT in tokens path

    import { defineConfig } from '@&#8203;pandacss/dev'

export default defineConfig({
  validation: 'error',
  theme: {
    semanticTokens: {
      colors: {
        primary: {
          DEFAULT: { value: '#ff3333' },
          lighter: { value: '#ff6666' },
        },
        background: { value: '{colors.primary}' }, // <-- ⚠️ wrong warning
        background2: { value: '{colors.primary.lighter}' }, // <-- no warning, correct
      },
    },
  },
})

    Add a warning when using value twice

    import { defineConfig } from '@&#8203;pandacss/dev'

export default defineConfig({
  validation: 'error',
  theme: {
    tokens: {
      colors: {
        primary: { value: '#ff3333' },
      },
    },
    semanticTokens: {
      colors: {
        primary: {
          value: { value: '{colors.primary}' }, // <-- ⚠️ new warning for this
        },
      },
    },
  },
})

  • Updated dependencies [d1516c8]

v0.33.0

Compare Source

Patch Changes

v0.32.1

Compare Source

Patch Changes

v0.32.0

Compare Source

Minor Changes

  • de4d9ef: Allow config.hooks to be shared in plugins

    For hooks that can transform Panda's internal state by returning something (like cssgen:done and codegen:prepare),
    each hook instance will be called sequentially and the return result (if any) of the previous hook call is passed to
    the next hook so that they can be chained together.

Patch Changes

v0.31.0

Compare Source

Minor Changes

  • f029624: - Sort the longhand/shorthand atomic rules in a deterministic order to prevent property conflicts

    • Automatically merge the base object in the css root styles in the runtime
    • This may be a breaking change depending on how your styles are created

    Ex:

    css({
  padding: '1px',
  paddingTop: '3px',
  paddingBottom: '4px',
})

    Will now always generate the following css:

    @&#8203;layer utilities {
  .p_1px {
    padding: 1px;
  }

  .pt_3px {
    padding-top: 3px;
  }

  .pb_4px {
    padding-bottom: 4px;
  }
}
Patch Changes

v0.30.2

Compare Source

Patch Changes

v0.30.1

Compare Source

Patch Changes

v0.30.0

Compare Source

Minor Changes
  • 0dd45b6: Fix issue where config changes could not be detected due to config bundling returning stale result
    sometimes.
Patch Changes

  • 74485ef: Add utils functions in the config:resolved hook, making it easy to apply transformations after all
    presets have been merged.

    For example, this could be used if you want to use most of a preset but want to completely omit a few things, while
    keeping the rest. Let's say we want to remove the stack pattern from the built-in @pandacss/preset-base:

    import { defineConfig } from '@&#8203;pandacss/dev'

export default defineConfig({
  // ...
  hooks: {
    'config:resolved': ({ config, utils }) => {
      return utils.omit(config, ['patterns.stack'])
    },
  },
})

  • ab32d1d: Fix issue where errors were thrown when semantic tokens are overriden in tokens.

  • d5977c2: - Add a --logfile flag to the panda, panda codegen, panda cssgen and panda debug commands.

    • Add a logfile option to the postcss plugin

    Logs will be streamed to the file specified by the --logfile flag or the logfile option. This is useful for
    debugging issues that occur during the build process.

    panda --logfile ./logs/panda.log
    module.exports = {
  plugins: {
    '@&#8203;pandacss/dev/postcss': {
      logfile: './logs/panda.log',
    },
  },
}

  • Updated dependencies [74485ef]

  • Updated dependencies [ab32d1d]

  • Updated dependencies [49c760c]

  • Updated dependencies [d5977c2]

v0.29.1

Compare Source

Patch Changes

v0.29.0

Compare Source

Minor Changes

  • a2fb5cc: - Add support for explicitly specifying config related files that should trigger a context reload on change.

    We automatically track the config file and (transitive) files imported by the config file as much as possible, but
    sometimes we might miss some. You can use this option as a workaround for those edge cases.

    Set the dependencies option in panda.config.ts to a glob or list of files.

    export default defineConfig({
  // ...
  dependencies: ['path/to/files/**.ts'],
})

    • Invoke config:change hook in more situations (when the --watch flag is passed to panda codegen,
      panda cssgen, panda ship)

    • Watch for more config options paths changes, so that the related artifacts will be regenerated a bit more reliably
      (ex: updating the config.hooks will now trigger a full regeneration of styled-system)

Patch Changes

v0.28.0

Compare Source

Minor Changes

  • f58f6df: Refactor config.hooks to be much more powerful, you can now:

    • Tweak the config after it has been resolved (after presets are loaded and merged), this could be used to dynamically
      load all recipes from a folder
    • Transform a source file's content before parsing it, this could be used to transform the file content to a
      tsx-friendly syntax so that Panda's parser can parse it.
    • Implement your own parser logic and add the extracted results to the classic Panda pipeline, this could be used to
      parse style usage from any template language
    • Tweak the CSS content for any @layer or even right before it's written to disk (if using the CLI) or injected
      through the postcss plugin, allowing all kinds of customizations like removing the unused CSS variables, etc.
    • React to any config change or after the codegen step (your outdir, the styled-system folder) have been generated

    See the list of available config.hooks here:

    export interface PandaHooks {
  /**
   * Called when the config is resolved, after all the presets are loaded and merged.
   * This is the first hook called, you can use it to tweak the config before the context is created.
   */
  'config:resolved': (args: { conf: LoadConfigResult }) => MaybeAsyncReturn
  /**
   * Called when the Panda context has been created and the API is ready to be used.
   */
  'context:created': (args: { ctx: ApiInterface; logger: LoggerInterface }) => void
  /**
   * Called when the config file or one of its dependencies (imports) has changed.
   */
  'config:change': (args: { config: UserConfig }) => MaybeAsyncReturn
  /**
   * Called after reading the file content but before parsing it.
   * You can use this hook to transform the file content to a tsx-friendly syntax so that Panda's parser can parse it.
   * You can also use this hook to parse the file's content on your side using a custom parser, in this case you don't have to return anything.
   */
  'parser:before': (args: { filePath: string; content: string }) => string | void
  /**
   * Called after the file styles are extracted and processed into the resulting ParserResult object.
   * You can also use this hook to add your own extraction results from your custom parser to the ParserResult object.
   */
  'parser:after': (args: { filePath: string; result: ParserResultInterface | undefined }) => void
  /**
   * Called after the codegen is completed
   */
  'codegen:done': () => MaybeAsyncReturn
  /**
   * Called right before adding the design-system CSS (global, static, preflight, tokens, keyframes) to the final CSS
   * Called right before writing/injecting the final CSS (styles.css) that contains the design-system CSS and the parser CSS
   * You can use it to tweak the CSS content before it's written to disk or injected through the postcss plugin.
   */
  'cssgen:done': (args: {
    artifact: 'global' | 'static' | 'reset' | 'tokens' | 'keyframes' | 'styles.css'
    content: string
  }) => string | void
}
Patch Changes

v0.27.3

Compare Source

Patch Changes

v0.27.2

Compare Source

Patch Changes
chakra-ui/panda (@​pandacss/dev)

v0.39.0

Compare Source

Patch Changes

v0.38.0

Compare Source

Patch Changes

v0.37.2

Compare Source

Patch Changes

v0.37.1

Compare Source

Patch Changes

v0.37.0

Compare Source

Patch Changes

v0.36.1

Compare Source

Patch Changes

v0.36.0

Compare Source

Minor Changes

  • 2691f16: Add config.themes to easily define and apply a theme on multiple tokens at once, using data attributes and
    CSS variables.

    Can pre-generate multiple themes with token overrides as static CSS, but also dynamically import and inject a theme
    stylesheet at runtime (browser or server).

    Example:

    // panda.config.ts
import { defineConfig } from '@&#8203;pandacss/dev'

export default defineConfig({
  // ...
  // main theme
  theme: {
    extend: {
      tokens: {
        colors: {
          text: { value: 'blue' },
        },
      },
      semanticTokens: {
        colors: {
          body: {
            value: {
              base: '{colors.blue.600}',
              _osDark: '{colors.blue.400}',
            },
          },
        },
      },
    },
  },
  // alternative theme variants
  themes: {
    primary: {
      tokens: {
        colors: {
          text: { value: 'red' },
        },
      },
      semanticTokens: {
        colors: {
          muted: { value: '{colors.red.200}' },
          body: {
            value: {
              base: '{colors.red.600}',
              _osDark: '{colors.red.400}',
            },
          },
        },
      },
    },
    secondary: {
      tokens: {
        colors: {
          text: { value: 'blue' },
        },
      },
      semanticTokens: {
        colors: {
          muted: { value: '{colors.blue.200}' },
          body: {
            value: {
              base: '{colors.blue.600}',
              _osDark: '{colors.blue.400}',
            },
          },
        },
      },
    },
  },
})
Pregenerating themes

By default, no additional theme variant is generated, you need to specify the specific themes you want to generate in
staticCss.themes to include them in the CSS output.

// panda.config.ts
import { defineConfig } from '@&#8203;pandacss/dev'

export default defineConfig({
  // ...
  staticCss: {
    themes: ['primary', 'secondary'],
  },
})

This will generate the following CSS:

@&#8203;lay

</details>

---

### Configuration

📅 **Schedule**: 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.

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

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/sonofmagic/weapp-pandacss).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy4xMDMuMSIsInVwZGF0ZWRJblZlciI6IjM3LjMzMS4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiJ9-->

@changeset-bot changeset-bot
Copy link

changeset-bot bot commented Jan 3, 2024 •
edited
Loading

⚠️ No Changeset found

Latest commit: fc6e267

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@renovate renovate bot force-pushed the renovate/panda-css-monorepo branch from ecb7a28 to d3d6e45 Compare January 7, 2024 05:23
@renovate renovate bot changed the title fix(deps): update panda-css monorepo to ^0.24.0 fix(deps): update panda-css monorepo to ^0.25.0 Jan 7, 2024
@renovate renovate bot force-pushed the renovate/panda-css-monorepo branch from d3d6e45 to 9908d25 Compare January 10, 2024 20:34
@renovate renovate bot changed the title fix(deps): update panda-css monorepo to ^0.25.0 fix(deps): update panda-css monorepo to ^0.26.0 Jan 10, 2024
@renovate renovate bot force-pushed the renovate/panda-css-monorepo branch from 9908d25 to e5ebbb1 Compare January 16, 2024 02:44
@renovate renovate bot changed the title fix(deps): update panda-css monorepo to ^0.26.0 fix(deps): update panda-css monorepo to ^0.27.0 Jan 16, 2024
@renovate renovate bot changed the title fix(deps): update panda-css monorepo to ^0.27.0 fix(deps): update panda-css monorepo to v0.27.2 Jan 17, 2024
@renovate renovate bot changed the title fix(deps): update panda-css monorepo to v0.27.2 fix(deps): update panda-css monorepo to v0.27.3 Jan 19, 2024
@renovate renovate bot force-pushed the renovate/panda-css-monorepo branch from e5ebbb1 to b6d84ea Compare January 24, 2024 17:48
@renovate renovate bot changed the title fix(deps): update panda-css monorepo to v0.27.3 fix(deps): update panda-css monorepo Jan 24, 2024
@renovate renovate bot force-pushed the renovate/panda-css-monorepo branch from b6d84ea to ad78204 Compare January 25, 2024 05:37
@renovate renovate bot changed the title fix(deps): update panda-css monorepo fix(deps): update panda-css monorepo to ^0.28.0 Jan 25, 2024
@codecov Codecov
Copy link

codecov bot commented Jan 25, 2024 •
edited
Loading

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.57%. Comparing base (b26d150) to head (e1356b0).

❗ Current head e1356b0 differs from pull request most recent head fc6e267. Consider uploading reports for the commit fc6e267 to get more accurate results

Additional details and impacted files 
@@           Coverage Diff           @@
##             main      #59   +/-   ##
=======================================
  Coverage   93.57%   93.57%           
=======================================
  Files          15       15           
  Lines         716      716           
  Branches       81       81           
=======================================
  Hits          670      670           
  Misses         45       45           
  Partials        1        1

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@renovate renovate bot force-pushed the renovate/panda-css-monorepo branch from ad78204 to 404e18a Compare January 30, 2024 08:57
@renovate renovate bot changed the title fix(deps): update panda-css monorepo to ^0.28.0 fix(deps): update panda-css monorepo to ^0.29.0 Jan 30, 2024
@renovate renovate bot force-pushed the renovate/panda-css-monorepo branch from 404e18a to 3bffaf3 Compare February 6, 2024 05:03
@renovate renovate bot changed the title fix(deps): update panda-css monorepo to ^0.29.0 fix(deps): update panda-css monorepo to ^0.30.0 Feb 6, 2024
@renovate renovate bot force-pushed the renovate/panda-css-monorepo branch from 3bffaf3 to fea22c0 Compare February 14, 2024 06:02
@renovate renovate bot changed the title fix(deps): update panda-css monorepo to ^0.30.0 fix(deps): update panda-css monorepo to ^0.31.0 Feb 14, 2024
@renovate renovate bot force-pushed the renovate/panda-css-monorepo branch from fea22c0 to 5fcfc81 Compare February 21, 2024 08:08
@renovate renovate bot changed the title fix(deps): update panda-css monorepo to ^0.31.0 fix(deps): update panda-css monorepo to ^0.32.0 Feb 21, 2024
@renovate renovate bot force-pushed the renovate/panda-css-monorepo branch from 5fcfc81 to efba8df Compare February 28, 2024 05:49
@renovate renovate bot changed the title fix(deps): update panda-css monorepo to ^0.32.0 fix(deps): update panda-css monorepo to ^0.33.0 Feb 28, 2024
@renovate renovate bot force-pushed the renovate/panda-css-monorepo branch from efba8df to af0092b Compare March 7, 2024 02:45
@renovate renovate bot changed the title fix(deps): update panda-css monorepo to ^0.33.0 fix(deps): update panda-css monorepo to ^0.34.0 Mar 7, 2024
@renovate renovate bot force-pushed the renovate/panda-css-monorepo branch from af0092b to 75caab9 Compare March 15, 2024 17:45
@renovate renovate bot changed the title fix(deps): update panda-css monorepo to ^0.34.0 fix(deps): update panda-css monorepo to ^0.35.0 Mar 15, 2024
@renovate renovate bot force-pushed the renovate/panda-css-monorepo branch from 75caab9 to 906f2cc Compare March 22, 2024 02:34
@renovate renovate bot changed the title fix(deps): update panda-css monorepo to ^0.35.0 fix(deps): update panda-css monorepo to ^0.36.0 Mar 22, 2024
@renovate renovate bot force-pushed the renovate/panda-css-monorepo branch from 906f2cc to e1356b0 Compare April 2, 2024 05:45
@renovate renovate bot changed the title fix(deps): update panda-css monorepo to ^0.36.0 fix(deps): update panda-css monorepo to ^0.37.0 Apr 2, 2024
@renovate renovate bot force-pushed the renovate/panda-css-monorepo branch from e1356b0 to 007a8b9 Compare April 30, 2024 05:39
@renovate renovate bot changed the title fix(deps): update panda-css monorepo to ^0.37.0 fix(deps): update panda-css monorepo to ^0.38.0 Apr 30, 2024
@renovate renovate bot force-pushed the renovate/panda-css-monorepo branch from 007a8b9 to fc6e267 Compare May 4, 2024 20:42
@renovate renovate bot changed the title fix(deps): update panda-css monorepo to ^0.38.0 fix(deps): update panda-css monorepo to ^0.39.0 May 4, 2024
@renovate renovate bot changed the title fix(deps): update panda-css monorepo to ^0.39.0 fix(deps): update panda-css monorepo to ^0.39.0 - autoclosed May 13, 2024
@renovate renovate bot closed this May 13, 2024
@renovate renovate bot deleted the renovate/panda-css-monorepo branch May 13, 2024 15:56
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