various new clickhouse syncs #3122
db-migration-backwards-compatibility.yaml
on: pull_request
Check if migrations changed
8s
Back-compat — Current branch migrations with dev branch code
14m 20s
No migration changes (skipped)
0s
Forward-compat — Current branch code with dev branch migrations
3m 28s
Annotations
3 errors and 2 warnings
|
Back-compat — Current branch migrations with dev branch code
Process completed with exit code 1.
|
|
tests/general/lint.test.ts > `pnpm run lint` > completes successfully:
apps/e2e/tests/general/lint.test.ts#L12
AssertionError: Expected no error to be thrown!
stdout:
> @stackframe/monorepo@0.0.0 lint /home/runner/work/stack-auth/stack-auth
> pnpm pre && turbo run lint --continue -- --max-warnings=0
> @stackframe/monorepo@0.0.0 pre /home/runner/work/stack-auth/stack-auth
> pnpm pre-preinstall
> @stackframe/monorepo@0.0.0 pre-preinstall /home/runner/work/stack-auth/stack-auth
> pnpx only-allow pnpm && node -e "if(process.env.STACK_SKIP_TEMPLATE_GENERATION !== 'true') require('child_process').execSync('pnpx --package=tsx tsx ./scripts/generate-sdks.ts', {stdio: 'inherit'})"
Generator lock file /home/runner/work/stack-auth/stack-auth/generator-lock-file.untracked.lock exists. Waiting for it to be released...
• Packages in scope: @stackframe/backend, @stackframe/convex-example, @stackframe/dashboard, @stackframe/dashboard-ui-components, @stackframe/dev-launchpad, @stackframe/docs-examples, @stackframe/docs-mintlify, @stackframe/e-commerce-demo, @stackframe/e2e-tests, @stackframe/example-cjs-test, @stackframe/example-demo-app, @stackframe/example-middleware-demo, @stackframe/example-supabase, @stackframe/hosted-components, @stackframe/init-stack, @stackframe/js, @stackframe/js-example, @stackframe/lovable-react-18-example, @stackframe/mock-oauth-server, @stackframe/react, @stackframe/sdk-spec, @stackframe/stack, @stackframe/stack-cli, @stackframe/stack-docs, @stackframe/stack-sc, @stackframe/stack-shared, @stackframe/stack-ui, @stackframe/swift-sdk, @stackframe/template, react-example
• Running lint in 30 packages
• Remote caching disabled
::group::@stackframe/example-cjs-test:lint
cache miss, executing 5d3635103889c083
> @stackframe/example-cjs-test@2.8.80 lint /home/runner/work/stack-auth/stack-auth/examples/cjs-test
> next lint --max-warnings=0
✔ No ESLint warnings or errors
::endgroup::
::group::@stackframe/example-middleware-demo:lint
cache miss, executing 11c77af09dd80a6c
> @stackframe/example-middleware-demo@2.8.80 lint /home/runner/work/stack-auth/stack-auth/examples/middleware
> next lint --max-warnings=0
✔ No ESLint warnings or errors
::endgroup::
::group::@stackframe/docs-examples:lint
cache miss, executing 2be3f597df3a171c
> @stackframe/docs-examples@2.8.80 lint /home/runner/work/stack-auth/stack-auth/examples/docs-examples
> next lint --max-warnings=0
✔ No ESLint warnings or errors
::endgroup::
::group::@stackframe/example-demo-app:lint
cache miss, executing 080ae3ceeba2e756
> @stackframe/example-demo-app@2.8.80 lint /home/runner/work/stack-auth/stack-auth/examples/demo
> next lint --max-warnings=0
`next lint` is deprecated and will be removed in Next.js 16.
For new projects, use create-next-app to choose your preferred linter.
For existing projects, migrate to the ESLint CLI:
npx @next/codemod@canary next-lint-to-eslint-cli .
✔ No ESLint warnings or errors
::endgroup::
::group::@stackframe/convex-example:lint
cache miss, executing 1f69f404e375fd29
> @stackframe/convex-example@2.8.80 lint /home/runner/work/stack-auth/stack-auth/examples/convex
> next lint --max-warnings=0
`next lint` is deprecated and will be removed in Next.js 16.
For new projects, use create-next-app to choose your preferred linter.
For existing projects, migrate to the ESLint CLI:
npx @next/codemod@canary next-lint-to-eslint-cli .
✔ No ESLint warnings or errors
::endgroup::
@stackframe/docs-mintlify:lint
cache miss, executing bf8e02339dabb4c4
> @stackframe/docs-mintlify@0.0.0 lint /home/runner/work/stack-auth/stack-auth/docs-mintlify
> mint validate && mint broken-links --max-warnings=0
error failed to extract mintlify framework version 0.0.2753, ZlibError: zlib:
unexpected end of file
ELIFECYCLE Command failed with exit code 1.
[WARN] command finished with error, but continuing...
::group::@stackframe/stack-docs:lint
cache miss, executing ea5a38cc0a89998d
> @stackframe/stack-docs@2.8.80 lint /home/runner/work/stack-auth/stack-auth/docs
> next lint --max-warnings=0
`next lint` is deprecated and will be removed in Next.js 16.
For new projects, use create-next-app to choose your preferred linter.
For ex
|
|
Forward-compat — Current branch code with dev branch migrations
Process completed with exit code 1.
|
|
Back-compat — Current branch migrations with dev branch code
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: JarvusInnovations/background-action@v1.0.7, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Forward-compat — Current branch code with dev branch migrations
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: JarvusInnovations/background-action@v1.0.7, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|