18-May-2026 — safer environment settings and more reliable contributor bundles ref #217

build 648commit 1cd138a


This release fixes two problems in the platform administration tools.

The first problem was that saving the environment settings page could accidentally lose hidden configuration values. The form showed the main settings correctly, but when it saved them back it rebuilt the configuration too narrowly. Some fields that were not visible on the form could be dropped. One of those fields is used by the deployment pipeline, so losing it could break the next build.

That has now been fixed. Saving environment settings now preserves the whole existing configuration and only changes the fields the form is meant to edit.

Contributor environment generation

The second fix is for the Contributor Environment tool.

This tool lets a site admin create a downloadable development bundle for a group. The bundle gives a contributor, developer, or coding assistant a realistic local environment to work in, with live reload and group-specific data, without giving them access to the central staging configuration.

That matters because it lowers the barrier to making useful changes to NGX. Someone can ask for help building or testing a feature in a real group context without first understanding every part of the NGX stack.

What changed

Why this matters

Before this fix, the contributor bundle flow could get stuck before it started, or fail with a message that did not explain what to do next. That made the feature feel unreliable just when someone was trying to set up help.

After this fix, a site admin can generate a contributor bundle more confidently, and the person receiving it can get to the useful part faster: making changes in a live-reloadable NGX environment that behaves like the group site they are working on.