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.

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

chore(deps): update all non-major dependencies #17

Merged
merged 1 commit into from
Jun 26, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 26, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
esbuild 0.18.0 -> 0.18.8 age adoption passing confidence
eslint (source) 8.36.0 -> 8.43.0 age adoption passing confidence
got 12.6.0 -> 12.6.1 age adoption passing confidence
netlify-cli 15.0.0 -> 15.6.0 age adoption passing confidence
pnpm (source) 8.6.3 -> 8.6.4 age adoption passing confidence
prettier (source) 2.8.7 -> 2.8.8 age adoption passing confidence

Release Notes

evanw/esbuild (esbuild)

v0.18.8

Compare Source

  • Implement transforming async generator functions (#​2780)

    With this release, esbuild will now transform async generator functions into normal generator functions when the configured target environment doesn't support them. These functions behave similar to normal generator functions except that they use the Symbol.asyncIterator interface instead of the Symbol.iterator interface and the iteration methods return promises. Here's an example (helper functions are omitted):

    // Original code
    async function* foo() {
      yield Promise.resolve(1)
      await new Promise(r => setTimeout(r, 100))
      yield *[Promise.resolve(2)]
    }
    async function bar() {
      for await (const x of foo()) {
        console.log(x)
      }
    }
    bar()
    
    // New output (with --target=es6)
    function foo() {
      return __asyncGenerator(this, null, function* () {
        yield Promise.resolve(1);
        yield new __await(new Promise((r) => setTimeout(r, 100)));
        yield* __yieldStar([Promise.resolve(2)]);
      });
    }
    function bar() {
      return __async(this, null, function* () {
        try {
          for (var iter = __forAwait(foo()), more, temp, error; more = !(temp = yield iter.next()).done; more = false) {
            const x = temp.value;
            console.log(x);
          }
        } catch (temp) {
          error = [temp];
        } finally {
          try {
            more && (temp = iter.return) && (yield temp.call(iter));
          } finally {
            if (error)
              throw error[0];
          }
        }
      });
    }
    bar();

    This is an older feature that was added to JavaScript in ES2018 but I didn't implement the transformation then because it's a rarely-used feature. Note that esbuild already added support for transforming for await loops (the other part of the asynchronous iteration proposal) a year ago, so support for asynchronous iteration should now be complete.

    I have never used this feature myself and code that uses this feature is hard to come by, so this transformation has not yet been tested on real-world code. If you do write code that uses this feature, please let me know if esbuild's async generator transformation doesn't work with your code.

v0.18.7

Compare Source

  • Add support for using declarations in TypeScript 5.2+ (#​3191)

    TypeScript 5.2 (due to be released in August of 2023) will introduce using declarations, which will allow you to automatically dispose of the declared resources when leaving the current scope. You can read the TypeScript PR for this feature for more information. This release of esbuild adds support for transforming this syntax to target environments without support for using declarations (which is currently all targets other than esnext). Here's an example (helper functions are omitted):

    // Original code
    class Foo {
      [Symbol.dispose]() {
        console.log('cleanup')
      }
    }
    using foo = new Foo;
    foo.bar();
    
    // New output (with --target=es6)
    var _stack = [];
    try {
      var Foo = class {
        [Symbol.dispose]() {
          console.log("cleanup");
        }
      };
      var foo = __using(_stack, new Foo());
      foo.bar();
    } catch (_) {
      var _error = _, _hasError = true;
    } finally {
      __callDispose(_stack, _error, _hasError);
    }

    The injected helper functions ensure that the method named Symbol.dispose is called on new Foo when control exits the scope. Note that as with all new JavaScript APIs, you'll need to polyfill Symbol.dispose if it's not present before you use it. This is not something that esbuild does for you because esbuild only handles syntax, not APIs. Polyfilling it can be done with something like this:

    Symbol.dispose ||= Symbol('Symbol.dispose')

    This feature also introduces await using declarations which are like using declarations but they call await on the disposal method (not on the initializer). Here's an example (helper functions are omitted):

    // Original code
    class Foo {
      async [Symbol.asyncDispose]() {
        await new Promise(done => {
          setTimeout(done, 1000)
        })
        console.log('cleanup')
      }
    }
    await using foo = new Foo;
    foo.bar();
    
    // New output (with --target=es2022)
    var _stack = [];
    try {
      var Foo = class {
        async [Symbol.asyncDispose]() {
          await new Promise((done) => {
            setTimeout(done, 1e3);
          });
          console.log("cleanup");
        }
      };
      var foo = __using(_stack, new Foo(), true);
      foo.bar();
    } catch (_) {
      var _error = _, _hasError = true;
    } finally {
      var _promise = __callDispose(_stack, _error, _hasError);
      _promise && await _promise;
    }

    The injected helper functions ensure that the method named Symbol.asyncDispose is called on new Foo when control exits the scope, and that the returned promise is awaited. Similarly to Symbol.dispose, you'll also need to polyfill Symbol.asyncDispose before you use it.

  • Add a --line-limit= flag to limit line length (#​3170)

    Long lines are common in minified code. However, many tools and text editors can't handle long lines. This release introduces the --line-limit= flag to tell esbuild to wrap lines longer than the provided number of bytes. For example, --line-limit=80 tells esbuild to insert a newline soon after a given line reaches 80 bytes in length. This setting applies to both JavaScript and CSS, and works even when minification is disabled. Note that turning this setting on will make your files bigger, as the extra newlines take up additional space in the file (even after gzip compression).

v0.18.6

Compare Source

  • Fix tree-shaking of classes with decorators (#​3164)

    This release fixes a bug where esbuild incorrectly allowed tree-shaking on classes with decorators. Each decorator is a function call, so classes with decorators must never be tree-shaken. This bug was a regression that was unintentionally introduced in version 0.18.2 by the change that enabled tree-shaking of lowered private fields. Previously decorators were always lowered, and esbuild always considered the automatically-generated decorator code to be a side effect. But this is no longer the case now that esbuild analyzes side effects using the AST before lowering takes place. This bug was fixed by considering any decorator a side effect.

  • Fix a minification bug involving function expressions (#​3125)

    When minification is enabled, esbuild does limited inlining of const symbols at the top of a scope. This release fixes a bug where inlineable symbols were incorrectly removed assuming that they were inlined. They may not be inlined in cases where they were referenced by earlier constants in the body of a function expression. The declarations involved in these edge cases are now kept instead of being removed:

    // Original code
    {
      const fn = () => foo
      const foo = 123
      console.log(fn)
    }
    
    // Old output (with --minify-syntax)
    console.log((() => foo)());
    
    // New output (with --minify-syntax)
    {
      const fn = () => foo, foo = 123;
      console.log(fn);
    }

v0.18.5

Compare Source

  • Implement auto accessors (#​3009)

    This release implements the new auto-accessor syntax from the upcoming JavaScript decorators proposal. The auto-accessor syntax looks like this:

    class Foo {
      accessor foo;
      static accessor bar;
    }
    new Foo().foo = Foo.bar;

    This syntax is not yet a part of JavaScript but it was added to TypeScript in version 4.9. More information about this feature can be found in microsoft/TypeScript#​49705. Auto-accessors will be transformed if the target is set to something other than esnext:

    // Output (with --target=esnext)
    class Foo {
      accessor foo;
      static accessor bar;
    }
    new Foo().foo = Foo.bar;
    
    // Output (with --target=es2022)
    class Foo {
      #foo;
      get foo() {
        return this.#foo;
      }
      set foo(_) {
        this.#foo = _;
      }
      static #bar;
      static get bar() {
        return this.#bar;
      }
      static set bar(_) {
        this.#bar = _;
      }
    }
    new Foo().foo = Foo.bar;
    
    // Output (with --target=es2021)
    var _foo, _bar;
    class Foo {
      constructor() {
        __privateAdd(this, _foo, void 0);
      }
      get foo() {
        return __privateGet(this, _foo);
      }
      set foo(_) {
        __privateSet(this, _foo, _);
      }
      static get bar() {
        return __privateGet(this, _bar);
      }
      static set bar(_) {
        __privateSet(this, _bar, _);
      }
    }
    _foo = new WeakMap();
    _bar = new WeakMap();
    __privateAdd(Foo, _bar, void 0);
    new Foo().foo = Foo.bar;

    You can also now use auto-accessors with esbuild's TypeScript experimental decorator transformation, which should behave the same as decorating the underlying getter/setter pair.

    Please keep in mind that this syntax is not yet part of JavaScript. This release enables auto-accessors in .js files with the expectation that it will be a part of JavaScript soon. However, esbuild may change or remove this feature in the future if JavaScript ends up changing or removing this feature. Use this feature with caution for now.

  • Pass through JavaScript decorators (#​104)

    In this release, esbuild now parses decorators from the upcoming JavaScript decorators proposal and passes them through to the output unmodified (as long as the language target is set to esnext). Transforming JavaScript decorators to environments that don't support them has not been implemented yet. The only decorator transform that esbuild currently implements is still the TypeScript experimental decorator transform, which only works in .ts files and which requires "experimentalDecorators": true in your tsconfig.json file.

  • Static fields with assign semantics now use static blocks if possible

    Setting useDefineForClassFields to false in TypeScript requires rewriting class fields to assignment statements. Previously this was done by removing the field from the class body and adding an assignment statement after the class declaration. However, this also caused any private fields to also be lowered by necessity (in case a field initializer uses a private symbol, either directly or indirectly). This release changes this transform to use an inline static block if it's supported, which avoids needing to lower private fields in this scenario:

    // Original code
    class Test {
      static #foo = 123
      static bar = this.#foo
    }
    
    // Old output (with useDefineForClassFields=false)
    var _foo;
    const _Test = class _Test {
    };
    _foo = new WeakMap();
    __privateAdd(_Test, _foo, 123);
    _Test.bar = __privateGet(_Test, _foo);
    let Test = _Test;
    
    // New output (with useDefineForClassFields=false)
    class Test {
      static #foo = 123;
      static {
        this.bar = this.#foo;
      }
    }
  • Fix TypeScript experimental decorators combined with --mangle-props (#​3177)

    Previously using TypeScript experimental decorators combined with the --mangle-props setting could result in a crash, as the experimental decorator transform was not expecting a mangled property as a class member. This release fixes the crash so you can now combine both of these features together safely.

v0.18.4

Compare Source

  • Bundling no longer unnecessarily transforms class syntax (#​1360, #​1328, #​1524, #​2416)

    When bundling, esbuild automatically converts top-level class statements to class expressions. Previously this conversion had the unfortunate side-effect of also transforming certain other class-related syntax features to avoid correctness issues when the references to the class name within the class body. This conversion has been reworked to avoid doing this:

    // Original code
    export class Foo {
      static foo = () => Foo
    }
    
    // Old output (with --bundle)
    var _Foo = class {
    };
    var Foo = _Foo;
    __publicField(Foo, "foo", () => _Foo);
    
    // New output (with --bundle)
    var Foo = class _Foo {
      static foo = () => _Foo;
    };

    This conversion process is very complicated and has many edge cases (including interactions with static fields, static blocks, private class properties, and TypeScript experimental decorators). It should already be pretty robust but a change like this may introduce new unintentional behavior. Please report any issues with this upgrade on the esbuild bug tracker.

    You may be wondering why esbuild needs to do this at all. One reason to do this is that esbuild's bundler sometimes needs to lazily-evaluate a module. For example, a module may end up being both the target of a dynamic import() call and a static import statement. Lazy module evaluation is done by wrapping the top-level module code in a closure. To avoid a performance hit for static import statements, esbuild stores top-level exported symbols outside of the closure and references them directly instead of indirectly.

    Another reason to do this is that multiple JavaScript VMs have had and continue to have performance issues with TDZ (i.e. "temporal dead zone") checks. These checks validate that a let, or const, or class symbol isn't used before it's initialized. Here are two issues with well-known VMs:

    JavaScriptCore had a severe performance issue as their TDZ implementation had time complexity that was quadratic in the number of variables needing TDZ checks in the same scope (with the top-level scope typically being the worst offender). V8 has ongoing issues with TDZ checks being present throughout the code their JIT generates even when they have already been checked earlier in the same function or when the function in question has already been run (so the checks have already happened).

    Due to esbuild's parallel architecture, esbuild both a) needs to convert class statements into class expressions during parsing and b) doesn't yet know whether this module will need to be lazily-evaluated or not in the parser. So esbuild always does this conversion during bundling in case it's needed for correctness (and also to avoid potentially catastrophic performance issues due to bundling creating a large scope with many TDZ variables).

  • Enforce TDZ errors in computed class property keys (#​2045)

    JavaScript allows class property keys to be generated at run-time using code, like this:

    class Foo {
      static foo = 'foo'
      static [Foo.foo + '2'] = 2
    }

    Previously esbuild treated references to the containing class name within computed property keys as a reference to the partially-initialized class object. That meant code that attempted to reference properties of the class object (such as the code above) would get back undefined instead of throwing an error.

    This release rewrites references to the containing class name within computed property keys into code that always throws an error at run-time, which is how this JavaScript code is supposed to work. Code that does this will now also generate a warning. You should never write code like this, but it now should be more obvious when incorrect code like this is written.

  • Fix an issue with experimental decorators and static fields (#​2629)

    This release also fixes a bug regarding TypeScript experimental decorators and static class fields which reference the enclosing class name in their initializer. This affected top-level classes when bundling was enabled. Previously code that does this could crash because the class name wasn't initialized yet. This case should now be handled correctly:

    // Original code
    class Foo {
      @​someDecorator
      static foo = 'foo'
      static bar = Foo.foo.length
    }
    
    // Old output
    const _Foo = class {
      static foo = "foo";
      static bar = _Foo.foo.length;
    };
    let Foo = _Foo;
    __decorateClass([
      someDecorator
    ], Foo, "foo", 2);
    
    // New output
    const _Foo = class _Foo {
      static foo = "foo";
      static bar = _Foo.foo.length;
    };
    __decorateClass([
      someDecorator
    ], _Foo, "foo", 2);
    let Foo = _Foo;
  • Fix a minification regression with negative numeric properties (#​3169)

    Version 0.18.0 introduced a regression where computed properties with negative numbers were incorrectly shortened into a non-computed property when minification was enabled. This regression has been fixed:

    // Original code
    x = {
      [1]: 1,
      [-1]: -1,
      [NaN]: NaN,
      [Infinity]: Infinity,
      [-Infinity]: -Infinity,
    }
    
    // Old output (with --minify)
    x={1:1,-1:-1,NaN:NaN,1/0:1/0,-1/0:-1/0};
    
    // New output (with --minify)
    x={1:1,[-1]:-1,NaN:NaN,[1/0]:1/0,[-1/0]:-1/0};

v0.18.3

Compare Source

  • Fix a panic due to empty static class blocks (#​3161)

    This release fixes a bug where an internal invariant that was introduced in the previous release was sometimes violated, which then caused a panic. It happened when bundling code containing an empty static class block with both minification and bundling enabled.

v0.18.2

Compare Source

  • Lower static blocks when static fields are lowered (#​2800, #​2950, #​3025)

    This release fixes a bug where esbuild incorrectly did not lower static class blocks when static class fields needed to be lowered. For example, the following code should print 1 2 3 but previously printed 2 1 3 instead due to this bug:

    // Original code
    class Foo {
      static x = console.log(1)
      static { console.log(2) }
      static y = console.log(3)
    }
    
    // Old output (with --supported:class-static-field=false)
    class Foo {
      static {
        console.log(2);
      }
    }
    __publicField(Foo, "x", console.log(1));
    __publicField(Foo, "y", console.log(3));
    
    // New output (with --supported:class-static-field=false)
    class Foo {
    }
    __publicField(Foo, "x", console.log(1));
    console.log(2);
    __publicField(Foo, "y", console.log(3));
  • Use static blocks to implement --keep-names on classes (#​2389)

    This change fixes a bug where the name property could previously be incorrect within a class static context when using --keep-names. The problem was that the name property was being initialized after static blocks were run instead of before. This has been fixed by moving the name property initializer into a static block at the top of the class body:

    // Original code
    if (typeof Foo === 'undefined') {
      let Foo = class {
        static test = this.name
      }
      console.log(Foo.test)
    }
    
    // Old output (with --keep-names)
    if (typeof Foo === "undefined") {
      let Foo2 = /* @​__PURE__ */ __name(class {
        static test = this.name;
      }, "Foo");
      console.log(Foo2.test);
    }
    
    // New output (with --keep-names)
    if (typeof Foo === "undefined") {
      let Foo2 = class {
        static {
          __name(this, "Foo");
        }
        static test = this.name;
      };
      console.log(Foo2.test);
    }

    This change was somewhat involved, especially regarding what esbuild considers to be side-effect free. Some unused classes that weren't removed by tree shaking in previous versions of esbuild may now be tree-shaken. One example is classes with static private fields that are transformed by esbuild into code that doesn't use JavaScript's private field syntax. Previously esbuild's tree shaking analysis ran on the class after syntax lowering, but with this release it will run on the class before syntax lowering, meaning it should no longer be confused by class mutations resulting from automatically-generated syntax lowering code.

v0.18.1

Compare Source

  • Fill in null entries in input source maps (#​3144)

    If esbuild bundles input files with source maps and those source maps contain a sourcesContent array with null entries, esbuild previously copied those null entries over to the output source map. With this release, esbuild will now attempt to fill in those null entries by looking for a file on the file system with the corresponding name from the sources array. This matches esbuild's existing behavior that automatically generates the sourcesContent array from the file system if the entire sourcesContent array is missing.

  • Support /* @​__KEY__ */ comments for mangling property names (#​2574)

    Property mangling is an advanced feature that enables esbuild to minify certain property names, even though it's not possible to automatically determine that it's safe to do so. The safe property names are configured via regular expression such as --mangle-props=_$ (mangle all properties ending in _).

    Sometimes it's desirable to also minify strings containing property names, even though it's not possible to automatically determine which strings are property names. This release makes it possible to do this by annotating those strings with /* @​__KEY__ */. This is a convention that Terser added earlier this year, and which esbuild is now following too: https://github.com/terser/terser/pull/1365. Using it looks like this:

    // Original code
    console.log(
      [obj.mangle_, obj.keep],
      [obj.get('mangle_'), obj.get('keep')],
      [obj.get(/* @​__KEY__ */ 'mangle_'), obj.get(/* @​__KEY__ */ 'keep')],
    )
    
    // Old output (with --mangle-props=_$)
    console.log(
      [obj.a, obj.keep],
      [obj.get("mangle_"), obj.get("keep")],
      [obj.get(/* @​__KEY__ */ "mangle_"), obj.get(/* @​__KEY__ */ "keep")]
    );
    
    // New output (with --mangle-props=_$)
    console.log(
      [obj.a, obj.keep],
      [obj.get("mangle_"), obj.get("keep")],
      [obj.get(/* @​__KEY__ */ "a"), obj.get(/* @​__KEY__ */ "keep")]
    );
  • Support /* @​__NO_SIDE_EFFECTS__ */ comments for functions (#​3149)

    Rollup has recently added support for /* @​__NO_SIDE_EFFECTS__ */ annotations before functions to indicate that calls to these functions can be removed if the result is unused (i.e. the calls can be assumed to have no side effects). This release adds basic support for these to esbuild as well, which means esbuild will now parse these comments in input files and preserve them in output files. This should help people that use esbuild in combination with Rollup.

    Note that this doesn't necessarily mean esbuild will treat these calls as having no side effects, as esbuild's parallel architecture currently isn't set up to enable this type of cross-file tree-shaking information (tree-shaking decisions regarding a function call are currently local to the file they appear in). If you want esbuild to consider a function call to have no side effects, make sure you continue to annotate the function call with /* @​__PURE__ */ (which is the previously-established convention for communicating this).

eslint/eslint (eslint)

v8.43.0

Compare Source

Features

  • 14581ff feat: directive prologue detection and autofix condition in quotes (#​17284) (Francesco Trotta)
  • e50fac3 feat: add declaration loc to message in block-scoped-var (#​17252) (Milos Djermanovic)
  • 1b7faf0 feat: add skipJSXText option to no-irregular-whitespace rule (#​17182) (Azat S)

Bug Fixes

  • 5338b56 fix: normalize cwd passed to ESLint/FlatESLint constructor (#​17277) (Milos Djermanovic)
  • 54383e6 fix: Remove no-extra-parens autofix for potential directives (#​17022) (Francesco Trotta)

Documentation

Chores

v8.42.0

Compare Source

Features

  • b8448ff feat: correct no-useless-return behaviour in try statements (#​16996) (Nitin Kumar)

Bug Fixes

  • a589636 fix: Config with ignores and without files should not always apply (#​17181) (Milos Djermanovic)
  • c4fad17 fix: Correct ignore message for "node_modules" subfolders (#​17217) (Francesco Trotta)

Documentation

  • 01d7142 docs: Update README (GitHub Actions Bot)
  • e5182b7 docs: Update README (GitHub Actions Bot)

Chores

v8.41.0

Compare Source

Features
  • 880a431 feat: change default ignore pattern to **/node_modules/ in flat config (#​17184) (Milos Djermanovic)
  • 8bf5505 feat: expose shouldUseFlatConfig (#​17169) (Connor Prussin)
Bug Fixes
  • 4f5440d fix: incorrect warning message for ignored dotfiles (#​17196) (Milos Djermanovic)
  • 94da96c fix: unify LintMessage type (#​17076) (Brandon Mills)
  • 0c415cd fix: validate ignorePatterns constructor option in FlatESLint class (#​17139) (Milos Djermanovic)
  • 9682d66 fix: switch grapheme-splitter to graphemer (#​17160) (fisker Cheung)
Documentation
  • 7709b14 docs: Update README (GitHub Actions Bot)
  • 7f183e0 docs: Update triage process description (#​17157) (Nicholas C. Zakas)
  • b68346b docs: fix license to reflect relicensing of jshint (#​17165) (Stefan Bischof)
Chores

v8.40.0

Compare Source

Features
  • 5db7808 feat: improve flat config errors for invalid rule options and severities (#​17140) (Josh Goldberg ✨)
  • f5574dc feat: Add findConfigFile() method to FlatESLint (#​17142) (Nicholas C. Zakas)
  • e52b98b feat: add sourceCode property to the rule context (#​17107) (Nitin Kumar)
  • 1468f5b feat: add physicalFilename property to the rule context (#​17111) (Nitin Kumar)
  • 0df4d4f feat: add cwd to rule context (#​17106) (Nitin Kumar)
  • 52018f2 feat: add filename property to the rule context (#​17108) (Nitin Kumar)
  • 559ff4e feat: add new omitLastInOneLineClassBody option to the semi rule (#​17105) (Nitin Kumar)
Bug Fixes
  • f076e54 fix: Ensure FlatESLint#findConfigFile() doesn't throw. (#​17151) (Nicholas C. Zakas)
Documentation
  • e980bf3 docs: Update README (GitHub Actions Bot)
  • e92a6fc docs: Update README (GitHub Actions Bot)
  • af5fe64 docs: Fix custom rule schema docs (#​17115) (Adam Jones)
  • 4a352a9 docs: explain how to include predefined globals (#​17114) (Marcus Wyatt)
  • 5ea15d9 docs: add mastodon link in readme (#​17110) (唯然)
Chores

v8.39.0

Compare Source

Features

  • 3f7af9f feat: Implement SourceCode#markVariableAsUsed() (#​17086) (Nicholas C. Zakas)

Documentation

  • 6987dc5 docs: Fix formatting in Custom Rules docs (#​17097) (Milos Djermanovic)
  • 4ee92e5 docs: Update README (GitHub Actions Bot)
  • d8e9887 docs: Custom Rules cleanup/expansion (#​16906) (Ben Perlmutter)
  • 1fea279 docs: Clarify how to add to tsc agenda (#​17084) (Nicholas C. Zakas)
  • 970ef1c docs: Update triage board location (Nicholas C. Zakas)
  • 6d8bffd docs: Update README (GitHub Actions Bot)

Chores

v8.38.0

Compare Source

Features
  • a1d561d feat: Move getDeclaredVariables and getAncestors to SourceCode (#​17059) (Nicholas C. Zakas)
Bug Fixes
  • 1c1ece2 fix: do not report on RegExp(...args) in require-unicode-regexp (#​17037) (Francesco Trotta)
Documentation
  • 7162d34 docs: Mention new config system is complete (#​17068) (Nicholas C. Zakas)
  • 0fd6bb2 docs: Update README (GitHub Actions Bot)
  • c83531c docs: Update/remove external links, eg. point to eslint-community (#​17061) (Pelle Wessman)
  • a3aa6f5 docs: Clarify no-div-regex rule docs (#​17051) (Francesco Trotta)
  • b0f11cf docs: Update README (GitHub Actions Bot)
  • da8d52a docs: Update the second object instance for the "no-new" rule (#​17020) (Ahmadou Waly NDIAYE)
  • 518130a docs: switch language based on current path (#​16687) (Percy Ma)
  • 24206c4 docs: Update README (GitHub Actions Bot)
Chores

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

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.

👻 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 Mend Renovate. View repository job log here.

@renovate renovate bot merged commit ee805ac into main Jun 26, 2023
5 checks passed
@renovate renovate bot deleted the renovate/all-minor-patch branch June 26, 2023 04:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants