ci(changesets): version packages #7079
Merged
Conversation
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
✅ Deploy Preview for refine-doc-live-previews ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
refine
|
||||||||||||||||||||||||||||
| Project |
refine
|
| Branch Review |
changeset-release/main
|
| Run status |
|
| Run duration | 23m 00s |
| Commit |
|
| Committer | Refine Community Bot |
| View all properties for this run ↗︎ | |
| Test results | |
|---|---|
Failures
|
0
|
Flaky
|
0
|
Pending
|
22
|
Skipped
|
0
|
Passing
|
378
|
| View all changes introduced in this branch ↗︎ | |
BatuhanW
approved these changes
Oct 15, 2025
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
@refinedev/[email protected]
Patch Changes
#7078
5518bee265a48abf3dbb3befc7028a53643847daThanks @erenkurnaz! - feat: addedfallbackToprop toNavigateToResourcecomponent [FEAT] Support custom fallback path in<NavigateToResource />#7077Now with
fallbackToprop, you can specify a fallback route when no resource is found to navigate to. The component will navigate to the provided fallback path instead of doing nothing, providing better user experience.Resolves [FEAT] Support custom fallback path in
<NavigateToResource />#7077@refinedev/[email protected]
Patch Changes
#7078
5518bee265a48abf3dbb3befc7028a53643847daThanks @erenkurnaz! - feat: addedfallbackToprop toNavigateToResourcecomponent [FEAT] Support custom fallback path in<NavigateToResource />#7077Now with
fallbackToprop, you can specify a fallback route when no resource is found to navigate to. The component will navigate to the provided fallback path instead of doing nothing, providing better user experience.Resolves [FEAT] Support custom fallback path in
<NavigateToResource />#7077@refinedev/[email protected]
Patch Changes
#7078
5518bee265a48abf3dbb3befc7028a53643847daThanks @erenkurnaz! - feat: addedfallbackToprop toNavigateToResourcecomponent [FEAT] Support custom fallback path in<NavigateToResource />#7077Now with
fallbackToprop, you can specify a fallback route when no resource is found to navigate to. The component will navigate to the provided fallback path instead of doing nothing, providing better user experience.Resolves [FEAT] Support custom fallback path in
<NavigateToResource />#7077