Skip to content

chore(deps): bump nest-native libs to latest (lockout/authlock 0.4.0, messaging 0.5.0)#68

Open
rodrigobnogueira wants to merge 1 commit into
mainfrom
chore/bump-nest-native-libs
Open

chore(deps): bump nest-native libs to latest (lockout/authlock 0.4.0, messaging 0.5.0)#68
rodrigobnogueira wants to merge 1 commit into
mainfrom
chore/bump-nest-native-libs

Conversation

@rodrigobnogueira

Copy link
Copy Markdown
Contributor

Bumps the three nest-native pins that had fallen behind their latest published versions. The other six libraries were already current.

Package Was Now
@authlock/core ^0.3.0 ^0.4.0
@nest-native/lockout ^0.3.1 ^0.4.0
@nest-native/messaging ^0.3.1 ^0.5.0

Why these are safe

All three are additive, backward-compatible releases, and every surface this app consumes is unchanged — so there are no app code changes, only the pins + regenerated lockfile.

  • lockout / authlock 0.4.0 — adds per-dimension identity normalize, resetAll() / store clearAll(), and an audit-logging recipe. The app's existing LockoutModule.forRootAsync config (SqliteLockoutStore, ['email']/['ip'] parameters, logger) is untouched.
  • messaging 0.4.0 + 0.5.0 — adds the opt-in worker wake tiers (OutboxWaker, WakeSocketServer/Client, Postgres LISTEN/NOTIFY). The worker loop is an unchanged pure poller when no waker is passed, which is how this app runs it.

Verification

Full CI gate green locally (node --import tsx suite, SQLite / in-process profile):

  • typecheck, client-smoke:typecheck
  • lint, complexity:check
  • test / test:cov (exit 0)
  • build
  • security:audit (--audit-level=high) — passes. The 6 remaining moderate advisories are all in dev/build tooling (esbuild via drizzle-kit, qs via typed-rest-client), outside the published production surface; Dependabot's territory, not a release blocker.

Live-Kafka e2e (test:full) not run in this environment; the bump does not touch the Kafka transport surface.

Possible follow-up (not in this PR)

The app locks by ['email'], so Alice@x.com / alice@x.com / alice@x.com currently split into three separate counters — the exact case-normalization bypass lockout 0.4.0's normalize closes. Adopting normalize: { email: (v) => v.trim().toLowerCase() } would be a natural showcase of the new version, but belongs in its own scoped PR.

… messaging 0.5.0)

Move the three pins that had fallen behind their latest published versions:

- @authlock/core        ^0.3.0 -> ^0.4.0
- @nest-native/lockout  ^0.3.1 -> ^0.4.0
- @nest-native/messaging ^0.3.1 -> ^0.5.0

All three are additive, backward-compatible releases: lockout/authlock 0.4.0
add per-dimension identity `normalize`, `resetAll()`, and audit-logging docs;
messaging 0.4.0/0.5.0 add the opt-in OutboxWaker / WakeSocket / Postgres
LISTEN-NOTIFY wake tiers (the poller is unchanged when no waker is passed). No
app code changes — every surface the app consumes is unchanged. The remaining
libraries were already at their latest.

Full gate green: typecheck, client-smoke typecheck, lint, complexity, tests
(exit 0), build, and security:audit (6 moderate advisories remain, all in
dev/build tooling only — esbuild via drizzle-kit, qs via typed-rest-client —
outside the production surface and below the high gate).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant