ci(changesets): next version packages

[refine-bot]

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

@pankod/refine-ably@3.26.0

Minor Changes

• #2217 b4aae00f77 Thanks @omeraplak! - All of the refine packages have dependencies on the @pankod/refine-core package. So far we have managed these dependencies with peerDependencies + dependencies but this causes issues like [BUG] Only the most recent version of refine-core does not break app authentication #2183. (having more than one @pankod/refine-core version in node_modules and creating different instances)

  Managing as peerDependencies + devDependencies seems like the best way for now to avoid such issues.

@pankod/refine-airtable@3.26.0

Minor Changes

• #2217 b4aae00f77 Thanks @omeraplak! - All of the refine packages have dependencies on the @pankod/refine-core package. So far we have managed these dependencies with peerDependencies + dependencies but this causes issues like [BUG] Only the most recent version of refine-core does not break app authentication #2183. (having more than one @pankod/refine-core version in node_modules and creating different instances)

  Managing as peerDependencies + devDependencies seems like the best way for now to avoid such issues.

@pankod/refine-altogic@3.26.0

Minor Changes

• #2217 b4aae00f77 Thanks @omeraplak! - All of the refine packages have dependencies on the @pankod/refine-core package. So far we have managed these dependencies with peerDependencies + dependencies but this causes issues like [BUG] Only the most recent version of refine-core does not break app authentication #2183. (having more than one @pankod/refine-core version in node_modules and creating different instances)

  Managing as peerDependencies + devDependencies seems like the best way for now to avoid such issues.

@pankod/refine-antd@3.32.0

Minor Changes

• #2217 b4aae00f77 Thanks @omeraplak! - All of the refine packages have dependencies on the @pankod/refine-core package. So far we have managed these dependencies with peerDependencies + dependencies but this causes issues like [BUG] Only the most recent version of refine-core does not break app authentication #2183. (having more than one @pankod/refine-core version in node_modules and creating different instances)

  Managing as peerDependencies + devDependencies seems like the best way for now to avoid such issues.

@pankod/refine-appwrite@3.26.0

Minor Changes

• #2217 b4aae00f77 Thanks @omeraplak! - All of the refine packages have dependencies on the @pankod/refine-core package. So far we have managed these dependencies with peerDependencies + dependencies but this causes issues like [BUG] Only the most recent version of refine-core does not break app authentication #2183. (having more than one @pankod/refine-core version in node_modules and creating different instances)

  Managing as peerDependencies + devDependencies seems like the best way for now to avoid such issues.

@pankod/refine-cloud@0.3.0

Minor Changes

• #2217 b4aae00f77 Thanks @omeraplak! - All of the refine packages have dependencies on the @pankod/refine-core package. So far we have managed these dependencies with peerDependencies + dependencies but this causes issues like [BUG] Only the most recent version of refine-core does not break app authentication #2183. (having more than one @pankod/refine-core version in node_modules and creating different instances)

  Managing as peerDependencies + devDependencies seems like the best way for now to avoid such issues.

@pankod/refine-core@3.47.0

Minor Changes

• #2217 b4aae00f77 Thanks @omeraplak! - All of the refine packages have dependencies on the @pankod/refine-core package. So far we have managed these dependencies with peerDependencies + dependencies but this causes issues like [BUG] Only the most recent version of refine-core does not break app authentication #2183. (having more than one @pankod/refine-core version in node_modules and creating different instances)

  Managing as peerDependencies + devDependencies seems like the best way for now to avoid such issues.

@pankod/refine-demo-sidebar@3.26.0

Minor Changes

• #2217 b4aae00f77 Thanks @omeraplak! - All of the refine packages have dependencies on the @pankod/refine-core package. So far we have managed these dependencies with peerDependencies + dependencies but this causes issues like [BUG] Only the most recent version of refine-core does not break app authentication #2183. (having more than one @pankod/refine-core version in node_modules and creating different instances)

  Managing as peerDependencies + devDependencies seems like the best way for now to avoid such issues.

@pankod/refine-graphql@4.4.0

Minor Changes

• #2217 b4aae00f77 Thanks @omeraplak! - All of the refine packages have dependencies on the @pankod/refine-core package. So far we have managed these dependencies with peerDependencies + dependencies but this causes issues like [BUG] Only the most recent version of refine-core does not break app authentication #2183. (having more than one @pankod/refine-core version in node_modules and creating different instances)

  Managing as peerDependencies + devDependencies seems like the best way for now to avoid such issues.

@pankod/refine-hasura@4.4.0

Minor Changes

• #2217 b4aae00f77 Thanks @omeraplak! - All of the refine packages have dependencies on the @pankod/refine-core package. So far we have managed these dependencies with peerDependencies + dependencies but this causes issues like [BUG] Only the most recent version of refine-core does not break app authentication #2183. (having more than one @pankod/refine-core version in node_modules and creating different instances)

  Managing as peerDependencies + devDependencies seems like the best way for now to avoid such issues.

@pankod/refine-kbar@0.3.0

Minor Changes

• #2217 b4aae00f77 Thanks @omeraplak! - All of the refine packages have dependencies on the @pankod/refine-core package. So far we have managed these dependencies with peerDependencies + dependencies but this causes issues like [BUG] Only the most recent version of refine-core does not break app authentication #2183. (having more than one @pankod/refine-core version in node_modules and creating different instances)

  Managing as peerDependencies + devDependencies seems like the best way for now to avoid such issues.

@pankod/refine-mui@3.38.0

Minor Changes

• #2217 b4aae00f77 Thanks @omeraplak! - All of the refine packages have dependencies on the @pankod/refine-core package. So far we have managed these dependencies with peerDependencies + dependencies but this causes issues like [BUG] Only the most recent version of refine-core does not break app authentication #2183. (having more than one @pankod/refine-core version in node_modules and creating different instances)

  Managing as peerDependencies + devDependencies seems like the best way for now to avoid such issues.

Patch Changes

• Updated dependencies [b4aae00f77]:
  • @pankod/refine-react-hook-form@3.28.0

@pankod/refine-nestjsx-crud@3.26.0

Minor Changes

• #2217 b4aae00f77 Thanks @omeraplak! - All of the refine packages have dependencies on the @pankod/refine-core package. So far we have managed these dependencies with peerDependencies + dependencies but this causes issues like [BUG] Only the most recent version of refine-core does not break app authentication #2183. (having more than one @pankod/refine-core version in node_modules and creating different instances)

  Managing as peerDependencies + devDependencies seems like the best way for now to avoid such issues.

@pankod/refine-nextjs-router@3.26.0

Minor Changes

• #2217 b4aae00f77 Thanks @omeraplak! - All of the refine packages have dependencies on the @pankod/refine-core package. So far we have managed these dependencies with peerDependencies + dependencies but this causes issues like [BUG] Only the most recent version of refine-core does not break app authentication #2183. (having more than one @pankod/refine-core version in node_modules and creating different instances)

  Managing as peerDependencies + devDependencies seems like the best way for now to avoid such issues.

@pankod/refine-nhost@3.28.0

Minor Changes

• #2217 b4aae00f77 Thanks @omeraplak! - All of the refine packages have dependencies on the @pankod/refine-core package. So far we have managed these dependencies with peerDependencies + dependencies but this causes issues like [BUG] Only the most recent version of refine-core does not break app authentication #2183. (having more than one @pankod/refine-core version in node_modules and creating different instances)

  Managing as peerDependencies + devDependencies seems like the best way for now to avoid such issues.

@pankod/refine-react-hook-form@3.28.0

Minor Changes

• #2217 b4aae00f77 Thanks @omeraplak! - All of the refine packages have dependencies on the @pankod/refine-core package. So far we have managed these dependencies with peerDependencies + dependencies but this causes issues like [BUG] Only the most recent version of refine-core does not break app authentication #2183. (having more than one @pankod/refine-core version in node_modules and creating different instances)

  Managing as peerDependencies + devDependencies seems like the best way for now to avoid such issues.

@pankod/refine-react-location@3.26.0

Minor Changes

• #2217 b4aae00f77 Thanks @omeraplak! - All of the refine packages have dependencies on the @pankod/refine-core package. So far we have managed these dependencies with peerDependencies + dependencies but this causes issues like [BUG] Only the most recent version of refine-core does not break app authentication #2183. (having more than one @pankod/refine-core version in node_modules and creating different instances)

  Managing as peerDependencies + devDependencies seems like the best way for now to avoid such issues.

@pankod/refine-react-router-v6@3.26.0

Minor Changes

• #2217 b4aae00f77 Thanks @omeraplak! - All of the refine packages have dependencies on the @pankod/refine-core package. So far we have managed these dependencies with peerDependencies + dependencies but this causes issues like [BUG] Only the most recent version of refine-core does not break app authentication #2183. (having more than one @pankod/refine-core version in node_modules and creating different instances)

  Managing as peerDependencies + devDependencies seems like the best way for now to avoid such issues.

@pankod/refine-react-table@4.2.0

Minor Changes

• #2217 b4aae00f77 Thanks @omeraplak! - All of the refine packages have dependencies on the @pankod/refine-core package. So far we have managed these dependencies with peerDependencies + dependencies but this causes issues like [BUG] Only the most recent version of refine-core does not break app authentication #2183. (having more than one @pankod/refine-core version in node_modules and creating different instances)

  Managing as peerDependencies + devDependencies seems like the best way for now to avoid such issues.

@pankod/refine-simple-rest@3.26.0

Minor Changes

• #2217 b4aae00f77 Thanks @omeraplak! - All of the refine packages have dependencies on the @pankod/refine-core package. So far we have managed these dependencies with peerDependencies + dependencies but this causes issues like [BUG] Only the most recent version of refine-core does not break app authentication #2183. (having more than one @pankod/refine-core version in node_modules and creating different instances)

  Managing as peerDependencies + devDependencies seems like the best way for now to avoid such issues.

@pankod/refine-strapi@3.26.0

Minor Changes

• #2217 b4aae00f77 Thanks @omeraplak! - All of the refine packages have dependencies on the @pankod/refine-core package. So far we have managed these dependencies with peerDependencies + dependencies but this causes issues like [BUG] Only the most recent version of refine-core does not break app authentication #2183. (having more than one @pankod/refine-core version in node_modules and creating different instances)

  Managing as peerDependencies + devDependencies seems like the best way for now to avoid such issues.

@pankod/refine-strapi-graphql@4.2.0

Minor Changes

• #2217 b4aae00f77 Thanks @omeraplak! - All of the refine packages have dependencies on the @pankod/refine-core package. So far we have managed these dependencies with peerDependencies + dependencies but this causes issues like [BUG] Only the most recent version of refine-core does not break app authentication #2183. (having more than one @pankod/refine-core version in node_modules and creating different instances)

  Managing as peerDependencies + devDependencies seems like the best way for now to avoid such issues.

@pankod/refine-strapi-v4@3.26.0

Minor Changes

• #2217 b4aae00f77 Thanks @omeraplak! - All of the refine packages have dependencies on the @pankod/refine-core package. So far we have managed these dependencies with peerDependencies + dependencies but this causes issues like [BUG] Only the most recent version of refine-core does not break app authentication #2183. (having more than one @pankod/refine-core version in node_modules and creating different instances)

  Managing as peerDependencies + devDependencies seems like the best way for now to avoid such issues.

@pankod/refine-supabase@3.28.0

Minor Changes

• #2217 b4aae00f77 Thanks @omeraplak! - All of the refine packages have dependencies on the @pankod/refine-core package. So far we have managed these dependencies with peerDependencies + dependencies but this causes issues like [BUG] Only the most recent version of refine-core does not break app authentication #2183. (having more than one @pankod/refine-core version in node_modules and creating different instances)

  Managing as peerDependencies + devDependencies seems like the best way for now to avoid such issues.

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 0b60fc1:

Sandbox	Source
fine-foods	Configuration
fine-foods-client	Configuration

[refine-bot]

♻️ PR Preview 0b60fc1 has been successfully destroyed since this PR has been closed.

_{🤖 By surge-preview}

[refine-bot]

♻️ PR Preview 0b60fc1 has been successfully destroyed since this PR has been closed.

_{🤖 By surge-preview}

[refine-bot]

😭 Deploy PR Preview 0b60fc1 failed. Build logs

_{🤖 By surge-preview}