Repository navigation
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: vaadin/sso-kit
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 4.1.3
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: vaadin/sso-kit
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 4.2.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 6 commits
- 37 files changed
- 6 contributors
Commits on Sep 2, 2026
-
chore: upgrade to Vaadin 25.3, Spring Boot 4.1.1 and react-router 8 (#…
…230) Aligns SSO Kit with the Vaadin 25.3 platform, which itself builds against Spring Boot 4.1.1 and license-checker 3.1.2, and moves the React client onto the router that Hilla 25.3 actually generates code for. ## Platform upgrade - `flow`/`hilla`: `25.1-SNAPSHOT` → `25.3-SNAPSHOT` - `spring-boot`: `4.0.7` → `4.1.1` (Spring Framework 7.0.9, Spring Security 7.1.1) - `vaadin.license.checker`: `3.0.1` → `3.1.2`, matching Flow 25.3 - `vaadin-parent`: `3.0.0` → `3.0.3` - Maven plugins: jar 3.5.1, source 3.4.0, surefire 3.5.6, spotless 3.10.1 - Playwright: `1.52.0` → `1.62.0`, both in the demo POM and in the IT workflow - Dropped the `json-smart` exclusion and pin from `sso-kit-core`: Spring Boot 4.1.1 already manages json-smart 2.6.0, which is the latest release - CI: `actions/checkout`, `setup-java` and `setup-node` v5, `actions/cache` v4, Node 22 ## Client packages - `@vaadin/hilla-frontend`: `24.4.0-alpha4` → `25.3.0-beta1` - Lit client: `@vaadin/router` `1.7.5` → `2.0.1`; replaced the deprecated v1 type aliases (`Context`, `ActionFn`) with `RouteContext` - React client: `JSX.Element` → `React.JSX.Element` for the React 19 types ## react-router 8 in the React client Vaadin 25.3 pins react-router 8.3.1, react 19.2.8 and react-dom 19.2.8 in the frontend it generates, while `react-router-dom` was discontinued at 7.18.3. Depending on `react-router-dom` 7 would have given applications a second, nested router next to the one they already run on, so `ProtectedRoute` would have read a different router context than the one rendering it. - `ProtectedRoute` imports from `react-router` instead of `react-router-dom` - `react` and `react-router` are now **peer dependencies** (`react: 18 || 19`, `react-router: 7 || 8`), the same way the Lit client already declares `lit`, so the application's own copies are used. They are kept as dev dependencies at the versions Vaadin 25.3 ships. > [!NOTE] > Applications on the React client must have `react-router` (7 or 8) in their own dependencies — with Vaadin 25.3 that is already the case for generated projects. Apps still importing from `react-router-dom` should switch to `react-router`. ## Tests The endpoint mocks were empty placeholders, so neither client could be exercised. They are now implemented (`SingleSignOnEndpointMock`, `UserEndpointMock`, `BackChannelLogoutEndpointMock`) and route protection is covered in both clients: the redirect when the user is not authenticated, a custom redirect path, nested routes, and delegation to the original route action when authenticated. The React tests render through a real react-router memory router (`createMemoryRouter` + `RouterProvider`). ## Ignore rules - The demo's own ignore file still pointed at `frontend/generated`, a path from the old project layout; because the pattern contains a slash it is anchored to the module root and never matched `src/main/frontend/generated`, so the generated output showed up as untracked. It now points at the real paths next to the other `vaadin-maven-plugin` entries and covers the dev bundle as well. - Generated frontend output (`src/main/bundles`, `src/main/frontend/generated`) that had been committed by accident is removed. - Root ignore: `sso-kit-client/node_modules` → `**/node_modules`, since npm workspaces now creates a nested one for the React client.
Configuration menu - View commit details
-
Copy full SHA for 757e90a - Browse repository at this point
Copy the full SHA 757e90aView commit details
Commits on Sep 8, 2026
-
Replace pull_request_target with pull_request in CI workflow (#224)
* Replace pull_request_target with pull_request in CI workflow Switch from pull_request_target to pull_request. Removes environment gate. Integration test job skips for fork PRs since TB_LICENSE is not available. Bumps upload-artifact to v5 and forces Node.js 24. * ci: cache workspace-local node_modules to fix react-router build failure The react-router 8 upgrade left react-router installed under sso-kit-client/react/node_modules instead of being hoisted. The node_modules cache only covered sso-kit-client/node_modules, so a cache hit skipped npm ci and the TypeScript build could not resolve react-router. Cache the per-workspace node_modules too and bump the cache key so the incomplete cached entry is not reused. --------- Co-authored-by: Giovanni Lovato <giovanni@vaadin.com>
Configuration menu - View commit details
-
Copy full SHA for b2191bc - Browse repository at this point
Copy the full SHA b2191bcView commit details
Commits on Sep 15, 2026
-
chore:upgrade 4.2-SNAPSHOT (#231)
* chore:upgrade 4.2-SNAPSHOT * use the install instead of package * Update package.json * Update lerna.json * Update package.json * Update package.json * chore: bump the client packages in the lockfile to 4.2.0 The workspace entries in `package-lock.json` still carried 4.1.3, which makes `npm ci` refuse to install once the node_modules cache misses. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * fix: stop the parallel client test suites from racing in Vite `lerna run test --parallel` starts three Karma runs at once, and each one boots its own Vite dev server. Two pieces of state were shared between them, so the suites failed randomly with `Uncaught Error loading <package>/test/<name>.test.ts`: - The Vite root is the Karma `basePath`, which is the workspace root, so all three dependency optimizers used the same `node_modules/.vite` cache directory and wiped it while a sibling was serving files from it. - Vite 4.2 bundles a TypeScript config file into a temp file named after the current millisecond. Three servers loading the same `vite.config.ts` collide whenever two of them start in the same millisecond, and one deletes the other's temp file. Inline the Vite configuration in `karma.config.cjs` with `configFile: false` and pin `cacheDir` to the package being tested, so nothing is shared. The suites went from ~40% failures to 30/30 green runs locally. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Configuration menu - View commit details
-
Copy full SHA for 4ef39d7 - Browse repository at this point
Copy the full SHA 4ef39d7View commit details
Commits on Sep 16, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 5d31012 - Browse repository at this point
Copy the full SHA 5d31012View commit details
Commits on Sep 21, 2026
-
chore: deprecate the SSO Kit entry points (#234)
* chore: deprecate the SSO Kit entry points SSO Kit is deprecated as of Vaadin 25.3 and will be removed in Vaadin 26.0, so the API it is entered through is marked accordingly. Only the types an application has to name in order to use the kit are annotated: the Flow and Hilla auto-configurations and their configuration properties, the Hilla single sign-on context, the logout event and the Keycloak user mapper. The types that are only reachable through one of those, such as the properties base class, the endpoints and the DTOs they return, are left alone so that application code gets one warning per feature to migrate instead of one per declaration. The back-channel logout filter and its supporting types were already deprecated in 3.1. The client packages get the same treatment on their entry points: the Lit single sign-on context and its default instance, and the React provider, hook and route protection helper. * chore: use the same deprecation message in the client packages The client entry points only said that SSO Kit is going away, while the Java ones also name the replacement. They now carry the same sentence, so the whole kit tells the same story wherever the deprecation is read. --------- Co-authored-by: totally-not-ai[bot] <290682512+totally-not-ai[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 8fb6ebb - Browse repository at this point
Copy the full SHA 8fb6ebbView commit details
Commits on Sep 22, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 64344e2 - Browse repository at this point
Copy the full SHA 64344e2View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 4.1.3...4.2.0