Repository navigation
chore(main): release 0.20.0 - #653
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
21 times, most recently
from
November 6, 2026 08:37
4b2411b to
d1f710f
Compare
github-actions
Bot
force-pushed
the
release-please--branches--main--components--openstorage
branch
7 times, most recently
from
November 6, 2026 13:39
db774df to
55f8e5f
Compare
github-actions
Bot
force-pushed
the
release-please--branches--main--components--openstorage
branch
28 times, most recently
from
November 9, 2026 09:48
540e1f1 to
0c9cfd0
Compare
github-actions
Bot
force-pushed
the
release-please--branches--main--components--openstorage
branch
from
November 9, 2026 15:55
0c9cfd0 to
1eff3cf
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.20.0 (2026-11-09)
⚠ BREAKING CHANGES
archiveanswers 422 for a repository that holds a symlink whose target is longer than 4,095 bytes, before any response byte, and the body names the symlink. Before, a target of 4,096 bytes up to about 1 MiB was in the archive, and a longer one cut the stream after its headers. To get the archive, pass the symlink inexclude_globs, or fetch the target with git.diff-commitanswers 400invalidfor a patch that gives a file a directory mode (new file mode 040000, or a mode change to040000). Before, such a patch answered 412no changes to commit, 409conflict, or 200 with a commit that lacked the file.diff-commitanswers 400invalidinstead of 409conflictfor a patch that only git refuses (.git./x,git~1/x, a.gitmodulessymlink,new mode 100664, a submodule patch without a commit or with a null commit). It answers 500 instead of 409 whengit apply --cachedfails for any other reason (a held index lock, a full disk, an unreadable index), and 500 instead of 400 when git fails while it parses the patch. A file name with a newline and afatal:line makes git's message look like a server fault, so the client's own 400 or 409 then answers 500. A patch that makes git abort and a header without a file name answer 400 instead of 500.forbiddeninstead of 401unauthorized. SDK 0.1.0 raisesPermissionDeniedErrorinstead ofAuthenticationErrorfor such a token. SDK 1.17.1 reports status 403 instead of 401, for exampleApiError.statusin TypeScript. A request without a Bearer token still gets 401.authentication_unavailableinstead of 401 (or instead of 403forbiddenfor a fork source token; the Git and LFS transports keep 401; during a key store outage a caller with any well-formed token sees this 403 instead of 401), and unmatched/api/paths answer problem bodies (404route_not_found, or 405method_not_allowedwithAllow) instead of ServeMux's plain text.resultenvelope. File conflicts answer 409 with upstream'sMergeConflictbody (error,conflict_type,conflict_paths,merge_base_sha), and every other merge failure answers the plain problem body. A non-fast-forwardff_onlymerge and a merge of unrelated histories answer 412precondition_failedinstead of 409. Note-write failures answer the plain problem body instead of the note envelope, except the 409 guard body. SDK 1.17.1 Go reads the note envelope only forapplication/json(util.go:154), so it now reports these note-write failures as a genericAPIErrorinstead of aRefUpdateError. I did not check the 1.17.1 TypeScript and Python clients.repository_not_found,branch_not_foundorref_not_found. SDK 1.17.1 Go reports these restore-commit failures asRefUpdateErrorwith status404(or the HTTP status) and a generic message, and builds the commit-pack and diff-commitRefUpdateErrorwith statusfailed. I did not check the 1.17.1 TypeScript and Python clients.RefUpdateErrorfrom that body withStatusfailedinstead ofunauthorized,forbidden,not_foundorunavailable. I did not check the 1.17.1 TypeScript and Python clients.expected_target_shaorexpected_head_shaoncommit-pack,diff-commitandrestore-commit, and a staleexpected_notes_ref_shaorexpected_ref_shaonPOST .../notesand theDELETE .../notesbody, now answer409withcode: ref_guard_failed,guard,current_shaandresult.status: conflict, instead of412precondition_failed. Go SDK 1.17.1 (code-storage-go) callers now get aRefUpdateErrorwith statusconflicton the three commit routes. On a note create they get anAPIErrorwith status 409 whose message is the raw body, because that SDK reads note bodies only forapplication/json. Go SDK 0.1.0 (github.com/pierrecomputer/sdk/go) callers get aRefGuardErroron every form.code,detail, ...) are now sent asContent-Type: application/problem+json, as upstream documents. SDK 1.17.1 Go and TypeScript clients parse error JSON only forapplication/json, so their error message becomes the raw body text and the parsed body becomes a string. SDK 0.1.0 and the 1.17.1 Python client are not affected.Features
Bug Fixes
Performance Improvements
This PR was generated with Release Please. See documentation.