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

chore(deps): update devdependencies #31

Merged
merged 1 commit into from
Apr 5, 2023
Merged

chore(deps): update devdependencies #31

merged 1 commit into from
Apr 5, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 17, 2023 •
edited

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@babel/core (source) 7.21.3 -> 7.21.4 age adoption passing confidence
@storybook/addon-essentials (source) 7.0.0-rc.3 -> 7.0.2 age adoption passing confidence
@storybook/addon-interactions (source) 7.0.0-rc.3 -> 7.0.2 age adoption passing confidence
@storybook/addon-links (source) 7.0.0-rc.3 -> 7.0.2 age adoption passing confidence
@storybook/blocks (source) 7.0.0-rc.3 -> 7.0.2 age adoption passing confidence
@storybook/nextjs (source) 7.0.0-rc.3 -> 7.0.2 age adoption passing confidence
@storybook/react (source) 7.0.0-rc.3 -> 7.0.2 age adoption passing confidence
@storybook/react-vite (source) 7.0.0-rc.3 -> 7.0.2 age adoption passing confidence
@storybook/testing-library 0.0.13 -> 0.1.0 age adoption passing confidence
@types/node (source) 18.15.3 -> 18.15.11 age adoption passing confidence
esbuild 0.17.11 -> 0.17.15 age adoption passing confidence
eslint (source) 8.36.0 -> 8.37.0 age adoption passing confidence
eslint-config-prettier 8.7.0 -> 8.8.0 age adoption passing confidence
prettier (source) 2.8.4 -> 2.8.7 age adoption passing confidence
storybook (source) 7.0.0-rc.3 -> 7.0.2 age adoption passing confidence
tailwindcss (source) 3.2.7 -> 3.3.1 age adoption passing confidence
token-transformer 0.0.30 -> 0.0.32 age adoption passing confidence
turbo (source) 1.8.3 -> 1.8.8 age adoption passing confidence
tw-colors 1.1.6 -> 1.2.0 age adoption passing confidence
typescript (source) 5.0.2 -> 5.0.3 age adoption passing confidence
vite (source) 4.2.0 -> 4.2.1 age adoption passing confidence
webpack 5.76.2 -> 5.77.0 age adoption passing confidence

Release Notes

babel/babel

v7.21.4

Compare Source

🐛 Bug Fix
  • babel-core, babel-helper-module-imports, babel-preset-typescript
  • babel-generator
💅 Polish
  • babel-helper-create-class-features-plugin, babel-plugin-proposal-class-properties, babel-plugin-transform-typescript, babel-traverse
🏠 Internal
storybookjs/storybook

v7.0.2

Compare Source

Storybook 7.0 is here! 🎉

7.0 contains hundreds more fixes, features, and tweaks. Browse the changelogs matching 7.0.0-alpha.*, 7.0.0-beta.*, and 7.0.0-rc.* for the full list of changes.

See our Migration guide to upgrade from earlier versions of Storybook.

Bug Fixes
  • CLI: Improve incompatible addons logic #​21883

v7.0.1

Compare Source

Bug Fixes
  • CLI: Always send error events if init doesn't succeed #​21879
  • CLI: Warn when community addons are incompatible with Storybook 7 #​21863
  • CLI: Fix migration summary message #​21862
  • CLI: Fix link to new framework API migrations #​21875
Maintenance
  • Angular: Remove deprecated component/propsMeta from story #​21807
  • Remove deprecated flags and properties #​21852
Dependencies

v7.0.0

Compare Source

Storybook 7.0 is here! 🎉

7.0 contains hundreds more fixes, features, and tweaks. Browse the changelogs matching 7.0.0-alpha.*, 7.0.0-beta.*, and 7.0.0-rc.* for the full list of changes.

See our Migration guide to upgrade from earlier versions of Storybook.

Full announcement and proper release to the latest npm tag coming soon. 😘

v7.0.0-rc.11

Compare Source

Features
  • CLI: Update stories glob in mdx codemod and not in mdx automigration #​21809
Bug Fixes
  • TS: Make sure components with interfaces or no props don't raise decorator assignability issues #​21833
  • Angular: Export applicationConfig decorator and adjust documentation for usage #​21851
  • Vite: Polyfill global by default #​21832
  • NextJS: Add explicit require.resolve calls to nextjs webpack loader config #​21834
  • Angular: Fix support on Windows when Storystore v7 is disabled #​21830
  • Angular: Fix module imported twice #​21770
Maintenance
  • CLI: Fix duplicated dependency warning for major version differences #​21850
  • Vite: downgrade remark related dependencies #​21836
Build
  • Build: Remove workflow we no longer use #​21829

v7.0.0-rc.10

Compare Source

Features
  • CLI: Warn the user for duplicated versions after automigrate #​21791
Bug Fixes
  • Addon-docs: Add remark-slug and remark-external-links to Vite builder #​21796
  • Blocks: Add children prop types #​21803
Maintenance
  • CLI: Upgrade to latest storybook/react-native version #​21811

v7.0.0-rc.9

Compare Source

Bug Fixes
  • CLI: Don't inline template functions in CSF2 to 3 codemod #​21539
  • ArgTypes: Fix JSdoc missing deprecated tag #​21794
  • UI: Scroll to highlighted search result #​21692
  • Actions: Fix clearing number of actions #​21760
  • UI: Fix cannot read properties of undefined at SearchResults #​21728
  • CLI: Fix an issue where port can be NaN #​21785
  • Docs: Exclude decorators by default from source #​21722
  • Docs: Fix ArgsTable crashing on subcomponents #​21769
  • Docs: Make Source transform API consistent #​21749
Maintenance
Dependency Upgrades

v7.0.0-rc.8

Compare Source

Bug Fixes
  • TypeScript: Fix missing env in StorybookConfig #​21732
  • Composition: Fix src of iframe unless the version changes #​21713
  • Composition: Fix the ref loading state showing up as empty instead #​21690
Build
  • Build: Add e2e-tests-dev task #​21546
  • Build: Fix CI after github.com SSH change #​21764

v7.0.0-rc.7

Compare Source

Bug Fixes
  • Svelte: Remount when resetting args in controls #​21659
  • CLI: Fix support for env vars when running dev/build commands #​21152
Maintenance
  • Core: upgrade esbuild, remove watch option from options #​21727

v7.0.0-rc.6

Compare Source

Bug Fixes
  • CLI: Fix sb add / mdx-gfm for addons with non-serializable values #​21731
  • CSF-plugin: Fix sourcemaps #​21704
  • React: Fix TS docgen for Functional Components #​21693
  • TypeScript: Add previewMainTemplate option to StorybookConfig #​21620
  • UI: Fix titles for addons/controls/panel tabs to support render fns and JSX elements #​21650
  • UI: Fix active state for menu iconbutton #​21666
  • CLI: Update renderer templates to provide correct typescript examples #​21647
  • Composition: Fix various CORS issues #​21682
  • Composition: Fix version switcher #​21621
Dependency Upgrades

v7.0.0-rc.5

Compare Source

Bug Fixes
  • UI: Fix IconButton to be in active state when corresponding menu is open #​21622
  • Angular: Fix sb init library support #​21675
  • CLI: Fix Vue3 template CSS #​21674
  • Core: fix storySort not reading from .mjs & .cjs files #​21637
  • Core: Fix cts/mts file extensions for config files #​21465
  • Core: Fix conflicting staticDirs case when -s flag is used #​21591
  • Angular: Fix source preview for angular stories #​21609

v7.0.0-rc.4

Compare Source

Features
  • Angular: Add "assets" build option #​21116
Bug Fixes
  • React: Fix missing framework options in shim #​21644
  • Docs: Update MDX Link component to be more user friendly #​21570
  • Links: Update LinkTo component #​21569
  • Vite: Allow vue files in importfn #​21550
  • Controls: Fix glitchy range control #​21459
  • CLI: Fix styling regression on CLI starter Introduction.mdx file #​21466
  • Addon-docs: Fix csf-plugin for Angular #​21629
  • Vite: Fix alias array converted incorrectly to an object #​21480
  • UI: Default white preview background #​21593
  • Vite: Fix dev and yarn pnp by adding lodash files to optimizeDeps.include #​21535
  • Composition: Fix blank page when ref is missing but specified in url #​21598
  • Core: Disable cache in dev-mode #​21574
  • Vite: Fix react-vite and projects with absolute path preview entries on Windows #​21545
  • UI: Change the way of preloading fonts #​21599
  • Core: Add preload and prefetch links for runtime.mjs and related files #​21594
  • React: Fix type inconsistencies in composeStories #​21575
  • UI: Fix WithTooltip to use visible prop instead of defaultVisible #​21589
Maintenance
Build
  • Build: Regen lockfiles #​21576
  • Build: Fix coverage job in CircleCI #​21633
  • Vite: Update sandbox template for vue2 script #​20750
storybookjs/testing-library

v0.1.0

Compare Source

🎉 This release contains work from a new contributor! 🎉

Thank you, Kasper Peulen (@​kasperpeulen), for all your work!

🚀 Enhancement
🐛 Bug Fix
Authors: 3
evanw/esbuild

v0.17.15

Compare Source

  • Allow keywords as type parameter names in mapped types (#​3033)

    TypeScript allows type keywords to be used as parameter names in mapped types. Previously esbuild incorrectly treated this as an error. Code that does this is now supported:

    type Foo = 'a' | 'b' | 'c'
type A = { [keyof in Foo]: number }
type B = { [infer in Foo]: number }
type C = { [readonly in Foo]: number }

  • Add annotations for re-exported modules in node (#​2486, #​3029)

    Node lets you import named imports from a CommonJS module using ESM import syntax. However, the allowed names aren't derived from the properties of the CommonJS module. Instead they are derived from an arbitrary syntax-only analysis of the CommonJS module's JavaScript AST.

    To accommodate node doing this, esbuild's ESM-to-CommonJS conversion adds a special non-executable "annotation" for node that describes the exports that node should expose in this scenario. It takes the form 0 && (module.exports = { ... }) and comes at the end of the file (0 && expr means expr is never evaluated).

    Previously esbuild didn't do this for modules re-exported using the export * from syntax. Annotations for these re-exports will now be added starting with this release:

    // Original input
export { foo } from './foo'
export * from './bar'

// Old output (with --format=cjs --platform=node)
...
0 && (module.exports = {
  foo
});

// New output (with --format=cjs --platform=node)
...
0 && (module.exports = {
  foo,
  ...require("./bar")
});

    Note that you need to specify both --format=cjs and --platform=node to get these node-specific annotations.

  • Avoid printing an unnecessary space in between a number and a . (#​3026)

    JavaScript typically requires a space in between a number token and a . token to avoid the . being interpreted as a decimal point instead of a member expression. However, this space is not required if the number token itself contains a decimal point, an exponent, or uses a base other than 10. This release of esbuild now avoids printing the unnecessary space in these cases:

    // Original input
foo(1000 .x, 0 .x, 0.1 .x, 0.0001 .x, 0xFFFF_0000_FFFF_0000 .x)

// Old output (with --minify)
foo(1e3 .x,0 .x,.1 .x,1e-4 .x,0xffff0000ffff0000 .x);

// New output (with --minify)
foo(1e3.x,0 .x,.1.x,1e-4.x,0xffff0000ffff0000.x);

  • Fix server-sent events with live reload when writing to the file system root (#​3027)

    This release fixes a bug where esbuild previously failed to emit server-sent events for live reload when outdir was the file system root, such as /. This happened because / is the only path on Unix that cannot have a trailing slash trimmed from it, which was fixed by improved path handling.

v0.17.14

Compare Source

  • Allow the TypeScript 5.0 const modifier in object type declarations (#​3021)

    The new TypeScript 5.0 const modifier was added to esbuild in version 0.17.5, and works with classes, functions, and arrow expressions. However, support for it wasn't added to object type declarations (e.g. interfaces) due to an oversight. This release adds support for these cases, so the following TypeScript 5.0 code can now be built with esbuild:

    interface Foo { <const T>(): T }
type Bar = { new <const T>(): T }

  • Implement preliminary lowering for CSS nesting (#​1945)

    Chrome has implemented the new CSS nesting specification in version 112, which is currently in beta but will become stable very soon. So CSS nesting is now a part of the web platform!

    This release of esbuild can now transform nested CSS syntax into non-nested CSS syntax for older browsers. The transformation relies on the :is() pseudo-class in many cases, so the transformation is only guaranteed to work when targeting browsers that support :is() (e.g. Chrome 88+). You'll need to set esbuild's target to the browsers you intend to support to tell esbuild to do this transformation. You will get a warning if you use CSS nesting syntax with a target which includes older browsers that don't support :is().

    The lowering transformation looks like this:

    /* Original input */
a.btn {
  color: #&#8203;333;
  &:hover { color: #&#8203;444 }
  &:active { color: #&#8203;555 }
}

/* New output (with --target=chrome88) */
a.btn {
  color: #&#8203;333;
}
a.btn:hover {
  color: #&#8203;444;
}
a.btn:active {
  color: #&#8203;555;
}

    More complex cases may generate the :is() pseudo-class:

    /* Original input */
div, p {
  .warning, .error {
    padding: 20px;
  }
}

/* New output (with --target=chrome88) */
:is(div, p) :is(.warning, .error) {
  padding: 20px;
}

    In addition, esbuild now has a special warning message for nested style rules that start with an identifier. This isn't allowed in CSS because the syntax would be ambiguous with the existing declaration syntax. The new warning message looks like this:

    ▲ [WARNING] A nested style rule cannot start with "p" because it looks like the start of a declaration [css-syntax-error]

    <stdin>:1:7:
      1 │ main { p { margin: auto } }
        │        ^
        ╵        :is(p)

  To start a nested style rule with an identifier, you need to wrap the identifier in ":is(...)" to
  prevent the rule from being parsed as a declaration.

    Keep in mind that the transformation in this release is a preliminary implementation. CSS has many features that interact in complex ways, and there may be some edge cases that don't work correctly yet.

  • Minification now removes unnecessary & CSS nesting selectors

    This release introduces the following CSS minification optimizations:

    /* Original input */
a {
  font-weight: bold;
  & {
    color: blue;
  }
  & :hover {
    text-decoration: underline;
  }
}

/* Old output (with --minify) */
a{font-weight:700;&{color:#&#8203;00f}& :hover{text-decoration:underline}}

/* New output (with --minify) */
a{font-weight:700;:hover{text-decoration:underline}color:#&#8203;00f}

  • Minification now removes duplicates from CSS selector lists

    This release introduces the following CSS minification optimization:

    /* Original input */
div, div { color: red }

/* Old output (with --minify) */
div,div{color:red}

/* New output (with --minify) */
div{color:red}

v0.17.13

Compare Source

  • Work around an issue with NODE_PATH and Go's WebAssembly internals (#​3001)

    Go's WebAssembly implementation returns EINVAL instead of ENOTDIR when using the readdir syscall on a file. This messes up esbuild's implementation of node's module resolution algorithm since encountering ENOTDIR causes esbuild to continue its search (since it's a normal condition) while other encountering other errors causes esbuild to fail with an I/O error (since it's an unexpected condition). You can encounter this issue in practice if you use node's legacy NODE_PATH feature to tell esbuild to resolve node modules in a custom directory that was not installed by npm. This release works around this problem by converting EINVAL into ENOTDIR for the readdir syscall.

  • Fix a minification bug with CSS @layer rules that have parsing errors (#​3016)

    CSS at-rules require either a {} block or a semicolon at the end. Omitting both of these causes esbuild to treat the rule as an unknown at-rule. Previous releases of esbuild had a bug that incorrectly removed unknown at-rules without any children during minification if the at-rule token matched an at-rule that esbuild can handle. Specifically cssnano can generate @layer rules with parsing errors, and empty @layer rules cannot be removed because they have side effects (@layer didn't exist when esbuild's CSS support was added, so esbuild wasn't written to handle this). This release changes esbuild to no longer discard @layer rules with parsing errors when minifying (the rule @layer c has a parsing error):

    /* Original input */
@&#8203;layer a {
  @&#8203;layer b {
    @&#8203;layer c
  }
}

/* Old output (with --minify) */
@&#8203;layer a.b;

/* New output (with --minify) */
@&#8203;layer a.b.c;

  • Unterminated strings in CSS are no longer an error

    The CSS specification provides rules for handling parsing errors. One of those rules is that user agents must close strings upon reaching the end of a line (i.e., before an unescaped line feed, carriage return or form feed character), but then drop the construct (declaration or rule) in which the string was found. For example:

    p {
  color: green;
  font-family: 'Courier New Times
  color: red;
  color: green;
}

    ...would be treated the same as:

    p { color: green; color: green; }

    ...because the second declaration (from font-family to the semicolon after color: red) is invalid and is dropped.

    Previously using this CSS with esbuild failed to build due to a syntax error, even though the code can be interpreted by a browser. With this release, the code now produces a warning instead of an error, and esbuild prints the invalid CSS such that it stays invalid in the output:

    /* esbuild's new non-minified output: */
p {
  color: green;
  font-family: 'Courier New Times
  color: red;
  color: green;
}
    /* esbuild's new minified output: */
p{font-family:'Courier New Times
color: red;color:green}

v0.17.12

Compare Source

  • Fix a crash when parsing inline TypeScript decorators (#​2991)

    Previously esbuild's TypeScript parser crashed when parsing TypeScript decorators if the definition of the decorator was inlined into the decorator itself:

    @&#8203;(function sealed(constructor: Function) {
  Object.seal(constructor);
  Object.seal(constructor.prototype);
})
class Foo {}

    This crash was not noticed earlier because this edge case did not have test coverage. The crash is fixed in this release.

eslint/eslint

v8.37.0

Compare Source

Features

Bug Fixes

  • 619f3fd fix: correctly handle null default config in RuleTester (#​17023) (Brad Zacher)
  • 1fbf118 fix: getFirstToken/getLastToken on comment-only node (#​16889) (Francesco Trotta)
  • 129e252 fix: Fix typo in logical-assignment-operators rule description (#​17000) (Francesco Trotta)

Documentation

Chores

prettier/eslint-config-prettier

v8.8.0

Compare Source

prettier/prettier

v2.8.7

Compare Source

diff

Allow multiple decorators on same getter/setter (#​14584 by @​fisker)
// Input
class A {
  @&#8203;decorator()
  get foo () {}
  
  @&#8203;decorator()
  set foo (value) {}
}

// Prettier 2.8.6
SyntaxError: Decorators cannot be applied to multiple get/set accessors of the same name. (5:3)
  3 |   get foo () {}
  4 |   
> 5 |   @&#8203;decorator()
    |   ^^^^^^^^^^^^
  6 |   set foo (value) {}
  7 | }

// Prettier 2.8.7
class A {
  @&#8203;decorator()
  get foo() {}

  @&#8203;decorator()
  set foo(value) {}
}

v2.8.6

Compare Source

diff

Allow decorators on private members and class expressions (#​14548 by @​fisker)
// Input
class A {
  @&#8203;decorator()
  #privateMethod () {}
}

// Prettier 2.8.5
SyntaxError: Decorators are not valid here. (2:3)
  1 | class A {
> 2 |   @&#8203;decorator()
    |   ^^^^^^^^^^^^
  3 |   #privateMethod () {}
  4 | }

// Prettier 2.8.6
class A {
  @&#8203;decorator()
  #privateMethod() {}
}

v2.8.5

Compare Source

diff

Support TypeScript 5.0 (#​14391 by @​fisker, #​13819 by @​fisker, @​sosukesuzuki)

TypeScript 5.0 introduces two new syntactic features:

  • const modifiers for type parameters
  • export type * declarations
Add missing parentheses for decorator (#​14393 by @​fisker)
// Input
class Person {
  @&#8203;(myDecoratorArray[0])
  greet() {}
}

// Prettier 2.8.4
class Person {
  @&#8203;myDecoratorArray[0]
  greet() {}
}

// Prettier 2.8.5
class Person {
  @&#8203;(myDecoratorArray[0])
  greet() {}
}
Add parentheses for TypeofTypeAnnotation to improve readability (#​14458 by @​fisker)
// Input
type A = (typeof node.children)[];

// Prettier 2.8.4
type A = typeof node.children[];

// Prettier 2.8.5
type A = (typeof node.children)[];
Support max_line_length=off when parsing .editorconfig (#​14516 by @​josephfrazier)

If an .editorconfig file is in your project and it sets max_line_length=off for the file you're formatting,
it will be interpreted as a printWidth of Infinity rather than being ignored
(which previously resulted in the default printWidth of 80 being applied, if not overridden by Prettier-specific configuration).

<!-- Input -->
<div className='HelloWorld' title={`You are visitor number ${ num }`} onMouseOver={onMouseOver}/>

<!-- Prettier 2.8.4 -->
<div
  className="HelloWorld"
  title={`You are visitor number ${num}`}
  onMouseOver={onMouseOver}
/>;

<!-- Prettier 2

</details>

---

### Configuration

📅 **Schedule**: Branch creation - "after 10pm every weekend,before 5am every weekend" in timezone Asia/Tokyo, Automerge - At any time (no schedule defined).

🚦 **Automerge**: Enabled.

♻ **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://togithub.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 [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://app.renovatebot.com/dashboard#github/ReoHakase/mystack).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNS45LjAiLCJ1cGRhdGVkSW5WZXIiOiIzNS4zMS40In0=-->

@renovate renovate bot added the 📦️ build Modification or additions to dependencies or build system label Mar 17, 2023
@vercel
Copy link

vercel bot commented Mar 17, 2023 •
edited

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
mystack-web ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 5, 2023 11:51am

@renovate renovate bot force-pushed the renovate/devdependencies branch from e398344 to e33b2b3 Compare March 20, 2023 09:46
@renovate renovate bot force-pushed the renovate/devdependencies branch from e33b2b3 to a55a973 Compare March 20, 2023 13:47
@renovate renovate bot force-pushed the renovate/devdependencies branch from a55a973 to 5e979e1 Compare March 20, 2023 19:58
@renovate renovate bot force-pushed the renovate/devdependencies branch from 5e979e1 to 6be23cd Compare March 20, 2023 22:13
@renovate renovate bot force-pushed the renovate/devdependencies branch from 6be23cd to 96eaba9 Compare March 21, 2023 08:25
@renovate renovate bot force-pushed the renovate/devdependencies branch from 96eaba9 to c9e3fde Compare March 21, 2023 12:46
@renovate renovate bot force-pushed the renovate/devdependencies branch from c9e3fde to 67149a5 Compare March 22, 2023 20:08
@renovate renovate bot force-pushed the renovate/devdependencies branch from 67149a5 to bf183e1 Compare March 23, 2023 14:42
@renovate renovate bot force-pushed the renovate/devdependencies branch from bf183e1 to 8a3633a Compare March 23, 2023 22:59
@renovate renovate bot force-pushed the renovate/devdependencies branch from 8a3633a to 0ac10d1 Compare March 24, 2023 12:09
@renovate renovate bot force-pushed the renovate/devdependencies branch from 0ac10d1 to 32cae41 Compare March 24, 2023 22:23
@renovate renovate bot force-pushed the renovate/devdependencies branch from 32cae41 to 5b5c5f8 Compare March 25, 2023 01:11
@renovate renovate bot force-pushed the renovate/devdependencies branch from 5b5c5f8 to 725b1af Compare March 25, 2023 07:30
@renovate renovate bot force-pushed the renovate/devdependencies branch from 725b1af to 9491fa2 Compare March 25, 2023 22:59
@renovate renovate bot force-pushed the renovate/devdependencies branch from 0d0bc98 to 3e20206 Compare March 29, 2023 18:22
@renovate renovate bot force-pushed the renovate/devdependencies branch from 3e20206 to 70438bb Compare March 29, 2023 23:10
@renovate renovate bot force-pushed the renovate/devdependencies branch from 70438bb to 4ccfce9 Compare March 30, 2023 20:45
@renovate renovate bot force-pushed the renovate/devdependencies branch from 4ccfce9 to b921dbe Compare March 30, 2023 21:06
@renovate renovate bot force-pushed the renovate/devdependencies branch from b921dbe to 7f7a796 Compare March 31, 2023 09:17
@renovate renovate bot force-pushed the renovate/devdependencies branch from 7f7a796 to f772ac2 Compare March 31, 2023 10:12
@renovate renovate bot force-pushed the renovate/devdependencies branch from f772ac2 to f4a02cc Compare March 31, 2023 13:21
@renovate renovate bot force-pushed the renovate/devdependencies branch from f4a02cc to 48708d1 Compare March 31, 2023 14:03
@renovate renovate bot force-pushed the renovate/devdependencies branch from 48708d1 to f6c70d8 Compare April 2, 2023 01:54
@renovate renovate bot force-pushed the renovate/devdependencies branch from f6c70d8 to 309a8bd Compare April 3, 2023 09:32
@renovate renovate bot force-pushed the renovate/devdependencies branch from 309a8bd to 13e0287 Compare April 3, 2023 10:40
@renovate renovate bot force-pushed the renovate/devdependencies branch from 13e0287 to ad82140 Compare April 4, 2023 03:47
@renovate renovate bot force-pushed the renovate/devdependencies branch from ad82140 to ed654e7 Compare April 5, 2023 11:50
@ReoHakase ReoHakase merged commit 63eb490 into main Apr 5, 2023
3 checks passed
@ReoHakase ReoHakase deleted the renovate/devdependencies branch April 5, 2023 13:51
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
📦️ build Modification or additions to dependencies or build system
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
1 participant
@ReoHakase