Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

chore(deps): update dependency quick/nimble to v12 - autoclosed #342

Closed
wants to merge 1 commit into from
Closed

chore(deps): update dependency quick/nimble to v12 - autoclosed #342

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 27, 2023 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Update Change
Quick/Nimble major 9.2.1 -> 12.3.0

Release Notes

Quick/Nimble (Quick/Nimble)

v12.3.0

Compare Source

Highlights

  • the async variant of toEventually no longer kicks off unstructured background tasks to check that the matcher matches. This means that there will no longer be the possibility that the same value will be being checked by multiples of the same matcher.

What's Changed

Full Changelog: Quick/Nimble@v12.2.0...v12.3.0

v12.2.0

Compare Source

Highlights

the equal matcher now supports arrays of tuples. For example:

expect([
    (1, 2),
    (3, 4)
]).to(equal([
    (1, 2),
    (3, 4)
]))

Thanks @​faroman for their contribution!

Automatically Generated Release Notes

What's Changed

New Contributors

Full Changelog: Quick/Nimble@v12.1.0...v12.2.0

v12.1.0: - AsyncPredicate

Compare Source

Highlights

  • You can now create Predicates that run in async contexts.

What's Changed

New Contributors

Full Changelog: Quick/Nimble@v12.0.1...v12.1.0

v12.0.1

Compare Source

What's Changed

Full Changelog: Quick/Nimble@v12.0.0...v12.0.1

v12.0.0

Compare Source

Nimble 12 adds the ability to using polling expectations with async expressions. Additionally, Nimble 12 includes a number of quality-of-life improvements and bug fixes.

What's Changed

New Contributors

Full Changelog: Quick/Nimble@v11.2.2...v12.0.0

v11.2.2

Compare Source

Highlights

Nimble v11.2.2 is a minor bug fix release which fixes the build on Xcode 14.3 and Wasm.

Thanks to @​dymv for fixing the Xcode 14.3 build and to @​ikesyo for fixing the wasm build!

Autogenerated Changelog

What's Changed

New Contributors

Full Changelog: Quick/Nimble@v11.2.1...v11.2.2

v11.2.1

Compare Source

Fixed tripping the main thread checker in async toEventually checks. Your CI should no longer report that tests erroneously crashed because the expression's debugDescription dared to reference something that needed to run on the main thread.

What's Changed

Full Changelog: Quick/Nimble@v11.2.0...v11.2.1

v11.2.0

Compare Source

Improved developer experience by allowing you to use the sync form of expect in a test that has other usage of async test. i.e. the following code compiles again:

class MyTest: XCTestCase {
    func testExample() {
        await someAsyncFunction()
        expect(someValue).to(equal(expectedValue))
    }
}

What's Changed

Full Changelog: Quick/Nimble@v11.1.1...v11.2.0

v11.1.1

Compare Source

What's Changed

Full Changelog: Quick/Nimble@v11.1.0...v11.1.1

v11.1.0

Compare Source

11.1.0 drops support for Swift 5.6 (you must use Xcode 14 or later). https://github.com/Quick/Nimble/pull/1009

11.1.0 fixes a developer experience bug where you could unknowingly use the sync version of toEventually in an async context, which will cause test timeout failures. https://github.com/Quick/Nimble/pull/1010

That is, the following test method (XCTest-style) would compile with no errors or warnings emitted, but fail at test runtime due to timeout issues. In v11.1.0, this now emits a warning that you're using the wrong version of toEventually (and similar).

@​MainActor func testSomething() async {
    expect(1).toEventually(equal(1)) // (in v11.0.0, this would not emit any kind of warning or error, but would definitely fail with a timeout error)
}

Full Changelog: Quick/Nimble@v11.0.0...v11.1.0

v11.0.0

Compare Source

This closes the v11.0.0 milestone.

Highlights

Primarily, this release now supports running tests in async contexts.

Fixed

New

Breaking

Auto-generated release notes

What's Changed

New Contributors

Full Changelog: Quick/Nimble@v10.0.0...v11.0.0

v10.0.0

Compare Source

This closes the v10.0.0 milestone.

Highlights

See additional details under the auto-generated release notes below.

Fixed

  • Various documentation improvements
  • Remove various deprecated APIs

New

  • Add toAlways, the inverse of toNever #​969
  • Add beWithin matcher #​886
  • Support nested optionals in beNil matcher #​894
  • Support operator overloads for beNil matcher #​893
  • Support throwAssertion matcher on SwiftPM on Linux #​891
  • Add support for tuples of up to 6 elements to equal matcher, as with the standard library #​880
  • Add matchers for Swift 5 Result type #​643

Breaking

  • Swift 5.4+
  • Xcode 12.5+
  • Remove old Matcher API #​876
  • Use FloatingPoint protocol in beCloseTo matcher #​879
  • passFunc of allPass matcher now takes S.Element over S.Element? #​895

Auto-generated release notes

What's Changed

New Contributors

Full Changelog: Quick/Nimble@v9.2.0...v10.0.0

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@techprimate-bot
Copy link

Warnings
⚠️ The Package.swift was updated, but there were no changes in TPPDF.podspec, Package.resolved. Did you forget to update them?

SwiftLint found issues

Severity File Reason
Warning Package.swift:16 There should be no space before and one after any comma. (comma)
Warning Package.swift:5 All declarations should specify Access Control Level keywords explicitly. (explicit_acl)
Warning Package.swift:12 Collection literals should not have trailing commas. (trailing_comma)
Warning Package.swift:16 Collection literals should not have trailing commas. (trailing_comma)
Warning Package.swift:25 Collection literals should not have trailing commas. (trailing_comma)
Warning Package.swift:32 Collection literals should not have trailing commas. (trailing_comma)
Warning Package.swift:33 Collection literals should not have trailing commas. (trailing_comma)

Generated by 🚫 Danger Swift against 609c5b9

@renovate renovate bot force-pushed the renovate/quick-nimble-12.x branch from 609c5b9 to 1d19785 Compare September 17, 2023 05:10
@techprimate-bot
Copy link

Warnings
⚠️ The Package.swift was updated, but there were no changes in TPPDF.podspec, Package.resolved. Did you forget to update them?

SwiftLint found issues

Severity File Reason
Warning Package.swift:16 There should be no space before and one after any comma. (comma)
Warning Package.swift:5 All declarations should specify Access Control Level keywords explicitly. (explicit_acl)
Warning Package.swift:12 Collection literals should not have trailing commas. (trailing_comma)
Warning Package.swift:16 Collection literals should not have trailing commas. (trailing_comma)
Warning Package.swift:25 Collection literals should not have trailing commas. (trailing_comma)
Warning Package.swift:32 Collection literals should not have trailing commas. (trailing_comma)
Warning Package.swift:33 Collection literals should not have trailing commas. (trailing_comma)

Generated by 🚫 Danger Swift against 1d19785

@renovate renovate bot changed the title chore(deps): update dependency quick/nimble to v12 chore(deps): update dependency quick/nimble to v12 - autoclosed Oct 10, 2023
@renovate renovate bot closed this Oct 10, 2023
@renovate renovate bot deleted the renovate/quick-nimble-12.x branch October 10, 2023 17:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@techprimate-bot