vikunja/frontend
Archived
6
39
Fork 48
Code Issues 1 Pull Requests 4 Projects Releases 26 Activity

chore(deps): update dev-dependencies #3690

Merged
konrad merged 1 commits from renovate/dev-dependencies into main 2023-07-18 08:50:39 +00:00
Conversation 1 Commits 1 Files Changed 2 +164 -162
renovate commented 2023-07-18 00:05:01 +00:00
Member
Copy Link

This PR contains the following updates:

Package Type Update Change
@typescript-eslint/eslint-plugin devDependencies minor 6.0.0 -> 6.1.0
@typescript-eslint/parser devDependencies minor 6.0.0 -> 6.1.0
esbuild devDependencies patch 0.18.13 -> 0.18.14
happy-dom devDependencies minor 10.3.2 -> 10.5.1
rollup (source) devDependencies patch 3.26.2 -> 3.26.3

Release Notes

typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v6.1.0

Compare Source

Bug Fixes
  • eslint-plugin: [comma-dangle] fixed crash from undefined predicate.ignore (#​7223) (d368164)
  • eslint-plugin: [no-floating-promises] false negative calling .then with second argument undefined (#​6881) (606a52c), closes #​6850
  • eslint-plugin: [no-floating-promises] finally should be transparent to unhandled promises (#​7092) (2a4421c)
  • eslint-plugin: [no-unnecessary-type-constraint] correctly fix in cts/mts files (#​6795) (1404796)
  • eslint-plugin: [no-unused-vars] check if any variable definition is exported (#​6873) (587ac30), closes #​6188
  • eslint-plugin: fix schemas across several rules and add schema tests (#​6947) (dd31bed)
  • eslint-plugin: include the rules types in the package (#​7215) (a3da11d)
Features
  • typescript-estree: add EXPERIMENTAL_useProjectService option to use TypeScript project service (#​6754) (6d3d162)

You can read about our versioning strategy and releases on our website.

typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v6.1.0

Compare Source

Features
  • typescript-estree: add EXPERIMENTAL_useProjectService option to use TypeScript project service (#​6754) (6d3d162)

You can read about our versioning strategy and releases on our website.

evanw/esbuild

v0.18.14

Compare Source

  • Implement local CSS names (#​20)

    This release introduces two new loaders called global-css and local-css and two new pseudo-class selectors :local() and :global(). This is a partial implementation of the popular CSS modules approach for avoiding unintentional name collisions in CSS. I'm not calling this feature "CSS modules" because although some people in the community call it that, other people in the community have started using "CSS modules" to refer to something completely different and now CSS modules is an overloaded term.

    Here's how this new local CSS name feature works with esbuild:

    • Identifiers that look like .className and #idName are global with the global-css loader and local with the local-css loader. Global identifiers are the same across all files (the way CSS normally works) but local identifiers are different between different files. If two separate CSS files use the same local identifier .button, esbuild will automatically rename one of them so that they don't collide. This is analogous to how esbuild automatically renames JS local variables with the same name in separate JS files to avoid name collisions.

    • It only makes sense to use local CSS names with esbuild when you are also using esbuild's bundler to bundle JS files that import CSS files. When you do that, esbuild will generate one export for each local name in the CSS file. The JS code can import these names and use them when constructing HTML DOM. For example:

      // app.js
import { outerShell } from './app.css'
const div = document.createElement('div')
div.className = outerShell
document.body.appendChild(div)

      /* app.css */
.outerShell {
  position: absolute;
  inset: 0;
}

      When you bundle this with esbuild app.js --bundle --loader:.css=local-css --outdir=out you'll now get this (notice how the local CSS name outerShell has been renamed):

      // out/app.js
(() => {
  // app.css
  var outerShell = "app_outerShell";

  // app.js
  var div = document.createElement("div");
  div.className = outerShell;
  document.body.appendChild(div);
})();

      /* out/app.css */
.app_outerShell {
  position: absolute;
  inset: 0;
}

      This feature only makes sense to use when bundling is enabled both because your code needs to import the renamed local names so that it can use them, and because esbuild needs to be able to process all CSS files containing local names in a single bundling operation so that it can successfully rename conflicting local names to avoid collisions.

    • If you are in a global CSS file (with the global-css loader) you can create a local name using :local(), and if you are in a local CSS file (with the local-css loader) you can create a global name with :global(). So the choice of the global-css loader vs. the local-css loader just sets the default behavior for identifiers, but you can override it on a case-by-case basis as necessary. For example:

      :local(.button) {
  color: red;
}
:global(.button) {
  color: blue;
}

      Processing this CSS file with esbuild with either the global-css or local-css loader will result in something like this:

      .stdin_button {
  color: red;
}
.button {
  color: blue;
}

    • The names that esbuild generates for local CSS names are an implementation detail and are not intended to be hard-coded anywhere. The only way you should be referencing the local CSS names in your JS or HTML is with an import statement in JS that is bundled with esbuild, as demonstrated above. For example, when --minify is enabled esbuild will use a different name generation algorithm which generates names that are as short as possible (analogous to how esbuild minifies local identifiers in JS).

    • You can easily use both global CSS files and local CSS files simultaneously if you give them different file extensions. For example, you could pass --loader:.css=global-css and --loader:.module.css=local-css to esbuild so that .css files still use global names by default but .module.css files use local names by default.

    • Keep in mind that the css loader is different than the global-css loader. The :local and :global annotations are not enabled with the css loader and will be passed through unchanged. This allows you to have the option of using esbuild to process CSS containing while preserving these annotations. It also means that local CSS names are disabled by default for now (since the css loader is currently the default for CSS files). The :local and :global syntax may be enabled by default in a future release.

    Note that esbuild's implementation does not currently have feature parity with other implementations of modular CSS in similar tools. This is only a preliminary release with a partial implementation that includes some basic behavior to get the process started. Additional behavior may be added in future releases. In particular, this release does not implement:

    • The composes pragma
    • Tree shaking for unused local CSS
    • Local names for keyframe animations, grid lines, @container, @counter-style, etc.

    Issue #​20 (the issue for this feature) is esbuild's most-upvoted issue! While this release still leaves that issue open, it's an important first step in that direction.

  • Parse :is, :has, :not, and :where in CSS

    With this release, esbuild will now parse the contents of these pseudo-class selectors as a selector list. This means you will now get syntax warnings within these selectors for invalid selector syntax. It also means that esbuild's CSS nesting transform behaves slightly differently than before because esbuild is now operating on an AST instead of a token stream. For example:

    /* Original code */
div {
  :where(.foo&) {
    color: red;
  }
}

/* Old output (with --target=chrome90) */
:where(.foo:is(div)) {
  color: red;
}

/* New output (with --target=chrome90) */
:where(div.foo) {
  color: red;
}
capricorn86/happy-dom

v10.5.1

Compare Source

👷‍♂️ Patch fixes
  • Fixes problem where HTMLIFrameElement fails to load page. The problem was most likely that some libraries overrides the Document.defaultView property somehow, making Document.defaultView.constructor not being the Window constructor. (#​992)

v10.5.0

Compare Source

🎨 Features
  • Fixes issue where CSS values with parentheses wasn't correctly parsed if the values also contained a comma. (#​976)
  • This fix should also fix a problem related to parsing a CSS string that ends with a variable setter. (#​670)

Thank you @​malko for your contribution!

v10.4.0

Compare Source

🎨 Features
  • Adds support for MouseEvent.movementX and MouseEvent.movementY. (#​953)

Thank you @​mertcan for your contribution!

rollup/rollup

v3.26.3

Compare Source

2023-07-17

Bug Fixes
  • Do not pass external modules to manualChunks to avoid breaking existing configs (#​5068)
Pull Requests

Configuration

📅 Schedule: Branch creation - "before 2am" (UTC), 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • 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 | |---|---|---|---| | [@typescript-eslint/eslint-plugin](https://github.com/typescript-eslint/typescript-eslint) | devDependencies | minor | [`6.0.0` -> `6.1.0`](https://renovatebot.com/diffs/npm/@typescript-eslint%2feslint-plugin/6.0.0/6.1.0) | | [@typescript-eslint/parser](https://github.com/typescript-eslint/typescript-eslint) | devDependencies | minor | [`6.0.0` -> `6.1.0`](https://renovatebot.com/diffs/npm/@typescript-eslint%2fparser/6.0.0/6.1.0) | | [esbuild](https://github.com/evanw/esbuild) | devDependencies | patch | [`0.18.13` -> `0.18.14`](https://renovatebot.com/diffs/npm/esbuild/0.18.13/0.18.14) | | [happy-dom](https://github.com/capricorn86/happy-dom) | devDependencies | minor | [`10.3.2` -> `10.5.1`](https://renovatebot.com/diffs/npm/happy-dom/10.3.2/10.5.1) | | [rollup](https://rollupjs.org/) ([source](https://github.com/rollup/rollup)) | devDependencies | patch | [`3.26.2` -> `3.26.3`](https://renovatebot.com/diffs/npm/rollup/3.26.2/3.26.3) | --- ### Release Notes <details> <summary>typescript-eslint/typescript-eslint (@&#8203;typescript-eslint/eslint-plugin)</summary> ### [`v6.1.0`](https://github.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#&#8203;610-httpsgithubcomtypescript-eslinttypescript-eslintcomparev600v610-2023-07-17) [Compare Source](https://github.com/typescript-eslint/typescript-eslint/compare/v6.0.0...v6.1.0) ##### Bug Fixes - **eslint-plugin:** \[comma-dangle] fixed crash from undefined predicate.ignore ([#&#8203;7223](https://github.com/typescript-eslint/typescript-eslint/issues/7223)) ([d368164](https://github.com/typescript-eslint/typescript-eslint/commit/d368164478a8b141ad6b1c4ea5088fdc639ccafe)) - **eslint-plugin:** \[no-floating-promises] false negative calling .then with second argument undefined ([#&#8203;6881](https://github.com/typescript-eslint/typescript-eslint/issues/6881)) ([606a52c](https://github.com/typescript-eslint/typescript-eslint/commit/606a52cefcecd594df6edc359bff291b835169f2)), closes [#&#8203;6850](https://github.com/typescript-eslint/typescript-eslint/issues/6850) - **eslint-plugin:** \[no-floating-promises] finally should be transparent to unhandled promises ([#&#8203;7092](https://github.com/typescript-eslint/typescript-eslint/issues/7092)) ([2a4421c](https://github.com/typescript-eslint/typescript-eslint/commit/2a4421ccf072f866bb6c2dadab967aa69ac9bf4a)) - **eslint-plugin:** \[no-unnecessary-type-constraint] correctly fix in cts/mts files ([#&#8203;6795](https://github.com/typescript-eslint/typescript-eslint/issues/6795)) ([1404796](https://github.com/typescript-eslint/typescript-eslint/commit/14047963d79e4d4a783854e2826a30004fa34570)) - **eslint-plugin:** \[no-unused-vars] check if any variable definition is exported ([#&#8203;6873](https://github.com/typescript-eslint/typescript-eslint/issues/6873)) ([587ac30](https://github.com/typescript-eslint/typescript-eslint/commit/587ac306d9e53736ebe799f5b9edcb7dd030eed6)), closes [#&#8203;6188](https://github.com/typescript-eslint/typescript-eslint/issues/6188) - **eslint-plugin:** fix schemas across several rules and add schema tests ([#&#8203;6947](https://github.com/typescript-eslint/typescript-eslint/issues/6947)) ([dd31bed](https://github.com/typescript-eslint/typescript-eslint/commit/dd31bed1e921531abe039180c9aeccbd56934601)) - **eslint-plugin:** include the rules types in the package ([#&#8203;7215](https://github.com/typescript-eslint/typescript-eslint/issues/7215)) ([a3da11d](https://github.com/typescript-eslint/typescript-eslint/commit/a3da11d09b1d119fd5bc4cd776474e2520d7fefd)) ##### Features - **typescript-estree:** add EXPERIMENTAL_useProjectService option to use TypeScript project service ([#&#8203;6754](https://github.com/typescript-eslint/typescript-eslint/issues/6754)) ([6d3d162](https://github.com/typescript-eslint/typescript-eslint/commit/6d3d162ce032ebcf5f892a4edfb897797fc96191)) You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website. </details> <details> <summary>typescript-eslint/typescript-eslint (@&#8203;typescript-eslint/parser)</summary> ### [`v6.1.0`](https://github.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#&#8203;610-httpsgithubcomtypescript-eslinttypescript-eslintcomparev600v610-2023-07-17) [Compare Source](https://github.com/typescript-eslint/typescript-eslint/compare/v6.0.0...v6.1.0) ##### Features - **typescript-estree:** add EXPERIMENTAL_useProjectService option to use TypeScript project service ([#&#8203;6754](https://github.com/typescript-eslint/typescript-eslint/issues/6754)) ([6d3d162](https://github.com/typescript-eslint/typescript-eslint/commit/6d3d162ce032ebcf5f892a4edfb897797fc96191)) You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website. </details> <details> <summary>evanw/esbuild</summary> ### [`v0.18.14`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#&#8203;01814) [Compare Source](https://github.com/evanw/esbuild/compare/v0.18.13...v0.18.14) - Implement local CSS names ([#&#8203;20](https://github.com/evanw/esbuild/issues/20)) This release introduces two new loaders called `global-css` and `local-css` and two new pseudo-class selectors `:local()` and `:global()`. This is a partial implementation of the popular [CSS modules](https://github.com/css-modules/css-modules) approach for avoiding unintentional name collisions in CSS. I'm not calling this feature "CSS modules" because although some people in the community call it that, other people in the community have started using "CSS modules" to refer to [something completely different](https://github.com/WICG/webcomponents/blob/60c9f682b63c622bfa0d8222ea6b1f3b659e007c/proposals/css-modules-v1-explainer.md) and now CSS modules is an overloaded term. Here's how this new local CSS name feature works with esbuild: - Identifiers that look like `.className` and `#idName` are global with the `global-css` loader and local with the `local-css` loader. Global identifiers are the same across all files (the way CSS normally works) but local identifiers are different between different files. If two separate CSS files use the same local identifier `.button`, esbuild will automatically rename one of them so that they don't collide. This is analogous to how esbuild automatically renames JS local variables with the same name in separate JS files to avoid name collisions. - It only makes sense to use local CSS names with esbuild when you are also using esbuild's bundler to bundle JS files that import CSS files. When you do that, esbuild will generate one export for each local name in the CSS file. The JS code can import these names and use them when constructing HTML DOM. For example: ```js // app.js import { outerShell } from './app.css' const div = document.createElement('div') div.className = outerShell document.body.appendChild(div) ``` ```css /* app.css */ .outerShell { position: absolute; inset: 0; } ``` When you bundle this with `esbuild app.js --bundle --loader:.css=local-css --outdir=out` you'll now get this (notice how the local CSS name `outerShell` has been renamed): ```js // out/app.js (() => { // app.css var outerShell = "app_outerShell"; // app.js var div = document.createElement("div"); div.className = outerShell; document.body.appendChild(div); })(); ``` ```css /* out/app.css */ .app_outerShell { position: absolute; inset: 0; } ``` This feature only makes sense to use when bundling is enabled both because your code needs to `import` the renamed local names so that it can use them, and because esbuild needs to be able to process all CSS files containing local names in a single bundling operation so that it can successfully rename conflicting local names to avoid collisions. - If you are in a global CSS file (with the `global-css` loader) you can create a local name using `:local()`, and if you are in a local CSS file (with the `local-css` loader) you can create a global name with `:global()`. So the choice of the `global-css` loader vs. the `local-css` loader just sets the default behavior for identifiers, but you can override it on a case-by-case basis as necessary. For example: ```css :local(.button) { color: red; } :global(.button) { color: blue; } ``` Processing this CSS file with esbuild with either the `global-css` or `local-css` loader will result in something like this: ```css .stdin_button { color: red; } .button { color: blue; } ``` - The names that esbuild generates for local CSS names are an implementation detail and are not intended to be hard-coded anywhere. The only way you should be referencing the local CSS names in your JS or HTML is with an `import` statement in JS that is bundled with esbuild, as demonstrated above. For example, when `--minify` is enabled esbuild will use a different name generation algorithm which generates names that are as short as possible (analogous to how esbuild minifies local identifiers in JS). - You can easily use both global CSS files and local CSS files simultaneously if you give them different file extensions. For example, you could pass `--loader:.css=global-css` and `--loader:.module.css=local-css` to esbuild so that `.css` files still use global names by default but `.module.css` files use local names by default. - Keep in mind that the `css` loader is different than the `global-css` loader. The `:local` and `:global` annotations are not enabled with the `css` loader and will be passed through unchanged. This allows you to have the option of using esbuild to process CSS containing while preserving these annotations. It also means that local CSS names are disabled by default for now (since the `css` loader is currently the default for CSS files). The `:local` and `:global` syntax may be enabled by default in a future release. Note that esbuild's implementation does not currently have feature parity with other implementations of modular CSS in similar tools. This is only a preliminary release with a partial implementation that includes some basic behavior to get the process started. Additional behavior may be added in future releases. In particular, this release does not implement: - The `composes` pragma - Tree shaking for unused local CSS - Local names for keyframe animations, grid lines, `@container`, `@counter-style`, etc. Issue [#&#8203;20](https://github.com/evanw/esbuild/issues/20) (the issue for this feature) is esbuild's most-upvoted issue! While this release still leaves that issue open, it's an important first step in that direction. - Parse `:is`, `:has`, `:not`, and `:where` in CSS With this release, esbuild will now parse the contents of these pseudo-class selectors as a selector list. This means you will now get syntax warnings within these selectors for invalid selector syntax. It also means that esbuild's CSS nesting transform behaves slightly differently than before because esbuild is now operating on an AST instead of a token stream. For example: ```css /* Original code */ div { :where(.foo&) { color: red; } } /* Old output (with --target=chrome90) */ :where(.foo:is(div)) { color: red; } /* New output (with --target=chrome90) */ :where(div.foo) { color: red; } ``` </details> <details> <summary>capricorn86/happy-dom</summary> ### [`v10.5.1`](https://github.com/capricorn86/happy-dom/releases/tag/v10.5.1) [Compare Source](https://github.com/capricorn86/happy-dom/compare/v10.5.0...v10.5.1) ##### :construction_worker_man: Patch fixes - Fixes problem where `HTMLIFrameElement` fails to load page. The problem was most likely that some libraries overrides the `Document.defaultView` property somehow, making `Document.defaultView.constructor` not being the `Window` constructor. ([#&#8203;992](https://github.com/capricorn86/happy-dom/issues/992)) ### [`v10.5.0`](https://github.com/capricorn86/happy-dom/releases/tag/v10.5.0) [Compare Source](https://github.com/capricorn86/happy-dom/compare/v10.4.0...v10.5.0) ##### :art: Features - Fixes issue where CSS values with parentheses wasn't correctly parsed if the values also contained a comma. ([#&#8203;976](https://github.com/capricorn86/happy-dom/issues/976)) - This fix should also fix a problem related to parsing a CSS string that ends with a variable setter. ([#&#8203;670](https://github.com/capricorn86/happy-dom/issues/670)) *** Thank you [@&#8203;malko](https://github.com/malko) for your contribution! ### [`v10.4.0`](https://github.com/capricorn86/happy-dom/releases/tag/v10.4.0) [Compare Source](https://github.com/capricorn86/happy-dom/compare/v10.3.2...v10.4.0) ##### :art: Features - Adds support for `MouseEvent.movementX` and `MouseEvent.movementY`. ([#&#8203;953](https://github.com/capricorn86/happy-dom/issues/953)) *** Thank you [@&#8203;mertcan](https://github.com/mertcan) for your contribution! </details> <details> <summary>rollup/rollup</summary> ### [`v3.26.3`](https://github.com/rollup/rollup/blob/HEAD/CHANGELOG.md#&#8203;3263) [Compare Source](https://github.com/rollup/rollup/compare/v3.26.2...v3.26.3) *2023-07-17* ##### Bug Fixes - Do not pass external modules to `manualChunks` to avoid breaking existing configs ([#&#8203;5068](https://github.com/rollup/rollup/issues/5068)) ##### Pull Requests - [#&#8203;5056](https://github.com/rollup/rollup/pull/5056): chore(deps): lock file maintenance minor/patch updates ([@&#8203;renovate](https://github.com/renovate)\[bot]) - [#&#8203;5059](https://github.com/rollup/rollup/pull/5059): chore(config): migrate renovate config ([@&#8203;renovate](https://github.com/renovate)\[bot]) - [#&#8203;5064](https://github.com/rollup/rollup/pull/5064): chore(deps): update dependency prettier to v3 ([@&#8203;renovate](https://github.com/renovate)\[bot]) - [#&#8203;5065](https://github.com/rollup/rollup/pull/5065): chore(deps): update typescript-eslint monorepo to v6 (major) ([@&#8203;renovate](https://github.com/renovate)\[bot]) - [#&#8203;5068](https://github.com/rollup/rollup/pull/5068): fix: don't pass external modules to the manualChunks function ([@&#8203;TrickyPi](https://github.com/TrickyPi)) </details> --- ### Configuration 📅 **Schedule**: Branch creation - "before 2am" (UTC), 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. 👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://github.com/renovatebot/renovate/discussions) if that's undesired. --- - [ ] <!-- 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:eyJjcmVhdGVkSW5WZXIiOiIzNS4yNC42IiwidXBkYXRlZEluVmVyIjoiMzUuMjQuNiJ9-->
renovate added the
dependencies
 label 2023-07-18 00:05:01 +00:00
frederick commented 2023-07-18 00:15:37 +00:00
Member
Copy Link

Hi renovate!

Thank you for creating a PR!

I've deployed the changes of this PR on a preview environment under this URL: https://3690-renovate-dev-dependencies--vikunja-frontend-preview.netlify.app

You can use this url to view the changes live and test them out.
You will need to manually connect this to an api running somehwere. The easiest to use is https://try.vikunja.io/.

Have a nice day!

Beep boop, I'm a bot.

Hi renovate! Thank you for creating a PR! I've deployed the changes of this PR on a preview environment under this URL: https://3690-renovate-dev-dependencies--vikunja-frontend-preview.netlify.app You can use this url to view the changes live and test them out. You will need to manually connect this to an api running somehwere. The easiest to use is https://try.vikunja.io/. Have a nice day! > Beep boop, I'm a bot.
renovate force-pushed renovate/dev-dependencies from 4dc2521941 to f086c47c71 2023-07-18 05:04:49 +00:00 Compare
konrad merged commit f786c2b8a2 into main 2023-07-18 08:50:39 +00:00
konrad deleted branch renovate/dev-dependencies 2023-07-18 08:50:39 +00:00
This repo is archived. You cannot comment on pull requests.
Reviewers
No reviewers
Labels
Clear labels   
area/internal-code

   
changes requested

   
confirmed

   
dependencies

   
duplicate

This issue or pull request already exists

  
good first issue

   
help wanted

Need some help

  
hosting

   
invalid

Something is wrong

  
kind/bug

Something is not working

  
kind/feature

New feature

  
question

More information is needed

  
wontfix

This won't be fixed

No Label
area/internal-code
changes requested
confirmed
dependencies
duplicate
good first issue
help wanted
hosting
invalid
kind/bug
kind/feature
question
wontfix
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
2 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: vikunja/frontend#3690
No description provided.
Delete Branch "renovate/dev-dependencies"

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?