pfSense

If the config is pointing to a nonexistent update branch it uses a default branch which is generally the current stable version. Once the configured branch becomes available again then it will be used. This is an issue in the following case since it results in undesired behavior:

1. The system is updated to a development branch.
2. The system is updated to the RELEASE version once its available.
3. A development branch is made available.

The above steps result in the system using the (new) development branch, e.g. for updating packages or for the widget update checks, without the user first opting into the development branch (by selecting it under System > Update).

By updating the configured branch once a system update is confirmed, the above steps will result in the system continuing to use the (e.g.) stable release branch while allowing the user to opt into the (new) development branch.