Skip to content

4.3.0

Latest

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.