Skip to content

Releases

4.3.0

Choose a tag to compare

@github-actions github-actions released this 18 Nov 02:13

Added

  • github-release, swiftpm-cask-release, macos-cask-release,
    claude-plugin-release, swift-package-ci, ios-ci,
    claude-plugin-ci, vapor-ci: an optional last step that asks
    armcknight/mcknight.io to refresh its projects page, with a
    repository_dispatch of event_type: release-published. The release
    workflows send it after the release is published; the CI workflows send it
    from a new notify-site job, only on a push to the default branch, never
    under pull_request. It runs only with the new optional SITE_DISPATCH_TOKEN
    secret, which the caller passes with secrets: inherit or by name; without
    it the step does nothing, so no caller change is needed. The script is
    scripts/site/notify.sh. In ios-ci, the Authorize job now skips a
    push, which it could never pass, so a push runs only the notification.
  • github-release: the optional major-alias input. Set it to true to
    move the major alias tag that callers pin (2 for the tag 2.1.0, v1 for
    v1.2.3) to the tag after a final release. It never moves for a release
    candidate, refuses a tag the default branch does not contain, and leaves the
    alias alone when a newer final release of the same major exists. The work is
    in scripts/release/move-major-alias.sh. No caller change is needed: the
    input is off by default.
  • This repository's own release.yml now calls github-release.yml with
    major-alias: true in place of its copy of the two jobs, so every release
    here goes through the shared workflow.

Changed

  • ios-ci, ota-refresh, ota-cleanup, macos-cask-release,
    swiftpm-cask-release, github-release, claude-plugin-release: the
    work their steps did in run: blocks is now in the scripts in
    scripts/staging/, scripts/xcode/, scripts/signing/ and
    scripts/release/, as for vapor-ci and fly-deploy. The steps check the
    scripts out at the workflow's commit and only set their variables, so the
    same operations run on a workstation or on a different CI provider. Every
    reusable workflow, vapor-ci and fly-deploy too, checks the scripts out with
    one step, the new scripts composite action. No caller change is needed.
    The changes in behavior:
    • ios-ci: the Stage job fails with a named error when MATCH_DEPLOY_KEY
      is empty, in place of a later match failure.
    • macos-cask-release: the cask bump authenticates its push with a
      credential helper, as swiftpm-cask-release does, so the tap token is no
      longer written into the clone's .git/config.
    • swiftpm-cask-release: with sign: true, the release fails when the
      certificate match fetches belongs to a team other than team-id, as
      macos-cask-release already does.
  • ios-ci, swift-package-ci: scripts/ios/ui-screenshots.sh has a
    run subcommand and scripts/swift-package/cli-examples.sh a build
    subcommand, for the steps that ran the UI tests and built the product
    inline.
  • swift-package-ci: the Python that reads the commands from a PR
    description's cli-examples marker is now its own file,
    scripts/swift-package/cli-examples-commands.py, not inline in
    cli-examples.sh. No change in behavior.
  • ci: make lint and the ci workflow also shellcheck the scripts in
    .github/actions/.

Fixed

  • ios-ci, ota-refresh, swift-package-ci: run the stale-comments,
    build-expiry, ui-screenshots and cli-examples scripts at the commit of
    the workflow, not at main. They are now in scripts/ (pr/, staging/,
    ios/ and swift-package/), and each job checks them out at
    job.workflow_sha; scripts/staging/publish.sh and refresh.sh call them
    there, not on PATH. Before, the jobs used them through composite actions
    pinned to @main, so a caller pinned to a tag ran an older workflow with the
    newest scripts, and a change to a script's interface on main could break
    it. No caller change.
  • swiftpm-cask-release: the README now names the signing inputs and secrets
    the workflow reads — match-git-url, team-id, bundle-id,
    MATCH_PASSWORD and MATCH_DEPLOY_KEY — in place of
    DEVELOPER_ID_P12_BASE64 and DEVELOPER_ID_P12_PASSWORD, and lists the
    submodules input. Docs only; the workflow does not change.
  • claude-plugin-ci, claude-plugin-release: pass plugin-path,
    marketplace-path and changelog to run: steps through env:, not as
    inline ${{ inputs.* }} expressions. Before, a value with a quote or $( in
    it ran as shell.

Deprecated

  • The stale-comments, build-expiry, ui-screenshots and cli-examples
    composite actions in .github/actions/. Workflows of 4.2.0 and earlier use
    them at @main, so they stay, and run the scripts in scripts/. They go in
    the next major version: move a pin of 4.2.0 or earlier to this release before
    then.

4.2.0

Choose a tag to compare

@github-actions github-actions released this 18 Oct 19:30

Added

  • vapor-ci: a new workflow for Vapor servers. It builds and tests the
    package on Linux, in the swift image the server's Dockerfile builds in, and
    builds the Docker image without pushing it. swift-package-ci.yml stays the
    macOS build for packages.
  • fly-deploy: a new workflow that deploys a Fly app from the tip of the
    default branch with --build-arg GIT_SHA=<commit>, then waits until the
    health check answers with that commit. deploy-on: manual (the default)
    deploys only on workflow_dispatch; merge also deploys on each push to the
    default branch. It refuses a commit that is not the branch's tip. It needs the
    FLY_API_TOKEN secret, a deploy token for the app.
  • scripts/: the shell scripts that vapor-ci.yml and fly-deploy.yml
    run, in scripts/vapor/ and scripts/fly/. They have no dependency on
    GitHub Actions, so they also run locally or on a different CI provider. The
    workflows check them out at their own commit. make lint and the ci
    workflow shellcheck them, and a change to them needs a changelog entry, as a
    change to .github/ does.
  • ios-ci, vapor-ci, fly-deploy: an optional working-directory
    input, default ., for a repository that keeps each component in its own
    directory, such as ios/ and server/. Every step that runs in the
    repository runs there, and paths such as the IPA, the test report, the
    Dockerfile and fly.toml are relative to it. In ios-ci,
    ui-screenshots-path is relative to it too. The default keeps today's
    behaviour.

4.1.0

Choose a tag to compare

@github-actions github-actions released this 16 Oct 22:35

Added

  • swiftpm-cask-release: rewrites the cask's binary lines from the
    binaries input on every release, so the cask always links what the archive
    holds. Before, only version and sha256 moved, and a new executable stayed
    unlinked until someone edited the tap by hand. The cask must already have at
    least one binary line; a cask with none fails the release with an error.

4.0.0

Choose a tag to compare

@github-actions github-actions released this 12 Oct 22:05

Changed

  • ios-ci, ota-refresh: the command for a new staging build is
    /build-staging, not /staging-build, so it agrees with /refresh-staging.
    The comments these workflows post name the new command.

  • ios-ci, ota-refresh: the workflows check the command text
    themselves, so a caller no longer gates its issue_comment trigger. A
    command rename is then a change in this repo only. Each check is a job-level
    if:, so any other comment skips the jobs before a runner starts. The
    commenter's author_association is checked in the jobs, as before.

  • ios-ci: a new optional rebuild input. The refresh caller's rebuild job
    sets it, so that a /refresh-staging comment can start the build of an
    expired staging build.

  • stale-comments: /build-staging comments are hidden as answered. Old
    /staging-build comments are hidden too.

    Caller migration

    In .github/workflows/staging-build.yml, delete the if: of the stage
    job. In .github/workflows/refresh-staging-link.yml, delete the if: of the
    refresh job, and if it has a rebuild job, add rebuild: true to that
    job's with:. Then move the ios-ci.yml and ota-refresh.yml pins to @4.
    See the README's caller examples.

Fixed

  • ios-ci: when the Stage job could not look up the PR's head branch, for
    example because of a network error, it checked out and staged the default
    branch, and the install link named the default branch's commit. It now tries
    the lookup three times, then fails.

3.1.0

Choose a tag to compare

@github-actions github-actions released this 12 Oct 05:36

Added

  • swift-package-ci: a new optional cli-examples-product input turns on a
    cli-examples job under pull_request. It runs the commands that a
    <!-- cli-examples: … --> marker in the PR description names, on the base
    branch and on the PR, and comments a diff of their output on the PR. The
    caller must grant pull-requests: write for the comment.
  • stale-comments: a new cli kind for the cli-examples comment, so only
    the newest one stays visible.

3.0.0

Choose a tag to compare

@github-actions github-actions released this 09 Oct 01:13

Changed

  • ios-ci: a staging build is on demand. Under pull_request the workflow
    runs only the tests and the UI screenshots; the Stage job runs only when the
    caller sets pr-number from another event, such as a /staging-build PR
    comment. A new Authorize job runs first in that case, before any job checks
    out the PR's code: it refuses a commenter who cannot write to the repo, a
    missing pr-number, and a PR that is closed or from a fork, and it reacts to
    the comment. The install-link comment names /staging-build for a new build.

  • ota-refresh: when the build is missing, the comment tells you to comment
    /staging-build, not to push a new commit.

  • stale-comments: /staging-build comments are hidden as answered, the
    same as /refresh-staging comments.

    Caller migration

    iOS apps that want staging builds: add .github/workflows/staging-build.yml
    from the README's caller examples, with the same ipa-name and arkana-keys
    as ci.yml, and move the ios-ci.yml pins to @3. ci.yml needs no edit.

2.2.0

Choose a tag to compare

@github-actions github-actions released this 08 Oct 22:12

Added

  • 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.

2.1.0

Choose a tag to compare

@github-actions github-actions released this 11 Aug 02:48

Added

  • github-release: a new reusable workflow that publishes a GitHub release
    from the tagged changelog section, optionally attaching files. For repos with
    nothing to build, sign or upload, where tagging is the release — a SwiftPM
    library resolved from the tag, or a Spoon repo installed off the branch.
    armcknight/swift-armcknight and armcknight/hammerspoons had each grown a
    near-identical copy of this; both now call it.

    Every input is optional: changelog, assets, prerelease, runs-on. A tag
    with a prerelease suffix is marked a prerelease regardless of the input. The
    workflow runs no caller-supplied commands — a caller gating the release on a
    check puts it in its own job and depends on it with needs:.

2.0.0

Choose a tag to compare

@github-actions github-actions released this 10 Aug 14:34

Added

  • swiftpm-cask-release: a bundle-id input, passed to fastlane match as
    app_identifier. match requires it even for a developer_id fetch with
    skip_provisioning_profiles — without it signing aborted with "No value found
    for 'app_identifier'". It is unused for the team-wide Developer ID certificate,
    but the caller supplies its own value so the workflow carries no identity.

    Caller migration

    Only callers that set sign: true: add a bundle-id input (e.g.
    bundle-id: com.example.<tool>).

1.2.0

Choose a tag to compare

@github-actions github-actions released this 10 Aug 13:06

Added

  • swift-package-ci and swiftpm-cask-release: a submodules input,
    passed straight to actions/checkout. A package whose dependencies are
    vendored as git submodules (path-based SwiftPM deps) sets submodules: recursive so the build can see them; the default (empty) is unchanged, so
    existing callers are unaffected.