Costin Serban
Costin Serban
The browser's history is impacted by the oAuth authentication procedure between the instance and the FlowFuse platform in which two redirects occur (one in `/account/authorize` and the second in `/account/complete/:code`)....
@knolleary, I assigned you as well so we won't loose track of it
not something we can easily fix, moving it to todo as other priorities take precedence
We've been carrying over this over multiple release versions and has no urgency or immediate fix that can be addressed as the oauth redirect is integral to the NR authentication...
v4 has a hard dependency of node >= v20 while [our docs](https://flowfuse.com/docs/contribute/local/?utm_campaign=215266513-FlowFuse+Expert#node.js) state that we support v18.
We're risking breaking things upgrading tailwind to 4.0 without making sure all on-premise installations have also done so. I'm fine with upgrading to 4.0 but we should make it clear...
spoke w @hardillb we can safely upgrade to 4.0, I'll add a changelog request announcing our minimum node version change and one for the docs to update the entry
[Changelog request](https://github.com/FlowFuse/website/issues/4083) and [docs update](https://github.com/FlowFuse/flowfuse/pull/6291) pr's are in place.
I'd love a go at the settings pages with tailwind plus, worth getting in my opinion
I set a hard minimum allowed limit of `4.0.0` but `4.1.17` is installed and will match any `4.*.*` version