Update dependency org.scalameta:munit to v1.0.0-M11 #7
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.0.0-M3
->1.0.0-M11
Release Notes
scalameta/munit (org.scalameta:munit)
v1.0.0-M11
Compare Source
This release restores the fixture ordering to match that of the v0.7.x release line.
The ordering was originally changed in v1.0.0-M1, and has been a source of confusion.
Going forward the order will be:
Click to see this vizualized as a diff
Customizing the ordering of
beforeAll
/afterAll
methodsIf you require the previous (v1.0.0-M1 - v1.0.0-M10) ordering, you can restore it by separating your fixture into two fixtures, a "before fixture" and "after fixture" and then specify them in an override of
munitFixtures
. If fact, this is exactly how the v0.7.x style ordering was restored in https://github.com/scalameta/munit/pull/724.A documented example should be available in the near future (https://github.com/scalameta/munit/issues/739)
Notable Changes
assertNotEquals
failure message by @ekans in https://github.com/scalameta/munit/pull/728What's Changed
New Contributors
Full Changelog: scalameta/munit@v1.0.0-M10...v1.0.0-M11
v1.0.0-M10
Compare Source
This release fixes async tests on Scala Native when overriding the
munitExecutionContext
.See issue https://github.com/scalameta/munit/issues/695 for more details.
What's Changed
scalanative.runtime.loop()
invocation to correct place by @armanbilge in https://github.com/scalameta/munit/pull/700Full Changelog: scalameta/munit@v1.0.0-M9...v1.0.0-M10
v1.0.0-M9
Compare Source
Notable Changes
All Changes
scalanative.runtime.loop()
by @armanbilge in https://github.com/scalameta/munit/pull/693New Contributors
Full Changelog: scalameta/munit@v1.0.0-M8...v1.0.0-M9
v1.0.0-M8
Compare Source
Notable Changes
Printer
more easily configurable in https://github.com/scalameta/munit/pull/640assume(false)
handling in https://github.com/scalameta/munit/pull/629All Changes
New Contributors
Full Changelog: scalameta/munit@v1.0.0-M7...v1.0.0-M8
v1.0.0-M7
Compare Source
Notable Changes
All Changes
def
to overridescalaCheckInitialSeed
by @armanbilge in https://github.com/scalameta/munit/pull/564New Contributors
Full Changelog: scalameta/munit@v1.0.0-M6...v1.0.0-M7
v1.0.0-M6
Compare Source
What's Changed
Full Changelog: scalameta/munit@v1.0.0-M5...v1.0.0-M6
v1.0.0-M5
Compare Source
What's Changed
Full Changelog: scalameta/munit@v1.0.0-M4...v1.0.0-M5
v1.0.0-M4
Compare Source
What's Changed
getting-started.md
by @lolgab in https://github.com/scalameta/munit/pull/504munit.internal
by @armanbilge in https://github.com/scalameta/munit/pull/441assertEquals()
by @valencik in https://github.com/scalameta/munit/pull/521Full Changelog: scalameta/munit@v1.0.0-M3...v1.0.0-M4
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.
This PR has been generated by Mend Renovate. View repository job log here.