Repository navigation
chore(desktop): release canary 0.0.14 - #130
Merged
Merged
Conversation
This branch was successfully 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.
Bumps the desktop version from 0.0.13 to 0.0.14, so Sparkle offers a new canary built from current
main(ea0e6f6) plus this bump. Nate asked for this release.Included since 0.0.13:
Validation:
bun typesandbun run cipass on this lane. The signed Desktop release workflow with publishing enabled is queued on 7f767cb: https://github.com/githubnext/ace2/actions/runs/37374082858. It notarizes the app and DMG and verifies the public download bytes before publishing the signed canary feed.Built in Ace
An Ace channel (canary-release) did all Git and GitHub work, checks, and the release dispatch through its shell tool. No other tools were used. Workaround: the
lanetool created the lane from the project checkout's stalefeat/github-cacheHEAD, so the agent reset the lane toorigin/main(#96).