fix(release): repair product download metadata#6
Merged
Merged
Conversation
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
download.genmeta.netto the live R2 public domaindownload.dhttp.netmain,contrib, andnon-freecomponentsRelease recovery context
The first
v0.6.0product tag run uploaded objects successfully, but the generated Homebrew/Scoop metadata embeddeddownload.genmeta.netURLs. Those URLs currently return 404, while the uploaded objects are live underdownload.dhttp.net.The DEB release job also targeted the split
apt/gmutilsrepository. Users consume the existing unified repo athttps://download.dhttp.net/ppa/genmeta, so the release workflow must writeppa/genmetawith suite/codenamegenmetaand preserve the archive metadata shape expected by that source.Because the
v0.6.0archive objects already exist, a retag/rerun must refresh mutable formula/json/APT metadata without trying to overwrite same-version immutable archives. The versioned payload planner skips existing remote archive keys and renders metadata with the remote sha256 when a local rebuild differs. APT mutable metadata uploads are now conditional on the remote baseline so concurrent gmutils/pishoo publishing fails safely and can be rerun instead of silently overwriting the other index update.Verification
cargo +nightly fmtcargo +nightly fmt -- --checkgit diff --checkcargo test -p xtask publish::s3::deb::testscargo test -p xtaskDHTTP_ROOT_CA=/home/yiyue/code/reimu/keychain/root.crt DHTTP_STUN_SERVER=nat.genmeta.net:20004 DHTTP_H3_DNS_SERVER=https://dns.genmeta.net:4433 DHTTP_HTTP_DNS_SERVER=https://dns.genmeta.net DHTTP_MDNS_SERVICE=_genmeta.local DHTTP_CERT_SERVER_URL=https://license.genmeta.net cargo clippy --all-targets --all-features -- -D warningsDHTTP_ROOT_CA=/home/yiyue/code/reimu/keychain/root.crt DHTTP_STUN_SERVER=nat.genmeta.net:20004 DHTTP_H3_DNS_SERVER=https://dns.genmeta.net:4433 DHTTP_HTTP_DNS_SERVER=https://dns.genmeta.net DHTTP_MDNS_SERVICE=_genmeta.local DHTTP_CERT_SERVER_URL=https://license.genmeta.net cargo test --all-targets --all-featuresNote: clippy/test still emit the pre-existing future-incompatibility warning for
proc-macro-error2 v2.0.1, but both commands exit successfully.