Version Packages (next)#998
Merged
Merged
Conversation
Deploying solid-primitives with
|
| Latest commit: |
95e5844
|
| Status: | 🚫 Build failed. |
github-actions
Bot
force-pushed
the
changeset-release/next
branch
from
July 22, 2026 01:32
c9d735e to
99638a5
Compare
github-actions
Bot
force-pushed
the
changeset-release/next
branch
from
July 22, 2026 01:41
99638a5 to
95e5844
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
1 participant
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 next, this PR will be updated.
nextis currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonnext.Releases
@solid-primitives/scroll@3.0.0-next.3
Patch Changes
createPreventScrollnow locks scroll ondocument.documentElementinstead of<body>. Locking<body>could breakposition: stickyelements, since sticky positioning is computed relative to the nearest scrolling ancestor — when that ancestor was<body>instead of the viewport, sticky children would unstick while scroll was prevented. Scrollbar-width, padding/margin compensation, and scroll-position restoration are all computed againstdocumentElementnow as well.@solid-primitives/storage@5.0.0-next.3
Patch Changes
messageSyncandwsSync: theirurlparameter's default value (globalThis.location?.href) lacked an explicit type annotation, which--isolatedDeclarations(used by the package's.d.tsgeneration) requires on any parameter whose type can't be trivially inferred. No behavior or API changes —urlis stillstring | undefined.