Skip to content

Put the upgrade note back at the top of Unreleased #721

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
davidmckayv merged 1 commit into from
Oct 2, 2026
Merged

Put the upgrade note back at the top of Unreleased #721

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 12 additions & 12 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,18 @@ Newest first. `Unreleased` is what is on `main` and not yet tagged.

## Unreleased

**Before upgrading.** Four things change for an existing deployment:
- Automatic Learning is on unless an administrator saved it off. It does nothing until a Learning
container is assigned; see below.
- A Bot's computer refuses the network until the server pushes its policy. A computer run without
an API server can set `EGRESS_POLICY_REQUIRED=0` for the old behaviour.
- The upgrade runs migrations `0042_user_preferences`, `0043_plugin_logos`, `0044_voice_sessions`,
`0045_channel_activity_source`, `0046_automatic_learning`, `0047_agent_pinning`,
`0048_coworker_parity`, `0049_coworker_parity_lanes`, `0050_review_fixes` and
`0051_routine_enabled_at`.
- An existing Windows clone checks text files out with LF only after
`git rm -r --cached . && git reset --hard` on a clean tree.

### A request to the approvals API that is not JSON answers 400

A body that could not be parsed as JSON, sent to any approvals route that reads one, such as
Expand Down Expand Up @@ -44,18 +56,6 @@ accepted the same way. A zone id such as `fe80::1%eth0` was accepted too, and th
filter on the first connection that policy judged. Each is now refused when the rule is saved, with
the sentence a malformed range already got. A rule like this saved earlier matches nothing.

**Before upgrading.** Four things change for an existing deployment:
- Automatic Learning is on unless an administrator saved it off. It does nothing until a Learning
container is assigned; see below.
- A Bot's computer refuses the network until the server pushes its policy. A computer run without
an API server can set `EGRESS_POLICY_REQUIRED=0` for the old behaviour.
- The upgrade runs migrations `0042_user_preferences`, `0043_plugin_logos`, `0044_voice_sessions`,
`0045_channel_activity_source`, `0046_automatic_learning`, `0047_agent_pinning`,
`0048_coworker_parity`, `0049_coworker_parity_lanes`, `0050_review_fixes` and
`0051_routine_enabled_at`.
- An existing Windows clone checks text files out with LF only after
`git rm -r --cached . && git reset --hard` on a clean tree.

### Deleting a channel twice is recorded once

A second `DELETE` of the same channel, from a retry or a second tab, still answers 204 as before.
Expand Down
Loading