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.

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

Update dependency org.scalameta:munit to v1.0.0-M11 #7

Merged
merged 1 commit into from
Mar 21, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 21, 2024

Mend Renovate

This PR contains the following updates:

Package Type Update Change
org.scalameta:munit Test patch 1.0.0-M3 -> 1.0.0-M11

Release Notes

scalameta/munit (org.scalameta:munit)

v1.0.0-M11

Compare Source

⚠️ Breaking Changes ⚠️

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:

  MySuite.beforeAll()
  myFixture.beforeAll()
  MySuite.beforeEach(test-1)
  myFixture.beforeEach(test-1)
  myFixture.afterEach(test-1)
  MySuite.afterEach(test-1)
  myFixture.afterAll()
  MySuite.afterAll()
Click to see this vizualized as a diff
-- v1.0.0-M1 - v1.0.0-M10 order
++ v0.7.x / +v1.0.0-M11 order
  MySuite.beforeAll()
  myFixture.beforeAll()
  MySuite.beforeEach(test-1)
  myFixture.beforeEach(test-1)
- MySuite.afterEach(test-1)
  myFixture.afterEach(test-1)
+ MySuite.afterEach(test-1)
- MySuite.afterAll()
  myFixture.afterAll()
+ MySuite.afterAll()
Customizing the ordering of beforeAll / afterAll methods

If 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

What'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

Full Changelog: scalameta/munit@v1.0.0-M9...v1.0.0-M10

v1.0.0-M9

Compare Source

Notable Changes

All Changes

New Contributors

Full Changelog: scalameta/munit@v1.0.0-M8...v1.0.0-M9

v1.0.0-M8

Compare Source

Notable Changes

All 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

New 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

Full 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.


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

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

@robstoll robstoll merged commit 61ab074 into main Mar 21, 2024
2 checks passed
@renovate renovate bot deleted the renovate/org.scalameta-munit-1.x branch March 21, 2024 16:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant