-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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.
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
ci(changesets): refine registry version packages #6682
Merged
Merged
Conversation
This file contains 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
refine
|
Project |
refine
|
Branch Review |
changeset-release/next
|
Run status |
|
Run duration | 18m 43s |
Commit |
|
Committer | Refine Community Bot |
View all properties for this run ↗︎ |
Test results | |
---|---|
|
0
|
|
0
|
|
22
|
|
0
|
|
378
|
View all changes introduced in this branch ↗︎ |
c3ee875
to
6308f79
Compare
6308f79
to
123244e
Compare
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 next, this PR will be updated.
Releases
@refinedev/[email protected]
Patch Changes
⚡ Refine Enterprise Release ⚡
#6683
a12a0821e3c573386c2a8eea4ac1582cc46dd26d
Thanks @aliemir! - fix(types): remove path aliases from type importsSince typescript doesn't resolve and replace path aliases, using them for the type imports will cause
d.ts
files to reference unresolvable paths and types.While this doesn't break everything, it breaks the types in places where the path aliases are used for type imports.
This change removes the path aliases from the type imports and replaces them with relative imports.
@refinedev/[email protected]
Patch Changes
⚡ Refine Enterprise Release ⚡
#6683
a12a0821e3c573386c2a8eea4ac1582cc46dd26d
Thanks @aliemir! - fix(types): remove path aliases from type importsSince typescript doesn't resolve and replace path aliases, using them for the type imports will cause
d.ts
files to reference unresolvable paths and types.While this doesn't break everything, it breaks the types in places where the path aliases are used for type imports.
This change removes the path aliases from the type imports and replaces them with relative imports.
@refinedev/[email protected]
Patch Changes
⚡ Refine Enterprise Release ⚡
#6658
91aaf75f04e6e6434196ece9a52b024c70d29df4
Thanks @arndom! - Move invalidation inuseRegister
to be called only on success.Resolves #6639
⚡ Refine Enterprise Release ⚡
#6683
a12a0821e3c573386c2a8eea4ac1582cc46dd26d
Thanks @aliemir! - fix(types): remove path aliases from type importsSince typescript doesn't resolve and replace path aliases, using them for the type imports will cause
d.ts
files to reference unresolvable paths and types.While this doesn't break everything, it breaks the types in places where the path aliases are used for type imports.
This change removes the path aliases from the type imports and replaces them with relative imports.
@refinedev/[email protected]
Patch Changes
a12a0821e3c573386c2a8eea4ac1582cc46dd26d
]:@refinedev/[email protected]
Patch Changes
⚡ Refine Enterprise Release ⚡
#6678
989b438ae2e5441f20844fda42769378985d4284
Thanks @shaun-ak! - fix: issue with custom mutation [BUG] GraphQL dataProvider is missing the params.payload variables merged into the buildVariables. #6665We missed passing param values for custom mutation
Fixes #6665
@refinedev/[email protected]
Patch Changes
⚡ Refine Enterprise Release ⚡
#6683
a12a0821e3c573386c2a8eea4ac1582cc46dd26d
Thanks @aliemir! - fix(types): remove path aliases from type importsSince typescript doesn't resolve and replace path aliases, using them for the type imports will cause
d.ts
files to reference unresolvable paths and types.While this doesn't break everything, it breaks the types in places where the path aliases are used for type imports.
This change removes the path aliases from the type imports and replaces them with relative imports.
@refinedev/[email protected]
Patch Changes
⚡ Refine Enterprise Release ⚡
#6683
a12a0821e3c573386c2a8eea4ac1582cc46dd26d
Thanks @aliemir! - fix(types): remove path aliases from type importsSince typescript doesn't resolve and replace path aliases, using them for the type imports will cause
d.ts
files to reference unresolvable paths and types.While this doesn't break everything, it breaks the types in places where the path aliases are used for type imports.
This change removes the path aliases from the type imports and replaces them with relative imports.