You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ota-refresh: after it posts the refreshed install link, hide the PR's
earlier install-link comments (the original "Staging build ready" from ios-ci and any prior refreshes) as outdated, so only the current link stays
visible. It also hides the /refresh-staging command comments and the
notices of earlier refreshes (a missing build, or an expired one being
rebuilt). Best-effort: a comment that cannot be hidden logs a warning and does
not fail the refresh. No caller change.
ota-refresh: when the PR has no build to re-sign (the bucket's lifecycle
rule deleted it, or an explicit run-id does not exist), comment the reason
and the way to get a new build on the PR, and write an ::error::
annotation, instead of failing with only a log line. An explicit run-id is
now checked before ota-publish runs. No caller change.
ota-refresh: new optional inputs rebuild-expired (default false) and retention-days (default 30), and a rebuild output. With rebuild-expired, a build older than retention-days that the bucket has
deleted sets rebuild instead of failing, so a caller job can run ios-ci.yml for the PR. See the README's refresh caller example.
ios-ci: new optional input pr-number, to build a PR's head from an event
other than pull_request. Unused under pull_request.
ios-ci: an optional ui-screenshots job, turned on by the new ui-screenshots-scheme and ui-screenshots-path inputs (with optional ui-screenshots-target and ui-screenshots-destination). Under pull_request it runs the UI test classes the PR adds or changes, plus any
test named in a <!-- ui-screenshots: … --> marker in the PR description,
on a simulator. It pushes the screenshots they attach to an orphan ui-screenshots branch and comments them on the PR, in a captioned table
per test. A caller that turns
it on must grant contents: write. Callers that leave it off are
unaffected.
ios-ci, ota-refresh: the install-link comment also says when the
build itself is deleted, as read from the staging bucket's lifecycle rule
(head-object on the build's metadata.json). The line is left out when no
rule applies. Shared through the new build-expiry composite action. No
caller change.
ios-ci: after the Stage job posts its install link, hide the PR's stale
comments the same way ota-refresh does. Both workflows share this through the
new stale-comments composite action. No caller change.
Fixed
ota-refresh: decide that a build exists by its metadata.json, not by
its run-* prefix. A refresh uploads manifest.plist and install.html
again, so after an earlier refresh the prefix outlives the build, and the
refresh failed inside ota-publish instead of explaining the missing build.
ios-ci: trust the armcknight/tools tap before brew bundle, which
Homebrew now refuses to load from an untrusted tap. A caller's Brewfile
must install the tools as a cask, cask 'armcknight/tools/tools': the tap no
longer has a formula of that name.