Repository navigation
chore: update to framework 5.6.0 - #70
Merged
Merged
Conversation
Biome 2.6 formats Markdown and YAML, so `npm run check` failed on 12 files after the dependency update. This is the `biome format --write` output. The YAML files parse to the same data (quote style, one blank line, a trailing comma in the mongo entrypoint list; `docker compose config` validates). The Markdown renders the same text; one list in .clinerules/09 gets looser spacing.
- @adaptivestone/framework ^5.6.0; oxc-parser ^0.156.0 (the 5.6.0 peer). - Every other package moves to the newest version its range allows (lockfile only): mongoose 9.11.4, express 5.3.0, @sentry/node 11.9.0, i18next 26.5.11, zod 4.6.7, Biome 2.6.3, among others. This covers the open Dependabot bumps (follow-redirects, postcss-selector-parser, source-map-js, brace-expansion, undici, nodemailer 9.1.1, biome, i18next, zod, qs). - biome.json moves to the 2.6.3 schema. No code changes: the example registers no validator drivers in bootHttp and its RateLimiter policy sets no consumeKeyComponents.request list. Verified in Docker: check, check:types (gen + tsc), Node 9/9, Bun 9/9, live /health/live, /health/ready, 404 and Person 404. nodemailer stays on 9.x: framework-module-email 2.1.0 pins ^9.0.1, and the open nodemailer advisories are fixed only in 10.1.4+, so `npm audit` still reports them until the email module moves to nodemailer 10.
…eleases - @adaptivestone/framework-module-email ^2.1.1, which moves to nodemailer ^10.2.1: `npm audit` now reports no vulnerabilities (it reported 1 high and 2 moderate nodemailer advisories with 2.1.0). - Declared minimums move to the current releases: @sentry/node ^11.9.0, i18next ^26.5.11, i18next-fs-backend ^2.6.9, zod ^4.6.7, and dev @biomejs/biome ^2.6.3, @types/express ^5.0.6, mongodb-memory-server ^11.3.0, nodemon ^3.1.14. Verified in Docker: check, check:types, Node 9/9, Bun 9/9, and a live GET /email/:email delivered through Mailpit.
This file contains hidden or 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
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.
Summary
Updates the example to framework 5.6.0 and framework-module-email 2.1.1, with every dependency on its current release.
2d288d4):@adaptivestone/framework^5.6.0 and theoxc-parser^0.156.0 peer. No code changes: the example registers no validator drivers insidebootHttp, and itsRateLimiterpolicy sets noconsumeKeyComponents.requestlist, so the 5.6.0 behavior changes do not touch it.cc47e39):@adaptivestone/framework-module-email^2.1.1, which moves to nodemailer ^10.2.1, sonpm auditreports no vulnerabilities (2.1.0 brought in 1 high and 2 moderate nodemailer advisories). Declared minimums move to the current releases:@sentry/node^11.9.0,i18next^26.5.11,i18next-fs-backend^2.6.9,zod^4.6.7, and dev@biomejs/biome^2.6.3,@types/express^5.0.6,mongodb-memory-server^11.3.0,nodemon^3.1.14.2d288d4): every package on the newest in-range version (mongoose 9.11.4, express 5.3.0, …). This covers the open Dependabot PRs (Bump qs from 6.15.3 to 6.16.0 #57, Bump zod from 4.4.3 to 4.6.5 #59–Bump undici from 7.29.0 to 7.30.0 #63, Bump brace-expansion from 5.0.9 to 5.0.12 #65, Bump source-map-js from 1.2.1 to 1.2.2 #67–Bump follow-redirects from 1.16.0 to 1.16.1 #69).biome.jsonmoves to the 2.6.3 schema.5a5a181, own commit): Biome 2.6 formats Markdown and YAML. The YAML files parse to the same data anddocker compose configvalidates; the Markdown renders the same text.Verification (in Docker)
npm run check,npm run check:types(gen + tsc): clean;npm audit: 0 vulnerabilitiesnpm test: 9/9; Bun (docker compose --profile bun run --rm backend-bun): 9/9/health/live200,/health/ready200 with mongo ok, unknown route 404, missing Person 404PERSON_NOT_FOUND, andGET /email/:emaildelivered through Mailpit