Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: apple/swift-container-plugin
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 1.1.2
Choose a base ref
...
head repository: apple/swift-container-plugin
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 1.2.0
Choose a head ref
  • 3 commits
  • 8 files changed
  • 2 contributors

Commits on Jan 7, 2026

  1. Bump the static linux SDK to make CI work again (#170) 

    Motivation
----------

CI is broken in #169 due to Swift 6.2.3 being used with a 6.2.0 Static
Linux SDK

Modifications
-------------

Bump the static linux SDK to 6.2.3

Result
------

CI should work.

Test Plan
---------

Let's wait for GHA
    @Joannis
    Joannis authored Jan 7, 2026
    Configuration menu
    Copy the full SHA
    b9fd555 View commit details
    Browse the repository at this point in the history

  2. Allow specifying a custom entrypoint & resources (#169) 

    Motivation
----------

This should allow users to add a debugserver and launch it.

Modifications
-------------

- Added a `--resources` flag that points to custom artifacts
- Added an option for a custom entrypoint

Result
------

You can add and run a debug server.

Test Plan
---------

Currently undergoing manual testing.

**Update:** Success
    @Joannis
    Joannis authored Jan 7, 2026
    Configuration menu
    Copy the full SHA
    e10069f View commit details
    Browse the repository at this point in the history

  3. Fix --tag parameter to properly push tags and update latest (#168) 

    Fix --tag parameter to properly push tags and update latest

Motivation
----------

The --tag parameter was accepted by containertool but had no effect on
the
actual tags pushed to the registry. When running:

swift package build-container-image --repository ghcr.io/org/image --tag
v1.0.0

The image was only pushed to `ghcr.io/org/image:latest` (the default
reference
from --repository), while the output misleadingly reported
`ghcr.io/org/image:v1.0.0`.

This made it impossible to publish versioned releases using the --tag
flag.

Modifications
-------------

- Collect all tags to publish: the --tag value (if provided) plus the
default
reference from --repository (typically 'latest')
- Push the manifest and index to each tag in the collection
- Skip duplicate pushes when --tag matches the repository reference
- Return the --tag reference (if provided) as the primary result

Result
------

When --tag is provided, the image is pushed to both the specified tag
AND the
default reference:

  --tag v1.0.0  →  pushes to v1.0.0 and latest
  --tag latest  →  pushes to latest (once, no duplicate)
  (no --tag)    →  pushes to latest (existing behavior)

Test Plan
---------

1. Build with --tag flag: `swift package build-container-image
--repository ghcr.io/org/image --tag v1.0.0`
2. Verify both tags exist: `docker pull ghcr.io/org/image:v1.0.0` and
`docker pull ghcr.io/org/image:latest`
3. Build with --tag latest: verify no errors and single push
4. Build without --tag: verify existing behavior unchanged
    @the-braveknight
    the-braveknight authored Jan 7, 2026
    Configuration menu
    Copy the full SHA
    197fb15 View commit details
    Browse the repository at this point in the history
Loading