toolshed/recipes.coopcloud.tech
toolshed/recipes.coopcloud.tech
1
2
Fork 0
Code Issues 7 Pull Requests Projects Releases Wiki Activity

Update dependency elm-test to v0.19.1-revision9 (main) #21

Closed
renovate-bot wants to merge 1 commits from renovate/main-elm-test-0.x into main
pull from: renovate/main-elm-test-0.x
merge into: toolshed:main
Conversation 1 Commits 1 Files Changed 1 +1 -1
renovate-bot commented 2023-01-20 08:15:09 +00:00
Contributor
Copy Link

This PR contains the following updates:

Package Type Update Change
elm-test devDependencies patch 0.19.1-revision2 -> 0.19.1-revision9

Release Notes

rtfeldman/node-test-runner

v0.19.1-revision9

Compare Source

Fixed
  • elm-test install-unstable-test-master (added in the previous version) now works with packages.

v0.19.1-revision8

Compare Source

Breaking
  • Removed support for Node.js 10 (which reached end of life 2021-04-30). Node.js 12.20.0 is now the minimum supported Node.js version. (Node.js 12 actually reached end of life 2022-04-30, but we decided to keep support for it for a while longer since there was no need of dropping it right now.)
Added
  • elm-test install-unstable-test-master
    • which installs the master version of the elm-explorations/test library in place of the 1.2.2 version in your ELM_HOME
  • elm-test uninstall-unstable-test-master
    • which undoes that

This let’s you test the upcoming major version of elm-explorations/test. Big thanks to Martin Janiczek!

Changed

  • elm-test no longer uses elm-json to calculate the set of dependencies needed to run your tests. Instead, we use elm-solve-deps-wasm which basically is a WebAssembly port of the dependency solver in elm-test-rs. Big thanks to Matthieu Pizenberg! Benefits of this change:

    • elm-test no longer needs to download the elm-json binary at install time or run time. elm-solve-deps-wasm is a regular, cross platform npm package.
    • Improves compatibility with Lamdera.
    • elm-solve-deps-wasm works offline to a greater extent than elm-json. Many times it doesn’t need to make any calls to package.elm-lang.org at all!

  • elm-test now shows suggestions on misspelled CLI flags.

Fixed
  • If you have module MyTest exposing (..) with the expose-all (..) and a char literal with a unicode escape, like '\u{000D}', in the same file, elm-test now correctly finds all tests to run in that file. A bug with unicode escape parsing previously caused no tests to be found.

v0.19.1-revision7

Compare Source

Fixed
  • elm-test now works if you have { "type": "module" } in your package.json.
  • --output=/dev/null is now ignored. This is needed by Emacs’ flycheck-elm package, which calls both elm make and elm-test make with --output=/dev/null. elm-test make does not produce any output files, so the flag doesn’t change anything. (Before 0.19.1-revision5, all unknown flags were silently ignored.)
  • The “no tests found” error message now works with --report=json and --report=junit again (regression in 0.19.1-revision5).
  • Better error message for --fuzz=0.

v0.19.1-revision6

Compare Source

Fixed
  • The --no-color and --color flags (to disable and force colors) now work again (regression in 0.19.1-revision5).
  • --no-color now turns off colors in Elm compiler error messages as well.

v0.19.1-revision5

Compare Source

Breaking
  • Removed support for Node.js 8 (which reached end of life 2019-12-31). Node.js 10.13.0 is now the minimum supported Node.js version.
  • Removed the undocumented --verbose flag. It didn’t do much at all in its current state.
Fixed
  • Now works on Apple Silicon/M1/ARM MacBooks. Installation used to fail with “Error: No binaries are available for your platform: darwin-arm64.”
  • You can now run your test from a subdirectory. elm-test finds your elm.json up the directory tree instead of printing an error.
  • If you had a port named send or receive and they were reached via test cases, elm-test used to fail with a duplicate port error. elm-test has renamed its internal ports so that conflicts are very unlikely.
  • The JUnit reporter now says @failures instead of @failed which makes Jenkins happier.
  • elm-test now errors on unknown (misspelled) flags instead of silently ignoring them.
  • elm-test now errors on bad --fuzz and --seed values instead of silently ignoring them.
  • A whole host of Elm package dependencies errors, by using elm-json to calculate the set of dependencies needed to run your tests.
  • elm-test --watch no longer crashes if for packages if there are compilation errors in src/ at startup.
  • elm-test --watch now detects changes in your elm.json.
  • elm-test --watch now works better when lots of files change at once. If 10 files changed, your tests used to run 10 times in sequence (more or less). Now, they only run once or twice. Changes within 100 ms are batched together. Changes happening while the tests are running no longer queue up – they instead trigger one single test once the current run is done.
  • Compilation errors are no longer hidden by a super long “Compilation failed while attempting to build [absolute paths to every single test Elm file]” message.
  • A bunch of checks and validations have been added to help in edge cases.

v0.19.1-revision4

Compare Source

Fixed
  • The --compiler command line flag now correctly finds elm executables on your PATH (see #​438).
  • We have hugely slimmed down the reproduction instructions so that the test runner no longer prints hundreds of test file paths to the console (see issue #​431 and fix #​432).
Performance
  • A whole host of spring cleaning that streamlines the test runner. (see #​425).

v0.19.1-revision3

Compare Source

Fixed
  • Pointing to specific test files sometimes failed (see issue #​391 and fix #​404).

Configuration

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

🚦 Automerge: Enabled.

♻️ 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 Renovate Bot.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [elm-test](https://github.com/rtfeldman/node-test-runner) | devDependencies | patch | [`0.19.1-revision2` -> `0.19.1-revision9`](https://renovatebot.com/diffs/npm/elm-test/0.19.1-revision2/0.19.1-revision9) | --- ### Release Notes <details> <summary>rtfeldman/node-test-runner</summary> ### [`v0.19.1-revision9`](https://github.com/rtfeldman/node-test-runner/blob/HEAD/CHANGELOG.md#&#8203;0191-revision9---2022-07-03) [Compare Source](https://github.com/rtfeldman/node-test-runner/compare/0.19.1-revision8...0.19.1-revision9) ##### Fixed - `elm-test install-unstable-test-master` (added in the previous version) now works with packages. ### [`v0.19.1-revision8`](https://github.com/rtfeldman/node-test-runner/blob/HEAD/CHANGELOG.md#&#8203;0191-revision8---2022-06-20) [Compare Source](https://github.com/rtfeldman/node-test-runner/compare/0.19.1-revision7...0.19.1-revision8) ##### Breaking - Removed support for Node.js 10 (which reached end of life 2021-04-30). Node.js 12.20.0 is now the minimum supported Node.js version. (Node.js 12 actually reached end of life 2022-04-30, but we decided to keep support for it for a while longer since there was no need of dropping it right now.) ##### Added - `elm-test install-unstable-test-master` - which installs the `master` version of the `elm-explorations/test` library in place of the `1.2.2` version in your `ELM_HOME` - `elm-test uninstall-unstable-test-master` - which undoes that **This let’s you test the [upcoming major version of elm-explorations/test](https://discourse.elm-lang.org/t/call-for-testing-of-elm-explorations-test-2-0-0/8458).** Big thanks to [Martin Janiczek](https://github.com/Janiczek/)! ##### Changed - elm-test no longer uses [elm-json](https://github.com/zwilias/elm-json/) to calculate the set of dependencies needed to run your tests. Instead, we use [elm-solve-deps-wasm](https://github.com/mpizenberg/elm-solve-deps-wasm) which basically is a WebAssembly port of the dependency solver in [elm-test-rs](https://github.com/mpizenberg/elm-test-rs). Big thanks to [Matthieu Pizenberg](https://github.com/mpizenberg/)! Benefits of this change: - elm-test no longer needs to download the elm-json binary at install time or run time. elm-solve-deps-wasm is a regular, cross platform npm package. - Improves compatibility with [Lamdera](https://lamdera.com/). - elm-solve-deps-wasm works offline to a greater extent than elm-json. Many times it doesn’t need to make any calls to package.elm-lang.org at all! - elm-test now shows suggestions on misspelled CLI flags. ##### Fixed - If you have `module MyTest exposing (..)` with the expose-all `(..)` *and* a char literal with a unicode escape, like `'\u{000D}'`, in the same file, elm-test now correctly finds all tests to run in that file. A bug with unicode escape parsing previously caused no tests to be found. ### [`v0.19.1-revision7`](https://github.com/rtfeldman/node-test-runner/blob/HEAD/CHANGELOG.md#&#8203;0191-revision7---2021-05-14) [Compare Source](https://github.com/rtfeldman/node-test-runner/compare/0.19.1-revision6...0.19.1-revision7) ##### Fixed - elm-test now works if you have `{ "type": "module" }` in your package.json. - `--output=/dev/null` is now ignored. This is needed by Emacs’ flycheck-elm package, which calls both `elm make` and `elm-test make` with `--output=/dev/null`. `elm-test make` does not produce any output files, so the flag doesn’t change anything. (Before 0.19.1-revision5, all unknown flags were silently ignored.) - The “no tests found” error message now works with `--report=json` and `--report=junit` again (regression in 0.19.1-revision5). - Better error message for `--fuzz=0`. ### [`v0.19.1-revision6`](https://github.com/rtfeldman/node-test-runner/blob/HEAD/CHANGELOG.md#&#8203;0191-revision6---2020-01-29) [Compare Source](https://github.com/rtfeldman/node-test-runner/compare/0.19.1-revision5...0.19.1-revision6) ##### Fixed - The `--no-color` and `--color` flags (to disable and force colors) now work again (regression in 0.19.1-revision5). - `--no-color` now turns off colors in Elm compiler error messages as well. ### [`v0.19.1-revision5`](https://github.com/rtfeldman/node-test-runner/blob/HEAD/CHANGELOG.md#&#8203;0191-revision5---2020-01-28) [Compare Source](https://github.com/rtfeldman/node-test-runner/compare/0.19.1-revision4...0.19.1-revision5) ##### Breaking - Removed support for Node.js 8 (which reached end of life 2019-12-31). Node.js 10.13.0 is now the minimum supported Node.js version. - Removed the undocumented `--verbose` flag. It didn’t do much at all in its current state. ##### Fixed - Now works on Apple Silicon/M1/ARM MacBooks. Installation used to fail with “Error: No binaries are available for your platform: darwin-arm64.” - You can now run your test from a subdirectory. `elm-test` finds your `elm.json` up the directory tree instead of printing an error. - If you had a port named `send` or `receive` and they were reached via test cases, `elm-test` used to fail with a duplicate port error. `elm-test` has renamed its internal ports so that conflicts are very unlikely. - The JUnit reporter now says `@failures` instead of `@failed` which makes Jenkins happier. - `elm-test` now errors on unknown (misspelled) flags instead of silently ignoring them. - `elm-test` now errors on bad `--fuzz` and `--seed` values instead of silently ignoring them. - A whole host of Elm package dependencies errors, by using `elm-json` to calculate the set of dependencies needed to run your tests. - `elm-test --watch` no longer crashes if for packages if there are compilation errors in `src/` at startup. - `elm-test --watch` now detects changes in your `elm.json`. - `elm-test --watch` now works better when lots of files change at once. If 10 files changed, your tests used to run 10 times in sequence (more or less). Now, they only run once or twice. Changes within 100 ms are batched together. Changes happening while the tests are running no longer queue up – they instead trigger one single test once the current run is done. - Compilation errors are no longer hidden by a super long “Compilation failed while attempting to build \[absolute paths to every single test Elm file]” message. - A bunch of checks and validations have been added to help in edge cases. ### [`v0.19.1-revision4`](https://github.com/rtfeldman/node-test-runner/blob/HEAD/CHANGELOG.md#&#8203;0191-revision4---2020-09-21) [Compare Source](https://github.com/rtfeldman/node-test-runner/compare/0.19.1-revision3...0.19.1-revision4) ##### Fixed - The `--compiler` command line flag now correctly finds elm executables on your PATH (see [#&#8203;438](https://github.com/rtfeldman/node-test-runner/pull/438)). - We have hugely slimmed down the reproduction instructions so that the test runner no longer prints hundreds of test file paths to the console (see issue [#&#8203;431](https://github.com/rtfeldman/node-test-runner/issues/431) and fix [#&#8203;432](https://github.com/rtfeldman/node-test-runner/pull/432)). ##### Performance - A whole host of spring cleaning that streamlines the test runner. (see [#&#8203;425](https://github.com/rtfeldman/node-test-runner/pull/425)). ### [`v0.19.1-revision3`](https://github.com/rtfeldman/node-test-runner/blob/HEAD/CHANGELOG.md#&#8203;0191-revision3---2020-01-10) [Compare Source](https://github.com/rtfeldman/node-test-runner/compare/0.19.1-revision2...0.19.1-revision3) ##### Fixed - Pointing to specific test files sometimes failed (see issue [#&#8203;391](https://github.com/rtfeldman/node-test-runner/issues/391) and fix [#&#8203;404](https://github.com/rtfeldman/node-test-runner/pull/404)). </details> --- ### Configuration :date: **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). :vertical_traffic_light: **Automerge**: Enabled. :recycle: **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. :no_bell: **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNC4xMDUuNCIsInVwZGF0ZWRJblZlciI6IjM0LjEwNS40In0=-->
renovate-bot added 1 commit 2023-01-20 08:15:20 +00:00
Update dependency elm-test to v0.19.1-revision9
Some checks failed
renovate/artifacts Artifact file update failure
continuous-integration/drone/pr Build is failing
Details
44e4ccee3e
renovate-bot scheduled this pull request to auto merge when all checks succeed 2023-01-20 08:15:27 +00:00
3wordchant closed this pull request 2023-01-23 04:43:44 +00:00
renovate-bot commented 2023-01-23 08:05:26 +00:00
Author
Contributor
Copy Link

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will now ignore this update (0.19.1-revision9). You will still receive a PR once a newer version is released, so if you wish to permanently ignore this dependency, please add it to the ignoreDeps array of your renovate config.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.

### Renovate Ignore Notification As this PR has been closed unmerged, Renovate will now ignore this update (0.19.1-revision9). You will still receive a PR once a newer version is released, so if you wish to permanently ignore this dependency, please add it to the `ignoreDeps` array of your renovate config. If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.
Some checks failed
renovate/artifacts Artifact file update failure
continuous-integration/drone/pr Build is failing
Details

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
bug
Something is not working
duplicate
This issue or pull request already exists
enhancement
New feature
help wanted
Need some help
invalid
Something is wrong
question
More information is needed
wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: toolshed/recipes.coopcloud.tech#21
No description provided.
Delete Branch "renovate/main-elm-test-0.x"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?