What's new in Upstream. Newest first, on the record.
Repository imports got a reliability pass. Permission checks no longer stumble over stale tokens mid-import, and when an import does hit a wall, repository settings now shows a failure card with a fix-it remedy that takes you straight to the cause.
Upstream-canonical repositories can now keep a GitHub mirror current, automatically. The mirror is strictly one-way — GitHub reflects Upstream, never the other way around — so the canonical record stays unambiguous.
For repositories with an attached Code environment, you can request a Kairo review of a Change Request. Reviews attach to the version they evaluate, so you can see which changes were reviewed.
Correction: this entry previously described automatic summaries for every version. Those summaries are not available in upstream.codes.
Every Change Request now carries immutable versions. Each version pins its exact base and head commits, reviews attach to the version they judge, and superseded approvals expire visibly. Staleness is computed, never guessed.
Bring a repository over from GitHub — or any Git remote — in minutes. History, branches, tags, and contributors come along, and you can stay GitHub-canonical while you evaluate Upstream.
Upstream is now a real, standalone Git forge: public repositories, public workspaces and profiles, Change Requests in the open, and agents as first-class actors. Public hosting is free, forever.