[examples] Unable to include 2.0.0 dependency with version number

[everyplace]

Expected behavior

In the examples, version 2.0.0 of the library is suggested to be included as a dependency, for example in the ApiGateway example. As of the date of this issue, this version does not yet exist, as the latest is currently 2.0.0-rc1. Using this non-semver identifier hasn't worked for me though, so I've had to use a revision to get the dependency to build correctly:

dependencies[
        // Use the hash that corresponds to 2.0.0-rc1
        .package(url: "https://github.com/swift-server/swift-aws-lambda-runtime.git", revision: "a1ab8df"),
]

I'm sure this is just a bad timing issue on my part, as the release notes for rc1 suggest that it will be the one released, but thought I should at least post the workaround in case others run into this issue.

Actual behavior

dependencies[
        // Use the from parameter
        .package(url: "https://github.com/swift-server/swift-aws-lambda-runtime.git", from: "2.0.0"),
]

Steps to reproduce

1. Include the library with `from: "2.0.0"
2. Attempt to build the library

If possible, minimal yet complete reproducer code (or URL to code)

// swift-tools-version:6.2

// From https://github.com/swift-server/swift-aws-lambda-runtime/blob/main/Examples/APIGateway/Package.swift

import PackageDescription

// needed for CI to test the local version of the library
import struct Foundation.URL

let package = Package(
    name: "swift-aws-lambda-runtime-example",
    platforms: [.macOS(.v15)],
    products: [
        .executable(name: "APIGatewayLambda", targets: ["APIGatewayLambda"])
    ],
    dependencies: [
        // during CI, the dependency on local version of swift-aws-lambda-runtime is added dynamically below
        .package(url: "https://github.com/swift-server/swift-aws-lambda-runtime.git", from: "2.0.0"),
        .package(url: "https://github.com/swift-server/swift-aws-lambda-events.git", from: "1.0.0"),
    ],
    targets: [
        .executableTarget(
            name: "APIGatewayLambda",
            dependencies: [
                .product(name: "AWSLambdaRuntime", package: "swift-aws-lambda-runtime"),
                .product(name: "AWSLambdaEvents", package: "swift-aws-lambda-events"),
            ],
            path: "Sources"
        )
    ]
)

What version of this project (swift-aws-lambda-runtime) are you using?

2.0.0-rc1

Swift version

swift-driver version: 1.127.14.1 Apple Swift version 6.2 (swiftlang-6.2.0.19.9 clang-1700.3.19.1)
Target: arm64-apple-macosx26.0
Darwin studio-26.local 25.0.0 Darwin Kernel Version 25.0.0: Mon Aug 25 21:16:39 PDT 2025; root:xnu-12377.1.9~3/RELEASE_ARM64_T6031 arm64

Amazon Linux 2 docker image version

No response

[sebsto]

Hello Erin,

Thank you for reporting this. I'm the one responsible for this. I decided to "upgrade" all examples to "2.0.0" in advance of the 2.0.0 release in a couple of days. We want to minimize the number of changes on the repo in the next couple of days, this is why we did this.

I have to admit I was hoping no one would notice.

The 2.0.0 release will be tagged at the start of next week (unless a critical issue is being reported on rc.1) and this will fix the issue you described.

In the meantime, the workaround, as you described it, is to change the version number in the examples Package.swift from 2.0.0 to 2.0.0-rc.1.

Again, all my apologies for the inconvenience. This is temporary for a couple of days.

[everyplace]

Totally understand, and appreciate the reply! And yes, since my filing included the workaround this was never a big issue, but I was mostly posting in case anyone else ran into it.

Re: using 2.0.0-rc1, I did attempt to do that first, but from: still didn't work, hence my revision: approach. Are you 100% sure from: can handle the -rc1 suffix?

[everyplace]

If it helps, 2.0.0 is working great for me!? I even had to work through an Api example (instead of the provided HttpApi ones) and it worked great. I may submit a PR proposing adding one of these for future reference.

[sebsto]

Are you 100% sure from: can handle the -rc1 suffix

Not at all :-)

I even had to work through an Api example (instead of the provided HttpApi ones) and it worked great. I may submit a PR proposing adding one of these for future reference.

yes please do so!
Are you referring to the API Gateway V1 ?

Before sending your PR, pay attention to the typical CI failures:

• swift format
• license header checks
• yaml lint

Also make sure there is a README :-)
Happy to help or to answer any questions you might have.

Thank you !

[everyplace]

@sebsto Thank you for the encouragement re: the forthcoming example. Yes, I'm referring to an example that in the template uses something like:

Events:
  Endpoint:
    Type: Api # As opposed to the default HttpApi in the rest of the examples
    Properties:
      Path: /
      Method: GET

And then in the main.swift using APIGatewayRequest and APIGatewayResponse instead of their V2 counterparts, for those times when you need more granularity or control.

I look forward to switching from revision: to from: next week!

[everyplace]

While #569 does not address this issue, it does address my above comments re: wanting an APIGateway (V1) example.

[sebsto]

v2.0.0 is officially released
https://github.com/swift-server/swift-aws-lambda-runtime/releases