Skip to content

release-winget/release-homebrew: surface the opened PR's URL more prominently #807

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 2 commits into from
Oct 21, 2025
Merged

release-winget/release-homebrew: surface the opened PR's URL more prominently #807

merged 2 commits into from
Oct 21, 2025

Conversation

dscho
Copy link
Member

@dscho dscho commented Oct 20, 2025

By prefixing the line with ::notice::, the result will not only be printed in the (not very long retained) job logs, but also on the summary page of the workflow run.

@dscho
fixup! Adding winget workflows
9cfba65 
release-winget: surface the opened PR's URL more prominently

By prefixing the line with `::notice::`, the result will not only be
printed in the (not very long retained) job logs, but also on the
summary page of the workflow run.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
@dscho dscho requested a review from mjcheetham October 20, 2025 09:25
@dscho dscho self-assigned this Oct 20, 2025
@dscho
fixup! homebrew: add GitHub workflow to release Cask
b7d34aa 
release-homebrew: surface the opened PR's URL more prominently

By prefixing the line with `::notice::`, the result will not only be
printed in the (not very long retained) job logs, but also on the
summary page of the workflow run. This has been done in
mjcheetham/update-homebrew#20, the result of
which has been tagged as v1.5.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
@dscho dscho changed the title release-winget: surface the opened PR's URL more prominently release-winget/release-homebrew: surface the opened PR's URL more prominently Oct 20, 2025
@dscho
Copy link
Member Author

dscho commented Oct 20, 2025

The CI failures are all due to the current Amazon Web Services outage, I believe:

Initialize containers 15s
▷ Checking docker version
▷ Clean up resources from previous jobs
▷ Create local container network
▼ Starting job container
  /usr/bin/docker pull ubuntu:rolling
  Error response from daemon: Head "https://registry-1.docker.io/v2/library/ubuntu/manifests/rolling": received unexpected HTTP status: 503 Service Unavailable
  Warning: Docker pull failed with exit code 1, back off 8.82 seconds before retry.
  /usr/bin/docker pull ubuntu:rolling
  Error response from daemon: Head "https://registry-1.docker.io/v2/library/ubuntu/manifests/rolling": received unexpected HTTP status: 503 Service Unavailable
  Warning: Docker pull failed with exit code 1, back off 4.841 seconds before retry.
  /usr/bin/docker pull ubuntu:rolling
  Error response from daemon: Head "https://registry-1.docker.io/v2/library/ubuntu/manifests/rolling": received unexpected HTTP status: 502 Bad Gateway
  Error: Docker pull failed with exit code 1

@dscho dscho enabled auto-merge October 20, 2025 11:18
@dscho dscho merged commit 22fcb3e into vfs-2.51.1 Oct 21, 2025
230 of 236 checks passed
@dscho dscho deleted the surface-winget-pr-url-more-prominently branch October 21, 2025 15:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@derrickstolee derrickstolee derrickstolee approved these changes

@mjcheetham mjcheetham Awaiting requested review from mjcheetham

Assignees

@dscho dscho

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@dscho @derrickstolee