Move releases to NextByte infrastructure - #3
Merged
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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.
TL;DR
Moves OpenUsage onto a clean NextByte-owned release path, modeled after MX Master Input: NextByte signing, App Store Connect API-key notarization, a fresh Sparkle key/feed, fork-owned URLs and identifiers, and SHA-pinned Actions. It also removes inherited Labeler/Stale automation and all upstream release/telemetry carry-forward.
What was happening
gh-pagesbranch contained upstream appcast/pricing content.openusageHomebrew cask installs the upstreamrobinebers/openusagebuild, not this NextByte fork.appcast.xmlcould not be rerun once a pricing-onlygh-pagesbranch existed.What this changes
8KZBNZJBAX,com.mattstallone.openusage, and matching production/development iCloud containers.latest.jsoncarry-forward, PostHog dSYM upload, and the upstream baked telemetry token.mstallone/openusage.Heads-up
mstallone/openusage. The production Developer ID iCloud profile was validated against NextByte team8KZBNZJBAX, bundle IDcom.mattstallone.openusage, containeriCloud.com.mattstallone.openusage, and the certificate embedded in the release.p12.Tests
swift test— 1,367 passed, 4 skipped, 0 failed.#2and inherited upstream PRs#1030and#1031../script/build_and_run.sh verify— built, signed with NextByte team8KZBNZJBAX, and launched.codesign --verify --deep --strict --verbose=2 dist/OpenUsage.app.bash -non changed release/build/profile scripts; linted both entitlement plists; rangit diff --check.