chore(deps-dev): bump the development-dependencies group across 1 directory with 8 updates

[dependabot[bot]]

Bumps the development-dependencies group with 8 updates in the / directory:

Package	From	To
@biomejs/biome	1.8.0	1.8.3
@effect/vitest	0.5.8	0.6.2
@types/node	20.14.2	20.14.10
@vitest/coverage-v8	1.6.0	2.0.1
@vitest/ui	1.6.0	2.0.1
rimraf	5.0.7	6.0.0
typescript	5.4.5	5.5.3
vitest	1.6.0	2.0.1

Updates @biomejs/biome from 1.8.0 to 1.8.3

Release notes

Sourced from @​biomejs/biome's releases.

CLI v1.8.3

CLI

Bug fixes

• Fix #3104 by suppressing node warnings when using biome migrate. Contributed by @​SuperchupuDev

• Force colors to be off when using the GitHub reporter to properly create annotations in GitHub actions (#3148). Contributed by @​Sec-ant

Parser

Bug fixes

• Implement CSS unicode range. Contributed by @​denbezrukov

Formatter

Bug fixes

• Fix #3184 CSS formatter converts custom identifiers to lowercase. Contributed by @​denbezrukov
• Fix #3256 constant crashes when editing css files #3256. Contributed by @​denbezrukov

Linter

New features

• Add nursery/useDeprecatedReason rule. Contributed by @​vohoanglong0107.
• Add nursery/noExportedImports. Contributed by @​Conaclos

Bug fixes

• useConsistentArrayType and useShorthandArrayType now ignore Array in the extends and implements clauses. Fix #3247. Contributed by @​Conaclos
• Fixes #3066 by taking into account the dependencies declared in the package.json. Contributed by @​ematipico
• The code action of the useArrowFunction rule now preserves a trailing comma when there is only a single type parameter in the arrow function and JSX is enabled. Fixes #3292. Contributed by @​Sec-ant

Enhancements

• Enhance tailwind sorting lint rule #1274 with variant support.

  Every preconfigured variant is assigned a weight that concurs on establishing the output sorting order. Since nesting variants on the same utility class is possible, the resulting weight is the Bitwise XOR of all the variants weight for that class. Dynamic variants (e.g. has-[.custom-class], group-[:checked]) are also supported and they take the weight of their base variant name the custom value attached (e.g. has-[.custom-class] takes has weight). Arbitrary variants (e.g. [&nth-child(2)]) don't have a weight assigned and they are placed after every known variant. Classes with the same amount of arbitrary variants follow lexicographical order. The class that has the highest number of nested arbitrary variants is placed last. Screen variants (e.g. sm:, max-md:, min-lg:) are not supported yet.

  Contributed by @​lutaok

... (truncated)

Changelog

Sourced from @​biomejs/biome's changelog.

v1.8.3 (2024-06-27)

CLI

Bug fixes

• Fix #3104 by suppressing node warnings when using biome migrate. Contributed by @​SuperchupuDev

• Force colors to be off when using the GitHub reporter to properly create annotations in GitHub actions (#3148). Contributed by @​Sec-ant

Parser

Bug fixes

• Implement CSS unicode range. Contributed by @​denbezrukov

Formatter

Bug fixes

• Fix #3184 CSS formatter converts custom identifiers to lowercase. Contributed by @​denbezrukov
• Fix #3256 constant crashes when editing css files #3256. Contributed by @​denbezrukov

Linter

New features

• Add nursery/useDeprecatedReason rule. Contributed by @​vohoanglong0107.
• Add nursery/noExportedImports. Contributed by @​Conaclos

Enhancements

• Implement suggestedExtensions option for useImportExtensions rule. Contributed by @​drdaemos

Bug fixes

• useConsistentArrayType and useShorthandArrayType now ignore Array in the extends and implements clauses. Fix #3247. Contributed by @​Conaclos
• Fixes #3066 by taking into account the dependencies declared in the package.json. Contributed by @​ematipico
• The code action of the useArrowFunction rule now preserves a trailing comma when there is only a single type parameter in the arrow function and JSX is enabled. Fixes #3292. Contributed by @​Sec-ant

Enhancements

• Enhance tailwind sorting lint rule #1274 with variant support.

  Every preconfigured variant is assigned a weight that concurs on establishing the output sorting order. Since nesting variants on the same utility class is possible, the resulting weight is the Bitwise XOR of all the variants weight for that class. Dynamic variants (e.g. has-[.custom-class], group-[:checked]) are also supported and they take the weight of their base variant name the custom value attached (e.g. has-[.custom-class] takes has weight). Arbitrary variants (e.g. [&nth-child(2)]) don't have a weight assigned and they are placed after every known variant. Classes with the same amount of arbitrary variants follow lexicographical order. The class that has the highest number of nested arbitrary variants is placed last. Screen variants (e.g. sm:, max-md:, min-lg:) are not supported yet.

... (truncated)

Commits

• c28d597 release: v1.8.3 (#3302)
• f88b7b2 chore: update codegen to include GraphQL (#3301)
• 6f9c938 feat(noExportedImports): add lint rule (#3097)
• cd3bb04 chore(deps): update @​biomejs packages (#3266)
• 54b4c9a release: v1.8.2 (#3243)
• 6f8cab7 feat(biome_css_analyzer): implement function-linear-gradient-no-nonstandard-d...
• 0d9b60a feat(lint/useValidAutocomplete): add rule (#3143)
• 9d518d8 chore(deps): update @​biomejs packages (#3145)
• 4a7baaa feat(biome_js_analyzer): noSubstr (#3125)
• 535acc7 fix(ci): rule check error messages (#3158)
• Additional commits viewable in compare view

Updates @effect/vitest from 0.5.8 to 0.6.2

Release notes

Sourced from @​effect/vitest's releases.

@​effect/vitest@​0.6.2

Patch Changes

• Updated dependencies [a435e0f, b5554db, a9c4fb3]:
  • effect@3.4.8

@​effect/vitest@​0.6.1

Patch Changes

• Updated dependencies [a5737d6]:
  • effect@3.4.7

Changelog

Sourced from @​effect/vitest's changelog.

0.6.2

Patch Changes

• Updated dependencies [a435e0f, b5554db, a9c4fb3]:
  • effect@3.4.8

0.6.1

Patch Changes

• Updated dependencies [a5737d6]:
  • effect@3.4.7

0.6.0

Minor Changes

• #3122 489d20a Thanks @​sukovanej! - Refactor @effect/vitest package.

  • Clear separation of the public API and internals.
  • Fix type of scoped, live, scopedLive and effect objects. Make sure skip and only are available.
  • Add each method to scoped, live, scopedLive and effect objects.

  Example usage

  import { expect, it } from "@effect/vitest";
  import { Effect } from "effect";
  it.scoped.skip("test skipped", () =>
  Effect.acquireRelease(Effect.die("skipped anyway"), () => Effect.void),
  );
  it.effect.each([1, 2, 3])("effect each %s", (n) =>
  Effect.sync(() => expect(n).toEqual(n)),
  );
  

Patch Changes

• Updated dependencies [5c0ceb0, 5c0ceb0, 33735b1, 5c0ceb0, 139d4b3]:
  • effect@3.4.6

0.5.21

Patch Changes

• Updated dependencies [a047af9]:
  • effect@3.4.5

... (truncated)

Commits

• 3429c8f Version Packages (#3172)
• ad51cbe Version Packages (#3162)
• a4982f6 Version Packages (#3128)
• 489d20a refactor vitest (#3122)
• c187493 Version Packages (#3100)
• e86211a Version Packages (#3093)
• 6b3bd87 Version Packages (#3081)
• a70705c Version Packages (#3071)
• 7ba763c Version Packages (#3060)
• 01075fb Version Packages (#3034)
• Additional commits viewable in compare view

Updates @types/node from 20.14.2 to 20.14.10

Commits

• See full diff in compare view

Updates @vitest/coverage-v8 from 1.6.0 to 2.0.1

Release notes

Sourced from @​vitest/coverage-v8's releases.

v2.0.1

   🐞 Bug Fixes

• browser: Correctly inherit browser config in a workspace  -  by @​sheremet-va in vitest-dev/vitest#6054 (4b03e)
• ui: Move virtual scroller to dev dependencies  -  by @​userquin in vitest-dev/vitest#6053 (f94ed)
• vitest: Print only running files, not every file  -  by @​sheremet-va in vitest-dev/vitest#6052 (4d559)

    View changes on GitHub

v2.0.0

Vitest 2.0 is here! This release page lists all changes made to the project during the beta. For the migration guide, please refer to the documentation.

🚨 Breaking Changes

• Simplify mock function generic types and align with jest - by @​hi-ogawa in vitest-dev/vitest#4784 (a0c1d37)
• Remove --segfault-retry - by @​sheremet-va in vitest-dev/vitest#5514 (ed60e)
  • This flag was introduced to combat threads segfaults. Our current recommendation is to use the new default forks pool instead.
• Run suite hooks in a stack - by @​sheremet-va in vitest-dev/vitest#5609 (1277d)
  • This feels like a more sensible default. Especially with the new onTestFinished hook. This can make your tests run a little bit slower.
• Enable coverage.ignoreEmptyLines by default - by @​AriPerkkio in vitest-dev/vitest#5543 (31994)
  • ⚠️ This change may cause significant differences in your coverage results compared to Vitest v1. These changes are expected as coverage reporting is now more accurate. See vitest-dev/vitest#5423 for more details.
• Add correct location and snapshot fields in json reporter - by @​sheremet-va in vitest-dev/vitest#5434 (bcccc)
  • Previously, the location field pointed to the error location instead of the test location. Now it is aligned with jest and contains the line and column of a test function, but requires includeTaskLocation to be enabled.
• Update dependency chai to v5 - by renovate[bot] and @​sheremet-va in vitest-dev/vitest#5135 (73646)
• Remove watchExclude - by @​patak-dev in vitest-dev/vitest#5177 (d7371)
• Change default pool to 'forks' - by @​AriPerkkio in vitest-dev/vitest#5047 (7f8f9)
  • This change is done for compatibility issues
  • This pool may be slightly slower than previous threads pool: https://vitest.dev/guide/improving-performance.html#pool
• --merge-reports to support coverage - by @​AriPerkkio in vitest-dev/vitest#5736 (b7438)
• Add promise-based return assertions, do not auto-resolve returned promises - by @​sheremet-va in vitest-dev/vitest#5749 (5f710)
  • ⚠️ Vitest no longer unwraps promises in spy.mock.returns. If the function is async or returns a promise, it will always succeed and have a Promise in results. To make migration easier, we introduced spy.mock.settledResults that unwraps promises and expect().toHaveResolved() matcher that accepts unwrapped value.
• Do not exit process if global setup has failed - by @​sheremet-va in vitest-dev/vitest#5726 (ddb09)
• Don't exit process if config failed - by @​sheremet-va in vitest-dev/vitest#5715 (f232f)
• Add meta to json output - by @​sheremet-va in vitest-dev/vitest#5802 (dd754)
• Rename indexScripts to orchestratorScripts in the browser config - by @​sheremet-va in vitest-dev/vitest#5842 (49f34)
• Add "vitest list" API to print collected tests without running them - by @​sheremet-va in vitest-dev/vitest#6013 (583dd)
  • ⚠️ This changes the custom pool API - now requires collectTests method alongside runTests.
• Remove the empty suite from the runner - by @​sheremet-va in vitest-dev/vitest#5435 (dbbbe)
• Support concurrent suites - by @​hi-ogawa in vitest-dev/vitest#5491 (222ce44)
• Support overriding exclude in coverage - by @​AriPerkkio in vitest-dev/vitest#5997 (169bc)
  • ⚠️ Vitest coverage no longer adds test files to exclude patterns if coverage.exclude was overridden in the config. Add your test patterns manually, or merge your overrides with default ones: ['**/my-pattern.js', ...coverageConfigDefaults.exclude]. See https://vitest.dev/config/#coverage-exclude for an example.

🚀 Features

• browser:
  • 🌐 This release lays the groundwork for the next iteration of Vitest Browser Mode. You can read more about our future plans at https://github.com/vitest-dev/vitest/discussions/5828
  • Add commands to communicate betweens server and the browser - by @​sheremet-va in vitest-dev/vitest#5097 (aa431)
  • Do not reload the page during watch mode - by @​sheremet-va in vitest-dev/vitest#5810 (e5b9a)

... (truncated)

Commits

• 16eb6c8 chore: release v2.0.1
• 1b150a3 chore: release v2.0.0
• 5611895 chore: release v2.0.0-beta.13
• 368c137 fix(coverage): remove work-around for implicit else (#6014)
• 05d5f38 chore(deps): update all non-major dependencies (#5957)
• 169bc1f fix(coverage): support overriding exclude (#5997)
• cd9cc6b chore: release v2.0.0-beta.12
• fca8b92 chore(deps): update v8-to-istanbul (#5958)
• 7080513 fix(coverage): pass thresholds errors to stderr of startVitest() (#5954)
• 3fd15ba chore: release v2.0.0-beta.11
• Additional commits viewable in compare view

Updates @vitest/ui from 1.6.0 to 2.0.1

Release notes

Sourced from @​vitest/ui's releases.

v2.0.1

   🐞 Bug Fixes

• browser: Correctly inherit browser config in a workspace  -  by @​sheremet-va in vitest-dev/vitest#6054 (4b03e)
• ui: Move virtual scroller to dev dependencies  -  by @​userquin in vitest-dev/vitest#6053 (f94ed)
• vitest: Print only running files, not every file  -  by @​sheremet-va in vitest-dev/vitest#6052 (4d559)

    View changes on GitHub

v2.0.0

Vitest 2.0 is here! This release page lists all changes made to the project during the beta. For the migration guide, please refer to the documentation.

🚨 Breaking Changes

• Simplify mock function generic types and align with jest - by @​hi-ogawa in vitest-dev/vitest#4784 (a0c1d37)
• Remove --segfault-retry - by @​sheremet-va in vitest-dev/vitest#5514 (ed60e)
  • This flag was introduced to combat threads segfaults. Our current recommendation is to use the new default forks pool instead.
• Run suite hooks in a stack - by @​sheremet-va in vitest-dev/vitest#5609 (1277d)
  • This feels like a more sensible default. Especially with the new onTestFinished hook. This can make your tests run a little bit slower.
• Enable coverage.ignoreEmptyLines by default - by @​AriPerkkio in vitest-dev/vitest#5543 (31994)
  • ⚠️ This change may cause significant differences in your coverage results compared to Vitest v1. These changes are expected as coverage reporting is now more accurate. See vitest-dev/vitest#5423 for more details.
• Add correct location and snapshot fields in json reporter - by @​sheremet-va in vitest-dev/vitest#5434 (bcccc)
  • Previously, the location field pointed to the error location instead of the test location. Now it is aligned with jest and contains the line and column of a test function, but requires includeTaskLocation to be enabled.
• Update dependency chai to v5 - by renovate[bot] and @​sheremet-va in vitest-dev/vitest#5135 (73646)
• Remove watchExclude - by @​patak-dev in vitest-dev/vitest#5177 (d7371)
• Change default pool to 'forks' - by @​AriPerkkio in vitest-dev/vitest#5047 (7f8f9)
  • This change is done for compatibility issues
  • This pool may be slightly slower than previous threads pool: https://vitest.dev/guide/improving-performance.html#pool
• --merge-reports to support coverage - by @​AriPerkkio in vitest-dev/vitest#5736 (b7438)
• Add promise-based return assertions, do not auto-resolve returned promises - by @​sheremet-va in vitest-dev/vitest#5749 (5f710)
  • ⚠️ Vitest no longer unwraps promises in spy.mock.returns. If the function is async or returns a promise, it will always succeed and have a Promise in results. To make migration easier, we introduced spy.mock.settledResults that unwraps promises and expect().toHaveResolved() matcher that accepts unwrapped value.
• Do not exit process if global setup has failed - by @​sheremet-va in vitest-dev/vitest#5726 (ddb09)
• Don't exit process if config failed - by @​sheremet-va in vitest-dev/vitest#5715 (f232f)
• Add meta to json output - by @​sheremet-va in vitest-dev/vitest#5802 (dd754)
• Rename indexScripts to orchestratorScripts in the browser config - by @​sheremet-va in vitest-dev/vitest#5842 (49f34)
• Add "vitest list" API to print collected tests without running them - by @​sheremet-va in vitest-dev/vitest#6013 (583dd)
  • ⚠️ This changes the custom pool API - now requires collectTests method alongside runTests.
• Remove the empty suite from the runner - by @​sheremet-va in vitest-dev/vitest#5435 (dbbbe)
• Support concurrent suites - by @​hi-ogawa in vitest-dev/vitest#5491 (222ce44)
• Support overriding exclude in coverage - by @​AriPerkkio in vitest-dev/vitest#5997 (169bc)
  • ⚠️ Vitest coverage no longer adds test files to exclude patterns if coverage.exclude was overridden in the config. Add your test patterns manually, or merge your overrides with default ones: ['**/my-pattern.js', ...coverageConfigDefaults.exclude]. See https://vitest.dev/config/#coverage-exclude for an example.

🚀 Features

• browser:
  • 🌐 This release lays the groundwork for the next iteration of Vitest Browser Mode. You can read more about our future plans at https://github.com/vitest-dev/vitest/discussions/5828
  • Add commands to communicate betweens server and the browser - by @​sheremet-va in vitest-dev/vitest#5097 (aa431)
  • Do not reload the page during watch mode - by @​sheremet-va in vitest-dev/vitest#5810 (e5b9a)

... (truncated)

Commits

• 16eb6c8 chore: release v2.0.1
• f94ede0 fix(ui): move virtual scroller to dev dependencies (#6053)
• 1b150a3 chore: release v2.0.0
• 5611895 chore: release v2.0.0-beta.13
• 05d5f38 chore(deps): update all non-major dependencies (#5957)
• 7ec298e feat(ui): add action to explorer item to show the test/suite line in the sour...
• cd9cc6b chore: release v2.0.0-beta.12
• 7fd341c chore(ui): add explorer.md overall behavior (#5950)
• c31c41c feat(ui): add initializing explorer logic (#5941)
• ea12834 chore(ui): fix teardown type in Error shim (#5949)
• Additional commits viewable in compare view

Updates rimraf from 5.0.7 to 6.0.0

Changelog

Sourced from rimraf's changelog.

6.0

• Drop support for nodes before v20

5.0

• No default export, only named exports

4.4

• Provide Dirent or Stats object as second argument to filter

4.3

• Return boolean indicating whether the path was fully removed
• Add filter option
• bin: add --verbose, -v to print files as they are deleted
• bin: add --no-verbose, -V to not print files as they are deleted
• bin: add -i --interactive to be prompted on each deletion
• bin: add -I --no-interactive to not be prompted on each deletion
• 4.3.1 Fixed inappropriately following symbolic links to directories

v4.2

• Brought back glob support, using the new and improved glob v9

v4.1

• Improved hybrid module with no need to look at the .default dangly bit. .default preserved as a reference to rimraf for compatibility with anyone who came to rely on it in v4.0.
• Accept and ignore -rf and -fr arguments to the bin.

v4.0

• Remove glob dependency entirely. This library now only accepts actual file and folder names to delete.
• Accept array of paths or single path.
• Windows performance and reliability improved.
• All strategies separated into explicitly exported methods.
• Drop support for Node.js below version 14
• rewrite in TypeScript
• ship CJS/ESM hybrid module
• Error on unknown arguments to the bin. (Previously they were silently ignored.)

v3.0

... (truncated)

Commits

• 90d1feb 6.0.0
• 9b2a2b1 drop dead node versions
• 546c9ec 5.0.9
• 043338a restore support for dead node versions
• 0d83c12 5.0.8
• 88e632b drop eol node 14
• f8c4b20 DOC: missing punctuation & some grammar fixes (#307)
• dc3ffe5 update tap, tshy, drop node 16 from ci
• See full diff in compare view

Updates typescript from 5.4.5 to 5.5.3

Release notes

Sourced from typescript's releases.

TypeScript 5.5.3

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for TypeScript v5.5.3 (Stable).
• fixed issues query for TypeScript v5.5.2 (Stable).
• fixed issues query for TypeScript v5.5.1 (RC).
• fixed issues query for TypeScript v5.5.0 (Beta).

Downloads are available on:

• npm
• NuGet package

TypeScript 5.5

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for TypeScript v5.5.2 (Stable).
• fixed issues query for TypeScript v5.5.1 (RC).
• fixed issues query for TypeScript v5.5.0 (Beta).

Downloads are available on:

• npm

TypeScript 5.5 RC

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for Typescript 5.5.0 (Beta).
• fixed issues query for Typescript 5.5.1 (RC).

Downloads are available on:

• NuGet package

TypeScript 5.5 Beta

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for Typescript 5.5.0 (Beta).

Downloads are available on:

• npm

... (truncated)

Commits

• f0e9921 Bump version to 5.5.3 and LKG
• 738bd60 Cherry-pick #58966 to release-5.5 (#59002)
• ce2e60e Update LKG
• f3b21a2 🤖 Pick PR #58931 (Defer creation of barebonesLibSourc...) into release-5.5 (#...
• 7b1620b 🤖 Pick PR #58811 (fix(58801): "Move to file" on globa...) into release-5.5 (#...
• 5367ae1 Bump version to 5.5.2 and LKG
• 02132e5 🤖 Pick PR #58895 (Fix global when typescript.js loade...) into release-5.5 (#...
• 45b1e3c 🤖 Pick PR #58872 (Fix declaration emit crash) into release-5.5 (#58874)
• 17933ee 🤖 Pick PR #58810 (Fixed declaration emit issue relate...) into release-5.5 (#...
• 552b07e 🤖 Pick PR #58786 (Fixed declaration emit crash relate...) into release-5.5 (#...
• Additional commits viewable in compare view

Updates vitest from 1.6.0 to 2.0.1

Release notes

Sourced from vitest's releases.

v2.0.1

   🐞 Bug Fixes

• browser: Correctly inherit browser config in a workspace  -  by @​sheremet-va in vitest-dev/vitest#6054 (4b03e)
• ui: Move virtual scroller to dev dependencies  -  by @​userquin in vitest-dev/vitest#6053 (f94ed)
• vitest: Print only running files, not every file  -  by @​sheremet-va in vitest-dev/vitest#6052 (4d559)

    View changes on GitHub

v2.0.0

Vitest 2.0 is here! This release page lists all changes made to the project during the beta. For the migration guide, please refer to the documentation.

🚨 Breaking Changes

• Simplify mock function generic types and align with jest - by @​hi-ogawa in vitest-dev/vitest#4784 (a0c1d37)
• Remove --segfault-retry - by @​sheremet-va in vitest-dev/vitest#5514 (ed60e)
  • This flag was introduced to combat threads segfaults. Our current recommendation is to use the new default forks pool instead.
• Run suite hooks in a stack - by @​sheremet-va in vitest-dev/vitest#5609 (1277d)
  • This feels like a more sensible default. Especially with the new onTestFinished hook. This can make your tests run a little bit slower.
• Enable coverage.ignoreEmptyLines by default - by @​AriPerkkio in vitest-dev/vitest#5543 (31994)
  • ⚠️ This change may cause significant differences in your coverage results compared to Vitest v1. These changes are expected as coverage reporting is now more accurate. See vitest-dev/vitest#5423 for more details.
• Add correct location and snapshot fields in json reporter - by @​sheremet-va in vitest-dev/vitest#5434 (bcccc)
  • Previously, the location field pointed to the error location instead of the test location. Now it is aligned with jest and contains the line and column of a test function, but requires includeTaskLocation to be enabled.
• Update dependency chai to v5 - by renovate[bot] and @​sheremet-va in vitest-dev/vitest#5135 (73646)
• Remove watchExclude - by @​patak-dev in vitest-dev/vitest#5177 (d7371)
• Change default pool to 'forks' - by @​AriPerkkio in vitest-dev/vitest#5047 (7f8f9)
  • This change is done for compatibility issues
  • This pool may be slightly slower than previous threads pool: https://vitest.dev/guide/improving-performance.html#pool
• --merge-reports to support coverage - by @​AriPerkkio in vitest-dev/vitest#5736 (b7438)
• Add promise-based return assertions, do not auto-resolve returned promises - by @​sheremet-va in vitest-dev/vitest#5749 (5f710)
  • ⚠️ Vitest no longer unwraps promises in spy.mock.returns. If the function is async or returns a promise, it will always succeed and have a Promise in results. To make migration easier, we introduced spy.mock.settledResults that unwraps promises and expect().toHaveResolved() matcher that accepts unwrapped value.
• Do not exit process if global setup has failed - by @​sheremet-va

Superseded by #399.