ci(changesets): version packages#7326
Merged
Merged
Conversation
refine
|
||||||||||||||||||||||||||||
| Project |
refine
|
| Branch Review |
changeset-release/main
|
| Run status |
|
| Run duration | 22m 48s |
| Commit |
|
| Committer | Refine Community Bot |
| View all properties for this run ↗︎ | |
| Test results | |
|---|---|
Failures
|
0
|
Flaky
|
0
|
Pending
|
22
|
Skipped
|
0
|
Passing
|
368
|
| View all changes introduced in this branch ↗︎ | |
refine-bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
611d868 to
bab79b8
Compare
refine-bot
force-pushed
the
changeset-release/main
branch
from
bab79b8 to
002065c
Compare
BatuhanW
approved these changes
Mar 5, 2026
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
2 participants
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
@refinedev/core@5.0.10
Patch Changes
#7245
bf3cc65f73a6801a5fd1e42e6162efd2e89406d3Thanks @harsha-cpp! - fix: correctly parse deeply nested conditional filters from URL with syncWithLocationIncreased
qs.parsedepth from default 5 to 10 to support deeply nested conditional filters (e.g.,or -> and -> {field, operator, value}). Previously, nested filter properties were incorrectly parsed as bracket notation keys ([field],[operator],[value]) after page reload when usingsyncWithLocation: true.@refinedev/mui@8.0.1
Patch Changes
91f0eac72e58fd220add066c12329d39bb38a326Thanks @kaigritun! - fix(mui): prevent nested interactive elements in navigation buttons@refinedev/nextjs-router@7.0.5
Patch Changes
#7245
bf3cc65f73a6801a5fd1e42e6162efd2e89406d3Thanks @harsha-cpp! - fix: correctly parse deeply nested conditional filters from URL with syncWithLocationIncreased
qs.parsedepth from default 5 to 10 to support deeply nested conditional filters (e.g.,or -> and -> {field, operator, value}). Previously, nested filter properties were incorrectly parsed as bracket notation keys ([field],[operator],[value]) after page reload when usingsyncWithLocation: true.@refinedev/react-router@2.0.4
Patch Changes
#7245
bf3cc65f73a6801a5fd1e42e6162efd2e89406d3Thanks @harsha-cpp! - fix: correctly parse deeply nested conditional filters from URL with syncWithLocationIncreased
qs.parsedepth from default 5 to 10 to support deeply nested conditional filters (e.g.,or -> and -> {field, operator, value}). Previously, nested filter properties were incorrectly parsed as bracket notation keys ([field],[operator],[value]) after page reload when usingsyncWithLocation: true.@refinedev/remix-router@4.0.4
Patch Changes
#7245
bf3cc65f73a6801a5fd1e42e6162efd2e89406d3Thanks @harsha-cpp! - fix: correctly parse deeply nested conditional filters from URL with syncWithLocationIncreased
qs.parsedepth from default 5 to 10 to support deeply nested conditional filters (e.g.,or -> and -> {field, operator, value}). Previously, nested filter properties were incorrectly parsed as bracket notation keys ([field],[operator],[value]) after page reload when usingsyncWithLocation: true.