Repository navigation
chore(main): release 0.21.0 - #812
Open
github-actions[bot] wants to merge 1 commit into
Open
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
github-actions
Bot
force-pushed
the
release-please--branches--main--components--openstorage
branch
29 times, most recently
from
November 13, 2026 23:44
b9aa19c to
80a1092
Compare
github-actions
Bot
force-pushed
the
release-please--branches--main--components--openstorage
branch
28 times, most recently
from
November 16, 2026 17:53
8533a43 to
e15702a
Compare
github-actions
Bot
force-pushed
the
release-please--branches--main--components--openstorage
branch
from
November 16, 2026 18:14
e15702a to
c4cb479
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 I have created a release beep boop
0.21.0 (2026-11-16)
⚠ BREAKING CHANGES
POST /repos/mergewithsquash: trueand nocommit_messagenow answers 400 before any branch lookup, instead of the answer it got before (a squash commit with a default message,no_op, or an error such as 403, 404, 409 or 412). A merge commit withoutcommit_messagenow gets the messageMerge branch '<source>' into <target>instead ofMerge <source> into <target>./<repo>.gitno longer lists, fetches or accepts pushes torefs/namespaces/refs, the API's ephemeral branches included, and an import push through/<repo>+import.gitcannot write them either. Use the HTTP API for those branches. Delete unwanted refs that a push wrote underrefs/namespaces/before you upgrade: git cannot delete them afterwards.POST /reposnow refuses adefault_branchoutsiderefs/heads/with 400, asPATCH /repodoes.+importremote is push-only and an import push writes the repository's normal branches and tags. Clone and fetch through+importanswer 403, and a repository with a sync base refuses an import push. Before you upgrade, stop pushes to+import, then fetch every ref you pushed through+importwith the current version and push it to the normal remote of a repository without a sync base. The copy stores the objects a second time, so raise the pack quota first when they do not fit (docs/explanation/git-protocol-and-namespaces.md, "Upgrading from 0.20.0 or earlier"). Data under the old<repo_id>+importkey keeps counting against the repository's quota until the repository is deleted.Features
Bug Fixes
This PR was generated with Release Please. See documentation.