From 5aaec1b18a9d8a7ef6f8715b72c87c8c124f2fcd Mon Sep 17 00:00:00 2001 From: William Mantly Date: Mon, 27 Jul 2026 17:46:26 -0400 Subject: [PATCH] Bump sso-manager-node to v1.6.1, proxy to v1.5.1 Co-Authored-By: Claude Sonnet 5 --- CHANGELOG.md | 19 +++++++++++++++++++ proxy | 2 +- sso-manager-node | 2 +- 3 files changed, 21 insertions(+), 2 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 34bcacd..40887ff 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -10,6 +10,25 @@ for what changed inside the apps it composes. ## [Unreleased] +## [1.9.0] - 2026-07-27 + +### Bumped +- sso-manager-node -> [v1.6.1](https://github.com/theta42/sso-manager-node/releases/tag/v1.6.1) +- proxy -> [v1.5.1](https://github.com/theta42/proxy/releases/tag/v1.5.1) + +Both apps had every native `alert()`/`confirm()` call removed, replaced by +`@simpleworkjs/frontend`'s `app.messages.action`/`confirm`/`toast` (the +same modules adopted in [1.8.0](#180---2026-07-27)). This was found live, +mid browser-verification of that release: clicking sso-manager-node +directory.ejs's "Rotate Client Secret" triggered a native `confirm()`, +which blocks all further browser events on the page — a real hazard for +anyone driving the app with browser automation, not just a cosmetic +inconsistency. sso-manager-node also dropped `app.user.remove`/ +`app.oauthClient.remove` from `public/js/app.js` (dead code with a native +`confirm()` guard and zero callers). + +No `setup.sh`, compose, or config change. + ## [1.8.0] - 2026-07-27 ### Bumped diff --git a/proxy b/proxy index 3686a5d..58204da 160000 --- a/proxy +++ b/proxy @@ -1 +1 @@ -Subproject commit 3686a5ddb8bfb7dae2e949553c38b317ce8fa601 +Subproject commit 58204da3cb250d4b21a8647ab24d5297a8ef2941 diff --git a/sso-manager-node b/sso-manager-node index ffb2e99..18119d5 160000 --- a/sso-manager-node +++ b/sso-manager-node @@ -1 +1 @@ -Subproject commit ffb2e991993d6be3bf88b65fd9dc017bbb806fc0 +Subproject commit 18119d54aac233f98663a25c5df9b15e8842748b