[GH-ISSUE #656] New Release #429

Closed
opened 2026-03-03 16:48:36 +03:00 by kerem · 8 comments
Owner

Originally created by @Nef10 on GitHub (May 15, 2021).
Original GitHub issue: https://github.com/OAuthSwift/OAuthSwift/issues/656

Originally assigned to: @phatblat on GitHub.

I just wanted to follow up on the comment in #649 on the next release, given that the ticket was closed.

@phatblat may I ask you for an update on the release plan?

The problem for me is that due to limitation of the Swift Package Manger, I see the warning which were introduced by Swift 5.4 and fixed in #650 in my packages. As I configure my build to treat warnings as errors, the build is failing now.

Originally created by @Nef10 on GitHub (May 15, 2021). Original GitHub issue: https://github.com/OAuthSwift/OAuthSwift/issues/656 Originally assigned to: @phatblat on GitHub. I just wanted to follow up on the comment in #649 on the next release, given that the ticket was closed. @phatblat may I ask you for an update on the release plan? The problem for me is that due to limitation of the Swift Package Manger, I see the warning which were introduced by Swift 5.4 and fixed in #650 in my packages. As I configure my build to treat warnings as errors, the build is failing now.
kerem 2026-03-03 16:48:36 +03:00
  • closed this issue
  • added the
    question
    label
Author
Owner

@phimage commented on GitHub (May 17, 2021):

in Swift Package Manger we could use temporary head/master branch code, isn't?

here I make a plan before release https://github.com/OAuthSwift/OAuthSwift/issues/649#issuecomment-828761986
to provide some info on what I see on change done since last tag/release
but phatblat could release when he want

<!-- gh-comment-id:842133524 --> @phimage commented on GitHub (May 17, 2021): in Swift Package Manger we could use temporary head/master branch code, isn't? here I make a plan before release https://github.com/OAuthSwift/OAuthSwift/issues/649#issuecomment-828761986 to provide some info on what I see on change done since last tag/release but phatblat could release when he want
Author
Owner

@phatblat commented on GitHub (May 17, 2021):

Sorry for the delay on this. Last week was crazy. I will work on getting 2.1.3 out today.

<!-- gh-comment-id:842648224 --> @phatblat commented on GitHub (May 17, 2021): Sorry for the delay on this. Last week was crazy. I will work on getting 2.1.3 out today.
Author
Owner

@phatblat commented on GitHub (May 17, 2021):

FYI, @Nef10 you can use code that's in the master branch before it's released using:

    dependencies: [
        .package(
            url: "https://github.com/OAuthSwift/OAuthSwift.git",
            .branch("master")
        ),
    ],

However, this can produce different behavior over time as new PRs are merged into master.

<!-- gh-comment-id:842710511 --> @phatblat commented on GitHub (May 17, 2021): FYI, @Nef10 you can use code that's in the `master` branch before it's released using: ```swift dependencies: [ .package( url: "https://github.com/OAuthSwift/OAuthSwift.git", .branch("master") ), ], ``` However, this can produce different behavior over time as new PRs are merged into master.
Author
Owner

@Nef10 commented on GitHub (May 18, 2021):

Hey, no worries, I just wanted to ask what the status is. :)

I know I can specify a branch or a specific commit in SPM, however this only works in the end consumer project. When you include a library via a branch or commit in another library, you won't be able to consume this library by specifying a version:

Note that packages which use branch-based dependency requirements
cannot be depended-upon by packages which use version-based dependency
requirements; you should remove branch-based dependency requirements
before publishing a version of your package.

from https://docs.swift.org/package-manager/PackageDescription/PackageDescription.html#package-dependency-requirement

To fix this one would need to use branch or commit dependency requirements in every library up to the last consumer.

<!-- gh-comment-id:842887192 --> @Nef10 commented on GitHub (May 18, 2021): Hey, no worries, I just wanted to ask what the status is. :) I know I can specify a branch or a specific commit in SPM, however this only works in the end consumer project. When you include a library via a branch or commit in another library, you won't be able to consume this library by specifying a version: > Note that packages which use branch-based dependency requirements cannot be depended-upon by packages which use version-based dependency requirements; you should remove branch-based dependency requirements before publishing a version of your package. from https://docs.swift.org/package-manager/PackageDescription/PackageDescription.html#package-dependency-requirement To fix this one would need to use branch or commit dependency requirements in every library up to the last consumer.
Author
Owner

@phimage commented on GitHub (May 18, 2021):

I just check CI and launch locally

%  xcodebuild -scheme "OAuthSwift" | xcpretty
▸ Processing Info.plist
▸ Compiling OAuth1Swift.swift
▸ Compiling OAuth2Swift.swift

❌  /Users/emarchand/Documents/GitHub/OAuthSwift/Sources/OAuth2Swift.swift:145:31: cannot find 'SFAuthenticationURLHandler' in scope

                              SFAuthenticationURLHandler.isCancelledError(domain: domain, code: code) {
                              ^~~~~~~~~~~~~~~~~~~~~~~~~~


** BUILD FAILED **

the code is a little crappy with all version and case, I suppose its issue is with target macCatalyst, in fact no sdk is passed in argument of build

I think in GitHub CI I will add compile on iOS and one one Mac catalyst ( + xcpretty)

https://github.com/OAuthSwift/OAuthSwift/pull/658

<!-- gh-comment-id:843111939 --> @phimage commented on GitHub (May 18, 2021): I just check CI and launch locally ``` % xcodebuild -scheme "OAuthSwift" | xcpretty ▸ Processing Info.plist ▸ Compiling OAuth1Swift.swift ▸ Compiling OAuth2Swift.swift ❌ /Users/emarchand/Documents/GitHub/OAuthSwift/Sources/OAuth2Swift.swift:145:31: cannot find 'SFAuthenticationURLHandler' in scope SFAuthenticationURLHandler.isCancelledError(domain: domain, code: code) { ^~~~~~~~~~~~~~~~~~~~~~~~~~ ** BUILD FAILED ** ``` the code is a little crappy with all version and case, I suppose its issue is with target macCatalyst, in fact no sdk is passed in argument of build I think in GitHub CI I will add compile on iOS and one one Mac catalyst ( + xcpretty) https://github.com/OAuthSwift/OAuthSwift/pull/658
Author
Owner

@phatblat commented on GitHub (May 20, 2021):

Version 2.2.0 is live now 🎉

<!-- gh-comment-id:845504116 --> @phatblat commented on GitHub (May 20, 2021): Version [2.2.0](https://github.com/OAuthSwift/OAuthSwift/releases/tag/2.2.0) is live now 🎉
Author
Owner

@phimage commented on GitHub (May 21, 2021):

thank you very much for the work done

<!-- gh-comment-id:845820169 --> @phimage commented on GitHub (May 21, 2021): thank you very much for the work done
Author
Owner

@Nef10 commented on GitHub (May 22, 2021):

Thanks!

<!-- gh-comment-id:846441138 --> @Nef10 commented on GitHub (May 22, 2021): Thanks!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/OAuthSwift#429
No description provided.