Changelog
QwenWorkChangelog 2.1.0
Release notes written for people who have to support the thing, not for a launch page. What changed, what it means for an existing install, and what to re-check.
2.1.0 - 2026-11-18
Packages
- All six installers rebuilt and republished. Sizes shift slightly with each build; the numbers on this site are the current ones.
- Windows ARM64 package shrank relative to 2.0.2 as unused runtime components were dropped.
- macOS Universal is not offered — the two dmgs remain separate, and the Intel build is still the larger of the two.
Signing and verification
- Hash values changed for every package, as they do with every release. Any note with a hash from before this build is now stale.
- The macOS builds continue to be notarised;
spctlshould still answersource=Notarized Developer ID. - Linux packages still ship without a detached GPG signature — hash comparison against the published value remains the practical check.
Workspace and account
- Switching between personal space and an organisation no longer requires a sign-out cycle.
- The active workspace is remembered per device, which means a shared machine may open in the previous user's workspace if they did not sign out.
- Join links now expire; an old invitation forwarded by email may no longer work.
Automation
- Event triggers cover ten types; the earlier build covered fewer.
- Rate limit is 200 runs per hour per workspace. Free workspaces can hold ten active tasks at once.
- Failures now report which step broke rather than a single generic error.
2.0.2 - 2026-11-12
A point release on top of 2.0.0. The visible change is stability in long sessions; the invisible one is a fix for a file lock that made in-place upgrades fail on Windows when the app was still running in the tray.
2.0.0 - 2026-11-09
The release that introduced the collaboration space and the automation layer, and moved the product from a single-user assistant to something a team can share. Everything after it has been refinement rather than a new surface.
Upgrade advice: if you pin versions for images, re-verify the hash before rolling out. The path did not change, the file behind it did — that is the whole trap of
/release/latest/.Full narrative version with context: release notes.