Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
0fa109a to
6572a58
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
6572a58 to
f68e242
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
f68e242 to
226ed30
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
226ed30 to
19e45b5
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
19e45b5 to
c431f50
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@pandacss/astro-plugin-studio@1.9.1
Patch Changes
@pandacss/dev@1.9.1
Patch Changes
@pandacss/config@1.9.1
Patch Changes
@pandacss/core@1.9.1
Patch Changes
8fda1a5: Fix pseudo-element conditions (::before, ::after) being placed before pseudo-class selectors in generated CSS
When a pseudo-element condition like
_beforewas combined with a mixed condition like_hover(defined as an arraywith a media query + selector), the pseudo-element would incorrectly appear before the pseudo-class in the generated
CSS selector.
Before (broken):
.class::before:is(:hover, ...)- invalid CSS After (fixed):.class:is(:hover, ...)::before- valid CSSThe fix ensures pseudo-element selectors are always sorted last in the condition chain, matching the CSS specification
requirement that pseudo-elements must appear at the end of a selector.
Updated dependencies [d02fcf6]
@pandacss/extractor@1.9.1
Patch Changes
@pandacss/generator@1.9.1
Patch Changes
@pandacss/logger@1.9.1
Patch Changes
@pandacss/mcp@1.9.1
Patch Changes
@pandacss/node@1.9.1
Patch Changes
@pandacss/parser@1.9.1
Patch Changes
@pandacss/postcss@1.9.1
Patch Changes
@pandacss/preset-atlaskit@1.9.1
Patch Changes
@pandacss/preset-base@1.9.1
Patch Changes
028e755: Fix
Spacerpattern not resolving spacing tokens for thesizeprop.Previously,
<Spacer size="5" />would generate invalid CSS (flex: 0 0 5) instead of resolving the spacing token.Now it correctly outputs
flex: 0 0 var(--spacing-5, 5).Before (broken):
flex: 0 0 5— raw value, not a valid CSS length After (fixed):flex: 0 0 var(--spacing-5, 5)— resolved spacing tokenCloses Spacer pattern does not apply spacing tokens to
sizeprop #3490@pandacss/preset-open-props@1.9.1
Patch Changes
@pandacss/preset-panda@1.9.1
Patch Changes
@pandacss/reporter@1.9.1
Patch Changes
@pandacss/studio@1.9.1
Patch Changes
@pandacss/token-dictionary@1.9.1
Patch Changes
d02fcf6: Fix duplicate token references with special characters resolving incorrectly in composite values
When the same token reference containing special characters (e.g.
{sizes.0.5}) appeared more than once in acomposite value, only the first occurrence was resolved correctly. The second occurrence produced a malformed CSS
variable name.
This was caused by
String.replace()only replacing the first match. Changed toString.replaceAll()inToken.expandReferences()andexpandReferences()utility.Before (broken):
--shadows-control-accent: 0 var(--sizes-0\.5) var(--sizes-0-5) rgba(92, 225, 113, 0.25)After (fixed):
--shadows-control-accent: 0 var(--sizes-0\.5) var(--sizes-0\.5) rgba(92, 225, 113, 0.25)@pandacss/is-valid-prop@1.9.1
@pandacss/shared@1.9.1
@pandacss/types@1.9.1