Repository navigation
ci(release): peel the release tag via the git refs API - #385
Merged
Merged
Conversation
Release run 48 failed with "ENOENT: lstat packaging/electron/libicuuc.77.dylib". Postgres.app's ICU libraries record bare install names (libicuuc.77.dylib), and the relinker passed them to realpathSync, which resolved them against the build step's working directory. Resolve a non-absolute dependency next to the image that records it, and fail with a clear message if it is not there.
Inspecting the pinned Postgres.app 2.9.6 DMG showed three more relink failures waiting behind the ICU one: - Every Mach-O is universal (x86_64 + arm64). otool prints one block per slice, so the parsers read the slice headers as dependencies and library ids. Thin each file to the build architecture first. - Six static archives are universal too, so `file` calls them Mach-O. They are link-time only; remove them. - The PL/Python modules link /Library/Frameworks/Python.framework, which the runner does not have and Vision does not use. Remove them and their extension scripts.
Release run 49 failed before publishing with "No commit found for SHA: tags/v2.0.0 (HTTP 422)": the commits API does not resolve tags/<name> for the annotated release tag. Resolve the tag through git/ref/tags and git/tags instead, in both places the publish step compares it with the verified commit.
EraPartner
enabled auto-merge (squash)
October 28, 2026 19:06
Coverage Report for backend
File CoverageNo changed files found. |
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.
Summary
Release run 49 built and attested the v2.0.0 artifacts, then failed in "Publish immutable-ready release" before publishing:
GET /repos/{owner}/{repo}/commits/tags/v2.0.0does not resolve the annotated release tag; I reproduced the same 422 locally. The publish step now resolves the tag throughgit/ref/tags/<tag>and peels annotated tag objects throughgit/tags/<sha>until it reaches the commit. This applies to both checks: the one before publication and the one after it.Testing
tag_commitfunction against the real repo withTAG=v2.0.0. It resolved tod35d0603317f32b03d42ff5cd707f44e300602eb, the commit Verify approved in run 49.After merge
Start Release with Run workflow from
mainandtag: v2.0.0. That run uses this fixed workflow, and the build still checks out the tagged commit. The v2.0.0 tag does not need to move.Generated by Claude Code