ci: fix checks

Author: mrlubos

.changeset/fix-runtime-config-path.md

@@ -6,5 +6,5 @@
 
 ### Changed `runtimeConfigPath` behavior
 
-This was a known, long-standing issue confusing first-time users. Before, defining client `runtimeConfigPath` value would paste it verbatim to the generated output. This release changes the behavior to resolve relative to the output folder.
+This was a known, long-standing issue confusing first-time users. Before, defining client `runtimeConfigPath` value would paste it verbatim to the generated output. This release changes the behavior to resolve relative to the current working directory the same way output path works.
 

examples/openapi-ts-next/openapi-ts.config.ts

@@ -13,7 +13,7 @@ export default defineConfig({
   plugins: [
     {
       name: '@hey-api/client-next',
-      runtimeConfigPath: '../hey-api',
+      runtimeConfigPath: './src/hey-api',
     },
     '@hey-api/sdk',
     {

packages/openapi-ts/src/plugins/@hey-api/client-core/client.ts

@@ -16,9 +16,8 @@ export function resolveRuntimeConfigPath({
   runtimeConfigPath: string;
 }): string {
   const isAbsolutePath = path.isAbsolute(runtimeConfigPath);
-
-  const isFileSystemPath =
-    isAbsolutePath || runtimeConfigPath.startsWith('./') || runtimeConfigPath.startsWith('../');
+  // Use a single regex to match './' or '../' at the start
+  const isFileSystemPath = isAbsolutePath || /^\.\.?\//.test(runtimeConfigPath);
   if (!isFileSystemPath) {
     return runtimeConfigPath;
   }