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

Update fimbullinter monorepo to ^0.24.0 #24

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 12, 2021

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@fimbul/valtyr ^0.21.0 -> ^0.24.0 age adoption passing confidence
@fimbul/wotan ^0.21.0 -> ^0.24.0 age adoption passing confidence

Release Notes

fimbullinter/wotan

v0.24.0

Compare Source

🎉 This release contains two major features: caching and code fixes in the LanguageService plugin.

⚠️ Breaking Changes:

The changes in the LanguageService plugin require that you update the @fimbul/mithotyn dependency and the fimbullinter.vscode-plugin VSCode plugin if you were using one of them.

Features:

  • new rule: no-object-spread-of-iterable warns about spreading an array into an object
  • new rule: no-implicit-tostring warns about implicit string coercion of certain types
  • new CLI option: --cache enables caching for fast incremental linting. Read more about caching
  • the LanguageService plugin uses caching to speed up linting in your editor
  • the LanguageService plugin now provides fixes for fixable findings

v0.23.0

Compare Source

⚠️ Breaking Changes:

  • prefer-dot-notation now requires type information

Features:

  • prefer-dot-notation no longer reports findings which would cause a compile error when fixed
  • new rule: no-writeonly-property-read
  • Added support for new language features in all rules:
    • optional chaining
    • nullish coalescing
    • private identifiers
    • control-flow effects of never-returning functions
      • no-fallthrough and no-unreachable-code report better findings if type inforamtion is available
      • return-never-call only reports calls that TypeScript's control-flow-analysis cannot detect
    • template literal types
  • no-restricted-property-access
    • allow accessing all members via static super
    • allow accessing accessors via super
    • allow accessing abstract accessors via this in constructor
    • disallow read access to uninitialized properties in another property's initializer

Bugfixes:

  • Exclude JSON files and declartions emitted from .js(x) files in composite projects
  • async-function-assignability fixed false-positive on static class members
  • no-restricted-property-access
    • treat MethodSignature like MethodDeclaration
    • fixed lookup of this container for decorators and computed property names
    • fixed crash on parameter properties and special JS property assignments
  • most rules can now handle excessively deep AST structures, e.g. concatenating 5000 strings

v0.22.0

Compare Source

⚠️ Breaking Changes:

  • TypeScript <3.9 is no longer supported
  • Node.js v8, v11 and v13 are no longer supported

Features:

  • Added support for typescript v3.9, v4.0 and v4.1
    • Fixes compile errors and crashes in existing code and tests
    • This does not contain full support for all language features added in those versions
  • //@&#8203;ts-nocheck in .ts files now disables rules with type information for that file, as it was already the case in .js files

Configuration

📅 Schedule: Branch creation - "after 10pm,before 5am" in timezone Europe/Berlin, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • 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
Copy link
Contributor Author

renovate bot commented Feb 12, 2021

Branch automerge failure

This PR was configured for branch automerge, however this is not possible so it has been raised as a PR instead.


  • Branch has one or more failed status checks

@renovate renovate bot force-pushed the renovate/fimbullinter-monorepo branch from 57e824a to dab1f83 Compare February 19, 2021 18:40
@renovate renovate bot changed the title Update fimbullinter monorepo to ^0.23.0 Update fimbullinter monorepo to ^0.24.0 Feb 19, 2021
@renovate
Copy link
Contributor Author

renovate bot commented Mar 24, 2023

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

Warning: custom changes will be lost.

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.

None yet

1 participant