[github-actions]

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

@fluojs/email@4.0.0

Major Changes

• #3995 d12115b Thanks @ayden94! - Require the optional Node SMTP peer nodemailer@^10.0.9 and resolve the workspace to 10.1.0 to address GHSA-prgh-xp8r-p3m5, GHSA-v53p-9fqp-m79j, GHSA-g57g-f23g-4646, GHSA-8vvx-rff5-p5rq, and GHSA-6vj9-mwq6-2f5v. Preserve the transport-agnostic root, explicit SMTP configuration, receipt mapping, and caller-owned versus factory-owned lifecycle.

  Migration: Node SMTP consumers upgrading from @fluojs/email 3.0.3 must replace Nodemailer 9.x with nodemailer@^10.0.9 and regenerate their lockfile. Nodemailer 10 requires Node.js 20 or newer and bundles its declarations; @types/nodemailer remains an optional peer. The Fluo wrapper and factory APIs do not change. Existing caller-owned transporters must use the supported peer. Consumers using only the transport-agnostic root do not need Nodemailer.

  TypeScript Node consumers must provide @types/node and explicitly include "types": ["node"] when ambient type inclusion is disabled, including TypeScript 6, without disabling strict declaration checks.

@fluojs/microservices@3.0.0

Major Changes

• #4000 4c2f534 Thanks @ayden94! - Require patched Fastify 5.12.7 and raise the optional gRPC peer security floor to @grpc/grpc-js 1.14.5. Existing transport APIs and resource ownership remain unchanged.

  Generated gRPC projects now require @grpc/grpc-js ^1.14.5, matching the microservices peer contract and the CLI installation guidance.

  Migration: Applications using @grpc/grpc-js 1.14.4 must install @grpc/grpc-js ^1.14.5 and refresh their lockfile before upgrading @fluojs/microservices. The gRPC peers remain optional when the application does not use gRPC.

@fluojs/cli@4.0.1

Patch Changes

• #4000 4c2f534 Thanks @ayden94! - Require patched Fastify 5.12.7 and raise the optional gRPC peer security floor to @grpc/grpc-js 1.14.5. Existing transport APIs and resource ownership remain unchanged.

  Generated gRPC projects now require @grpc/grpc-js ^1.14.5, matching the microservices peer contract and the CLI installation guidance.

  Migration: Applications using @grpc/grpc-js 1.14.4 must install @grpc/grpc-js ^1.14.5 and refresh their lockfile before upgrading @fluojs/microservices. The gRPC peers remain optional when the application does not use gRPC.

@fluojs/platform-fastify@2.0.6

Patch Changes

• #4000 4c2f534 Thanks @ayden94! - Require patched Fastify 5.12.7 and raise the optional gRPC peer security floor to @grpc/grpc-js 1.14.5. Existing transport APIs and resource ownership remain unchanged.

  Generated gRPC projects now require @grpc/grpc-js ^1.14.5, matching the microservices peer contract and the CLI installation guidance.

  Migration: Applications using @grpc/grpc-js 1.14.4 must install @grpc/grpc-js ^1.14.5 and refresh their lockfile before upgrading @fluojs/microservices. The gRPC peers remain optional when the application does not use gRPC.

@fluojs/example-fluo-blog@0.0.6

Patch Changes

• Updated dependencies [4c2f534]:
  • @fluojs/platform-fastify@2.0.6

@fluojs/example-openapi-multiple-documents@0.0.9

Patch Changes

• Updated dependencies [4c2f534]:
  • @fluojs/platform-fastify@2.0.6

@fluojs/example-react-stable-ssr@0.0.9

Patch Changes

• Updated dependencies [4c2f534]:
  • @fluojs/platform-fastify@2.0.6

@fluojs/example-react-vite-ssr@0.0.9

Patch Changes

• Updated dependencies [4c2f534]:
  • @fluojs/platform-fastify@2.0.6

배포 복구 검증

• 배포 실패를 고친 PR #4004가 main에 병합되어 source release38582249647의 전체 검증이 통과했습니다. 이 Version PR은 남아 있던 보안 changeset을 소비합니다.
• CLI의 미게시4.0.0 major 이후4.0.1 patch에서도 이전 published tag보다 높은 major changelog와 정확한 Node migration 근거를 검증하도록 내부 release verifier를 보완했습니다. major semver, migration 안내, 실제 engine 범위를 낮추거나 게이트를 생략하지 않습니다.
• AI가 내부 verifier 수정과 회귀 테스트를 작성하고 검토했습니다. 사람의 추가 코드 리뷰를 수행했다고 주장하지 않습니다.
• starter snapshot 테스트9/9 통과. engine/release-lane owner 테스트74/74 통과. 두 reviewer heading 차단 사례는 수정 전 실패를 재현했습니다. 실제 stable release lane은0 pending intents,4 manifest version deltas로 통과했습니다. 변경 파일 lint와 diff 검사도 통과했습니다.
• 현재 검증 대상 head a855b4e4a6209a7a20e1d1366de227441b679282에 대한 GitHub CI와 병합 후 canonical Changesets Release에서 실제 npm 게시 성공을 확인합니다. 로컬 npm publish는 실행하지 않습니다.

CI 컴파일 integration 제한 시간

CI run 38593631038에서 실제 컴파일·앱 부팅 테스트의 기본 5초 제한 초과를 확인했습니다. 두 테스트 파일의 세 호출에 인접 integration 테스트와 같은 30초 제한을 명시했습니다. 실제 compile·HTTP 호출, 단언, cleanup, 실행 범위는 그대로이며 sleep·retry·skip을 추가하지 않았습니다. 관련 테스트 19/19, lint·diagnostics·diff 검사가 통과했고, 새 exact head의 증분 리뷰도 APPROVE입니다. 최종 head CI와 실제 게시 성공은 별도로 확인합니다.