refactor(runtime): migrate to node 24 and upgrade deps - #206
Merged
Conversation
Signed-off-by: Dariusz Porowski <3431813+DariuszPorowski@users.noreply.github.com>
Signed-off-by: Dariusz Porowski <3431813+DariuszPorowski@users.noreply.github.com>
1 task
Signed-off-by: Dariusz Porowski <3431813+DariuszPorowski@users.noreply.github.com>
Signed-off-by: Dariusz Porowski <3431813+DariuszPorowski@users.noreply.github.com>
nithyatsu
approved these changes
Mar 19, 2026
sylvainsf
added a commit
to radius-project/radius
that referenced
this pull request
Mar 26, 2026
…Backstage upgrade The dashboard's Backstage dependency upgrade in radius-project/dashboard#206 bumped @backstage/plugin-auth-backend from 0.25.x to 0.27.x. Starting in 0.26.x, the guest auth provider is silently disabled when NODE_ENV=production (set in the dashboard Dockerfile). This causes 401 'Missing credentials' errors on all dashboard pages. Set NODE_ENV=development via the Helm chart so the Backstage guest auth provider remains active. The value is configurable through dashboard.nodeEnv in values.yaml and defaults to 'development'. Fixes: #11519
12 tasks
sylvainsf
added a commit
to radius-project/radius
that referenced
this pull request
Mar 26, 2026
…Backstage upgrade (#11520) # Description The dashboard is completely inoperative on Radius 0.56.0, returning `401 Unauthorized` with `"Missing credentials"` on all pages ([screenshots in issue](https://github.com/radius-project/radius/issues/11519)). **Root cause**: The dashboard repo's PR [radius-project/dashboard#206](radius-project/dashboard#206) ("migrate to node 24 and upgrade deps") bumped `@backstage/plugin-auth-backend` from `^0.25.7` to `^0.27.2`. Starting in Backstage auth-backend 0.26.x, the **guest auth provider is silently disabled when `NODE_ENV=production`**. The dashboard Dockerfile has always set `NODE_ENV=production` (standard Node.js practice), so this behavior change broke guest auth without any visible error. **Fix**: Set `NODE_ENV=development` on the dashboard container via the Helm chart deployment template. This re-enables the Backstage guest auth provider. The value is configurable through `dashboard.nodeEnv` in `values.yaml` and defaults to**Fix**: Set `NODE_ENV=development` on the a**Fix**per tool**Fix**: Set `NODE_ENV=development` on the dashboard container via the Helm chart deployment template. This re-enables the Backstage guest auth provider. The value is configurable through `dashboard.nodeEnv` k required). Fixes: #11519 ## Contributor checklist Please verify that the PR meets the following requirements, where applicable: <!-- This checklist uses "TaskRadio" comments to make certain options mutually exclusive. See: https://github.com/mheap/require-checklist-action?tab=readme-ov-file#radio-groups For details on how this works and why it's required. --> - An overview of proposed schema changes is included in a linked GitHub issue. - [ ] Yes <!-- TaskRadio schema --> - [x] Not applicable <!-- TaskRadio schema --> - A design document PR is created in the [design-notes repository](https://github.com/radius-project/design-notes/), if new APIs are being introduced. - [ ] Yes <!-- TaskRadio design-pr --> - [x] Not applicable <!-- TaskRadio design-pr --> - The design document has been reviewed and approved by Radius maintainers/approvers. - [ ] Yes <!-- TaskRadio design-review --> - [x] Not applicable <!-- TaskRadio design-review --> - A PR for the [samples repository](https://github.com/radius- A PR fosamples) is created, if existing samples are affected by the changes in this PR. - [ ] Yes <!-- TaskRadio samples-pr --> - [x] Not applicable <!-- TaskRadio samples-pr --> - A PR for the [documentation repository](https://github.com/radius-project/docs) is created, if the change- A PR for the [documentation repository](https://gacing updates are made. - [ ] Yes <!-- TaskRadio docs-pr --> - [x] Not applicable <!-- TaskRadio docs-pr --> - A PR for the [recipes repository](https://github.com/radius-project/recipes) is created, if existing recipes are affected by the changes in this PR. - [ ] Yes <!-- TaskRadio recipes-pr --> - [x] Not applicable <!-- TaskRadio recipes-pr -->
sylvainsf
added a commit
to radius-project/radius
that referenced
this pull request
Mar 26, 2026
…Backstage upgrade The dashboard's Backstage dependency upgrade in radius-project/dashboard#206 bumped @backstage/plugin-auth-backend from 0.25.x to 0.27.x. Starting in 0.26.x, the guest auth provider is silently disabled when NODE_ENV=production (set in the dashboard Dockerfile). This causes 401 'Missing credentials' errors on all dashboard pages. Set NODE_ENV=development via the Helm chart so the Backstage guest auth provider remains active. The value is configurable through dashboard.nodeEnv in values.yaml and defaults to 'development'. Fixes: #11519
6 tasks
sk593
pushed a commit
to radius-project/radius
that referenced
this pull request
Mar 26, 2026
…Backstage upgrade (#11520) # Description The dashboard is completely inoperative on Radius 0.56.0, returning `401 Unauthorized` with `"Missing credentials"` on all pages ([screenshots in issue](https://github.com/radius-project/radius/issues/11519)). **Root cause**: The dashboard repo's PR [radius-project/dashboard#206](radius-project/dashboard#206) ("migrate to node 24 and upgrade deps") bumped `@backstage/plugin-auth-backend` from `^0.25.7` to `^0.27.2`. Starting in Backstage auth-backend 0.26.x, the **guest auth provider is silently disabled when `NODE_ENV=production`**. The dashboard Dockerfile has always set `NODE_ENV=production` (standard Node.js practice), so this behavior change broke guest auth without any visible error. **Fix**: Set `NODE_ENV=development` on the dashboard container via the Helm chart deployment template. This re-enables the Backstage guest auth provider. The value is configurable through `dashboard.nodeEnv` in `values.yaml` and defaults to**Fix**: Set `NODE_ENV=development` on the a**Fix**per tool**Fix**: Set `NODE_ENV=development` on the dashboard container via the Helm chart deployment template. This re-enables the Backstage guest auth provider. The value is configurable through `dashboard.nodeEnv` k required). Fixes: #11519 ## Contributor checklist Please verify that the PR meets the following requirements, where applicable: <!-- This checklist uses "TaskRadio" comments to make certain options mutually exclusive. See: https://github.com/mheap/require-checklist-action?tab=readme-ov-file#radio-groups For details on how this works and why it's required. --> - An overview of proposed schema changes is included in a linked GitHub issue. - [ ] Yes <!-- TaskRadio schema --> - [x] Not applicable <!-- TaskRadio schema --> - A design document PR is created in the [design-notes repository](https://github.com/radius-project/design-notes/), if new APIs are being introduced. - [ ] Yes <!-- TaskRadio design-pr --> - [x] Not applicable <!-- TaskRadio design-pr --> - The design document has been reviewed and approved by Radius maintainers/approvers. - [ ] Yes <!-- TaskRadio design-review --> - [x] Not applicable <!-- TaskRadio design-review --> - A PR for the [samples repository](https://github.com/radius- A PR fosamples) is created, if existing samples are affected by the changes in this PR. - [ ] Yes <!-- TaskRadio samples-pr --> - [x] Not applicable <!-- TaskRadio samples-pr --> - A PR for the [documentation repository](https://github.com/radius-project/docs) is created, if the change- A PR for the [documentation repository](https://gacing updates are made. - [ ] Yes <!-- TaskRadio docs-pr --> - [x] Not applicable <!-- TaskRadio docs-pr --> - A PR for the [recipes repository](https://github.com/radius-project/recipes) is created, if existing recipes are affected by the changes in this PR. - [ ] Yes <!-- TaskRadio recipes-pr --> - [x] Not applicable <!-- TaskRadio recipes-pr --> (cherry picked from commit ddd4eeb)
sk593
pushed a commit
to radius-project/radius
that referenced
this pull request
Mar 26, 2026
…Backstage upgrade (#11520) # Description The dashboard is completely inoperative on Radius 0.56.0, returning `401 Unauthorized` with `"Missing credentials"` on all pages ([screenshots in issue](https://github.com/radius-project/radius/issues/11519)). **Root cause**: The dashboard repo's PR [radius-project/dashboard#206](radius-project/dashboard#206) ("migrate to node 24 and upgrade deps") bumped `@backstage/plugin-auth-backend` from `^0.25.7` to `^0.27.2`. Starting in Backstage auth-backend 0.26.x, the **guest auth provider is silently disabled when `NODE_ENV=production`**. The dashboard Dockerfile has always set `NODE_ENV=production` (standard Node.js practice), so this behavior change broke guest auth without any visible error. **Fix**: Set `NODE_ENV=development` on the dashboard container via the Helm chart deployment template. This re-enables the Backstage guest auth provider. The value is configurable through `dashboard.nodeEnv` in `values.yaml` and defaults to**Fix**: Set `NODE_ENV=development` on the a**Fix**per tool**Fix**: Set `NODE_ENV=development` on the dashboard container via the Helm chart deployment template. This re-enables the Backstage guest auth provider. The value is configurable through `dashboard.nodeEnv` k required). Fixes: #11519 ## Contributor checklist Please verify that the PR meets the following requirements, where applicable: <!-- This checklist uses "TaskRadio" comments to make certain options mutually exclusive. See: https://github.com/mheap/require-checklist-action?tab=readme-ov-file#radio-groups For details on how this works and why it's required. --> - An overview of proposed schema changes is included in a linked GitHub issue. - [ ] Yes <!-- TaskRadio schema --> - [x] Not applicable <!-- TaskRadio schema --> - A design document PR is created in the [design-notes repository](https://github.com/radius-project/design-notes/), if new APIs are being introduced. - [ ] Yes <!-- TaskRadio design-pr --> - [x] Not applicable <!-- TaskRadio design-pr --> - The design document has been reviewed and approved by Radius maintainers/approvers. - [ ] Yes <!-- TaskRadio design-review --> - [x] Not applicable <!-- TaskRadio design-review --> - A PR for the [samples repository](https://github.com/radius- A PR fosamples) is created, if existing samples are affected by the changes in this PR. - [ ] Yes <!-- TaskRadio samples-pr --> - [x] Not applicable <!-- TaskRadio samples-pr --> - A PR for the [documentation repository](https://github.com/radius-project/docs) is created, if the change- A PR for the [documentation repository](https://gacing updates are made. - [ ] Yes <!-- TaskRadio docs-pr --> - [x] Not applicable <!-- TaskRadio docs-pr --> - A PR for the [recipes repository](https://github.com/radius-project/recipes) is created, if existing recipes are affected by the changes in this PR. - [ ] Yes <!-- TaskRadio recipes-pr --> - [x] Not applicable <!-- TaskRadio recipes-pr --> (cherry picked from commit ddd4eeb)
willtsai
pushed a commit
to radius-project/radius
that referenced
this pull request
Mar 30, 2026
…Backstage upgrade (#11520) # Description The dashboard is completely inoperative on Radius 0.56.0, returning `401 Unauthorized` with `"Missing credentials"` on all pages ([screenshots in issue](https://github.com/radius-project/radius/issues/11519)). **Root cause**: The dashboard repo's PR [radius-project/dashboard#206](radius-project/dashboard#206) ("migrate to node 24 and upgrade deps") bumped `@backstage/plugin-auth-backend` from `^0.25.7` to `^0.27.2`. Starting in Backstage auth-backend 0.26.x, the **guest auth provider is silently disabled when `NODE_ENV=production`**. The dashboard Dockerfile has always set `NODE_ENV=production` (standard Node.js practice), so this behavior change broke guest auth without any visible error. **Fix**: Set `NODE_ENV=development` on the dashboard container via the Helm chart deployment template. This re-enables the Backstage guest auth provider. The value is configurable through `dashboard.nodeEnv` in `values.yaml` and defaults to**Fix**: Set `NODE_ENV=development` on the a**Fix**per tool**Fix**: Set `NODE_ENV=development` on the dashboard container via the Helm chart deployment template. This re-enables the Backstage guest auth provider. The value is configurable through `dashboard.nodeEnv` k required). Fixes: #11519 ## Contributor checklist Please verify that the PR meets the following requirements, where applicable: <!-- This checklist uses "TaskRadio" comments to make certain options mutually exclusive. See: https://github.com/mheap/require-checklist-action?tab=readme-ov-file#radio-groups For details on how this works and why it's required. --> - An overview of proposed schema changes is included in a linked GitHub issue. - [ ] Yes <!-- TaskRadio schema --> - [x] Not applicable <!-- TaskRadio schema --> - A design document PR is created in the [design-notes repository](https://github.com/radius-project/design-notes/), if new APIs are being introduced. - [ ] Yes <!-- TaskRadio design-pr --> - [x] Not applicable <!-- TaskRadio design-pr --> - The design document has been reviewed and approved by Radius maintainers/approvers. - [ ] Yes <!-- TaskRadio design-review --> - [x] Not applicable <!-- TaskRadio design-review --> - A PR for the [samples repository](https://github.com/radius- A PR fosamples) is created, if existing samples are affected by the changes in this PR. - [ ] Yes <!-- TaskRadio samples-pr --> - [x] Not applicable <!-- TaskRadio samples-pr --> - A PR for the [documentation repository](https://github.com/radius-project/docs) is created, if the change- A PR for the [documentation repository](https://gacing updates are made. - [ ] Yes <!-- TaskRadio docs-pr --> - [x] Not applicable <!-- TaskRadio docs-pr --> - A PR for the [recipes repository](https://github.com/radius-project/recipes) is created, if existing recipes are affected by the changes in this PR. - [ ] Yes <!-- TaskRadio recipes-pr --> - [x] Not applicable <!-- TaskRadio recipes-pr --> Signed-off-by: Will Tsai <28876888+willtsai@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This pull request modernizes the development environment, updates dependencies, and improves configuration and documentation for the project. The main themes are upgrading Node.js and Yarn versions, aligning development and CI environments, updating dependency versions, and refining documentation and configuration for maintainability and consistency.
These changes collectively bring the project up to date with the latest Node.js and Yarn releases, streamline developer onboarding, and ensure consistency across development, CI, and production environments.
Type of change
Issue: #183
Screenshots