You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The single-marker idempotency check (skip if patchstackGuard present) meant re-running protect
after a connect upgrade silently did nothing — so an app wired by 0.3.0 never gained the new
server-function guard. Rework patchStart to reconcile each piece independently: extend the guard
import, add each middleware definition, and register each guard only when absent. Re-running now
adds exactly what's missing (verified: 0.3.0-wired app gains patchstackFunctionGuard with no
duplication; a second run is a no-op).
Copy file name to clipboardExpand all lines: package.json
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
{
2
2
"name": "@patchstack/connect",
3
-
"version": "0.3.1",
3
+
"version": "0.3.2",
4
4
"description": "Patchstack connector for JavaScript applications. Scans your lockfile and reports installed packages to Patchstack for vulnerability monitoring.",
0 commit comments