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

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

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

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 4, 2023 •
edited

Mend Renovate

This PR contains the following updates:

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

Release Notes

scalameta/munit (org.scalameta:munit)

v1.0.0

Compare Source

https://scalameta.org/munit/blog/2024/05/15/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 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

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.

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

None yet
2 participants
@yegor256 @rultor