Skip to content

Update dependency org.scalameta:munit to v1.2.1 #37

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
Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update dependency org.scalameta:munit to v1.2.1 #37

wants to merge 1 commit into from

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Sep 4, 2023 •
edited
Loading

This PR contains the following updates:

Package Type Update Change
org.scalameta:munit Test minor 1.0.0-M6 -> 1.2.1

Release Notes

scalameta/munit (org.scalameta:munit)

v1.2.1

Compare Source

Pull Requests

v1.2.0

Compare Source

Pull Requests

v1.1.2

Compare Source

What's Changed

New Contributors

Full Changelog: scalameta/munit@v1.1.1...v1.2.0

v1.1.1

Compare Source

Pull Requests

v1.1.0

Compare Source

Important changes

These changes control output in case of assert failure and include minor API changes (only in rare cases of method overrides), hence minor version bump:

  • Add DiffOptions implicit parameter:
  • Diff: swap the order of expected-vs-obtained (#​875) @​kitbellew
    • previously, the actual results were shown in red (removed) and expected in green (added) which led to occasional cases of confusion with standard git diff output (which shows these changes in the "normal" way)

Miscellaneous

Build and dependency updates

v1.0.4

Compare Source

Notable Changes

Pull Requests

v1.0.3

Compare Source

Notable Changes

Pull Requests

v1.0.2

Compare Source

This release changes the Location to not include full path (instead a relative one independent of the machine), which while not a binary breaking change, it might still be relevant to a number of users.

Pull Requests

v1.0.1

Compare Source

Pull Requests

v1.0.0

Compare Source

https://scalameta.org/munit/blog/2024/05/22/release-1.0.0.html

v1.0.0-RC1

Compare Source

This is hopefully the last version before the real 1.0.0. That release will be accompanied by actual release notes that encompass all the changes done since 0.x series.

What's Changed

New Contributors

Full Changelog: scalameta/munit@v1.0.0-M12...v1.0.0-RC1

v1.0.0-M12

Compare Source

Pull Requests

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 #​724.

A documented example should be available in the near future (#​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 #​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

  • Fix Async tests on Scala Native #​693
  • Fail test suites on fatal exceptions #​669

All Changes

New Contributors

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

v1.0.0-M8

Compare Source

Notable Changes

  • Handle a StackOverflowError in addition to NonFatal errors in #​648
  • Use js-native folder by sbt-crossproject in #​646
  • Make Printer more easily configurable in #​640
  • Fix assume(false) handling in #​629

All Changes

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 was generated by Mend Renovate. View the repository job log.

@yegor256
Copy link
Member

yegor256 commented Sep 4, 2023

@rultor please, try to merge, since 5 checks have passed

@rultor
Copy link

rultor commented Sep 4, 2023

@rultor please, try to merge, since 5 checks have passed

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

@rultor
Copy link

rultor commented Sep 4, 2023

@rultor please, try to merge, since 5 checks have passed

@renovate[bot] @yegor256 Oops, I failed. You can see the full log here (spent 11s)

+ set -e
+ set -o pipefail
++ dirname ./run.sh
+ cd .
+ echo 3186704
+ echo '2.0-SNAPSHOT BUILD'
2.0-SNAPSHOT BUILD
+ date
Mon 04 Sep 2023 08:32:51 PM CEST
+ uptime
 20:32:51 up 285 days,  1:10,  0 users,  load average: 1.79, 1.68, 1.81
+ cat
com.rultor.spi.Profile: There is no 'merge' section in .rultor.yml for branch master in repo polystat/polystat-cli
	at com.rultor.agents.req.StartsRequest.docker(StartsRequest.java:350)
	at com.rultor.agents.req.StartsRequest.vars(StartsRequest.java:255)
	at com.rultor.agents.req.StartsRequest.script(StartsRequest.java:148)
	at com.rultor.agents.req.StartsRequest.process(StartsRequest.java:109)
	at com.rultor.agents.AbstractAgent.execute(AbstractAgent.java:75)
	at com.rultor.spi.Agent.execute(Agent.java:84)
	at com.rultor.agents.VerboseAgent.execute(VerboseAgent.java:62)
	at com.rultor.Routine.process(Routine.java:202)
	at com.rultor.Routine.unsafe_aroundBody0(Routine.java:180)
	at com.rultor.Routine.run(Routine.java:1)
	at org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:179)
	at com.jcabi.aspects.aj.MethodInterrupter.wrap(MethodInterrupter.java:108)
	at com.rultor.Routine.unsafe(Routine.java:175)
	at com.rultor.Routine.run(Routine.java:142)
	at com.jcabi.log.VerboseRunnable.run(VerboseRunnable.java:190)
	at com.jcabi.aspects.aj.MethodScheduler.lambda./run.sh(MethodScheduler.java:194)
	at java.base/java.util.concurrent.Executors.call(Executors.java:539)
	at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
	at java.base/java.util.concurrent.ScheduledThreadPoolExecutor.run(ScheduledThreadPoolExecutor.java:305)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
	at java.base/java.util.concurrent.ThreadPoolExecutor.run(ThreadPoolExecutor.java:635)
	at com.jcabi.log.VerboseThreads.run(VerboseThreads.java:222)
	at java.base/java.lang.Thread.run(Thread.java:833)

+ exit -1
'cid' file is absent, most probably the Docker container wasn't started correctly

@renovate renovate bot force-pushed the renovate/org.scalameta-munit-1.x branch from 9657705 to df1e107 Compare September 14, 2023 20:53
@renovate renovate bot changed the title Update dependency org.scalameta:munit to v1.0.0-M8 Update dependency org.scalameta:munit to v1.0.0-M9 Sep 14, 2023
@renovate renovate bot force-pushed the renovate/org.scalameta-munit-1.x branch from df1e107 to 5a0ba5d Compare September 17, 2023 02:35
@renovate renovate bot changed the title Update dependency org.scalameta:munit to v1.0.0-M9 Update dependency org.scalameta:munit to v1.0.0-M10 Sep 17, 2023
@renovate renovate bot force-pushed the renovate/org.scalameta-munit-1.x branch from 5a0ba5d to 57e8e05 Compare February 4, 2024 05:50
@renovate renovate bot changed the title Update dependency org.scalameta:munit to v1.0.0-M10 Update dependency org.scalameta:munit to v1.0.0-M11 Feb 4, 2024
@renovate renovate bot force-pushed the renovate/org.scalameta-munit-1.x branch from 57e8e05 to 3c84566 Compare April 18, 2024 17:53
@renovate renovate bot changed the title Update dependency org.scalameta:munit to v1.0.0-M11 Update dependency org.scalameta:munit to v1.0.0-M12 Apr 18, 2024
@renovate renovate bot force-pushed the renovate/org.scalameta-munit-1.x branch from 3c84566 to 3e8ebca Compare April 26, 2024 02:52
@renovate renovate bot changed the title Update dependency org.scalameta:munit to v1.0.0-M12 Update dependency org.scalameta:munit to v1.0.0-RC1 Apr 26, 2024
@renovate renovate bot force-pushed the renovate/org.scalameta-munit-1.x branch from 3e8ebca to d83f8f0 Compare May 22, 2024 20:40
@renovate renovate bot changed the title Update dependency org.scalameta:munit to v1.0.0-RC1 Update dependency org.scalameta:munit to v1.0.0 May 22, 2024
@renovate renovate bot force-pushed the renovate/org.scalameta-munit-1.x branch from d83f8f0 to bf63002 Compare August 12, 2024 23:47
@renovate renovate bot changed the title Update dependency org.scalameta:munit to v1.0.0 Update dependency org.scalameta:munit to v1.0.1 Aug 12, 2024
@renovate renovate bot force-pushed the renovate/org.scalameta-munit-1.x branch from bf63002 to 179a292 Compare September 14, 2024 05:56
@renovate renovate bot changed the title Update dependency org.scalameta:munit to v1.0.1 Update dependency org.scalameta:munit to v1.0.2 Sep 14, 2024
@renovate renovate bot force-pushed the renovate/org.scalameta-munit-1.x branch from 179a292 to df59897 Compare December 4, 2024 08:54
@renovate renovate bot changed the title Update dependency org.scalameta:munit to v1.0.2 Update dependency org.scalameta:munit to v1.0.3 Dec 4, 2024
@renovate renovate bot force-pushed the renovate/org.scalameta-munit-1.x branch from df59897 to 11124a6 Compare January 9, 2025 19:34
@renovate renovate bot changed the title Update dependency org.scalameta:munit to v1.0.3 Update dependency org.scalameta:munit to v1.0.4 Jan 9, 2025
@renovate renovate bot force-pushed the renovate/org.scalameta-munit-1.x branch from 11124a6 to 442e0c7 Compare January 23, 2025 08:15
@renovate renovate bot changed the title Update dependency org.scalameta:munit to v1.0.4 Update dependency org.scalameta:munit to v1.1.0 Jan 23, 2025
@renovate renovate bot force-pushed the renovate/org.scalameta-munit-1.x branch from 442e0c7 to 7661292 Compare May 3, 2025 03:25
@renovate renovate bot changed the title Update dependency org.scalameta:munit to v1.1.0 Update dependency org.scalameta:munit to v1.1.1 May 3, 2025
@renovate renovate bot force-pushed the renovate/org.scalameta-munit-1.x branch from 7661292 to cad0579 Compare September 14, 2025 20:14
@renovate renovate bot changed the title Update dependency org.scalameta:munit to v1.1.1 Update dependency org.scalameta:munit to v1.2.0 Sep 14, 2025
@renovate renovate bot force-pushed the renovate/org.scalameta-munit-1.x branch from cad0579 to 9bc8416 Compare October 15, 2025 19:50
@renovate renovate bot changed the title Update dependency org.scalameta:munit to v1.2.0 Update dependency org.scalameta:munit to v1.2.1 Oct 15, 2025
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.

2 participants

@yegor256 @rultor