search

usethesource / rascal-language-servers

An LSP server for Rascal which includes an easy-to-use LSP generator for languages implemented in Rascal, and an interactive terminal REPL.
BSD 2-Clause "Simplified" License
10 stars 7 forks source link

Bump the dev-packages group in /rascal-vscode-extension with 8 updates #399

Closed dependabot[bot] closed 1 week ago

dependabot[bot] commented 1 week ago

Bumps the dev-packages group in /rascal-vscode-extension with 8 updates:

Package From To
@typescript-eslint/eslint-plugin 7.11.0 7.14.1
@typescript-eslint/parser 7.11.0 7.14.1
@vscode/vsce 2.26.1 2.29.0
esbuild 0.21.4 0.22.0
mocha 10.4.0 10.5.2
@types/mocha 10.0.6 10.0.7
typescript 5.4.5 5.5.2
vscode-extension-tester 8.2.0 8.3.1

Updates @typescript-eslint/eslint-plugin from 7.11.0 to 7.14.1

Release notes

Sourced from @​typescript-eslint/eslint-plugin's releases.

v7.14.1

7.14.1 (2024-06-24)

🚀 Features

  • support TypeScript 5.5 (#9397)
  • ast-spec: tighter types and documentation for declaration/* (#9211)

đź©ą Fixes

  • keep warnAbountTSVersion in sync with package.json (#9400)
  • eslint-plugin: [no-extraneous-class] handle abstract members (#9367)
  • eslint-plugin: [prefer-nullish-coalescing] handle intersected primitive types (#9378)
  • eslint-plugin: [no-invalid-this] support AccessorProperty (#9411)
  • eslint-plugin: [prefer-nullish-coalescing] treat enums and literals as their underlying primitive types (#9376)
  • eslint-plugin: [prefer-nullish-coalescing] ensure ternary fix does not remove parens (#9380)

❤️ Thank You

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

v7.14.0

7.14.0 (2024-06-24)

We followed this up soon after with 7.14.1 - see the combined release notes here https://github.com/typescript-eslint/typescript-eslint/releases/tag/v7.14.1

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

v7.13.1

7.13.1 (2024-06-17)

đź©ą Fixes

  • eslint-plugin: [prefer-readonly] refine report locations (#8894)
  • eslint-plugin: [return-await] support explicit resource management (#9044)
  • eslint-plugin: [no-unsafe-member-access] differentiate a types-error any from a true any (#9291)

❤️ Thank You

... (truncated)

Changelog

Sourced from @​typescript-eslint/eslint-plugin's changelog.

7.14.1 (2024-06-24)

đź©ą Fixes

  • eslint-plugin: [prefer-nullish-coalescing] treat enums and literals as their underlying primitive types

  • eslint-plugin: [prefer-nullish-coalescing] ensure ternary fix does not remove parens

❤️ Thank You

  • Jake Bailey

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

7.14.0 (2024-06-24)

🚀 Features

  • support TypeScript 5.5

đź©ą Fixes

  • eslint-plugin: [no-extraneous-class] handle abstract members

  • eslint-plugin: [prefer-nullish-coalescing] handle intersected primitive types

  • eslint-plugin: [no-invalid-this] support AccessorProperty

❤️ Thank You

  • Brad Zacher
  • cm-ayf
  • Jake Bailey
  • James Zhan
  • Joshua Chen
  • yoshi2no

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

7.13.1 (2024-06-17)

đź©ą Fixes

  • eslint-plugin: [prefer-readonly] refine report locations

... (truncated)

Commits
  • b4fe94f chore(release): publish 7.14.1
  • f29150f fix(eslint-plugin): [prefer-nullish-coalescing] ensure ternary fix does not r...
  • 9b7731d fix(eslint-plugin): [prefer-nullish-coalescing] treat enums and literals as t...
  • dfc4469 chore(release): publish 7.14.0
  • 635133a docs: split troubleshooting into granular sections (#9024)
  • c322099 fix(eslint-plugin): [no-invalid-this] support AccessorProperty (#9411)
  • 23e6468 fix(eslint-plugin): [prefer-nullish-coalescing] handle intersected primitive ...
  • 5c4a5de feat(ast-spec): tighter types and documentation for declaration/* (#9211)
  • e47123d fix(eslint-plugin): [no-extraneous-class] handle abstract members (#9367)
  • dc18229 feat: support TypeScript 5.5 (#9397)
  • Additional commits viewable in compare view


Updates @typescript-eslint/parser from 7.11.0 to 7.14.1

Release notes

Sourced from @​typescript-eslint/parser's releases.

v7.14.1

7.14.1 (2024-06-24)

🚀 Features

  • support TypeScript 5.5 (#9397)
  • ast-spec: tighter types and documentation for declaration/* (#9211)

đź©ą Fixes

  • keep warnAbountTSVersion in sync with package.json (#9400)
  • eslint-plugin: [no-extraneous-class] handle abstract members (#9367)
  • eslint-plugin: [prefer-nullish-coalescing] handle intersected primitive types (#9378)
  • eslint-plugin: [no-invalid-this] support AccessorProperty (#9411)
  • eslint-plugin: [prefer-nullish-coalescing] treat enums and literals as their underlying primitive types (#9376)
  • eslint-plugin: [prefer-nullish-coalescing] ensure ternary fix does not remove parens (#9380)

❤️ Thank You

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

v7.14.0

7.14.0 (2024-06-24)

We followed this up soon after with 7.14.1 - see the combined release notes here https://github.com/typescript-eslint/typescript-eslint/releases/tag/v7.14.1

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

v7.13.1

7.13.1 (2024-06-17)

đź©ą Fixes

  • eslint-plugin: [prefer-readonly] refine report locations (#8894)
  • eslint-plugin: [return-await] support explicit resource management (#9044)
  • eslint-plugin: [no-unsafe-member-access] differentiate a types-error any from a true any (#9291)

❤️ Thank You

... (truncated)

Changelog

Sourced from @​typescript-eslint/parser's changelog.

7.14.1 (2024-06-24)

This was a version bump only for parser to align it with other projects, there were no code changes.

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

7.14.0 (2024-06-24)

🚀 Features

  • support TypeScript 5.5

❤️ Thank You

  • Brad Zacher
  • cm-ayf
  • Jake Bailey
  • James Zhan
  • Joshua Chen
  • yoshi2no

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

7.13.1 (2024-06-17)

This was a version bump only for parser to align it with other projects, there were no code changes.

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

7.13.0 (2024-06-10)

🚀 Features

  • parser, typescript-estree: export withoutProjectParserOptions utility

❤️ Thank You

  • Fotis Papadogeorgopoulos
  • Joshua Chen
  • Kirk Waiblinger
  • Tobiloba Adedeji
  • Vinccool96
  • YeonJuan

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

... (truncated)

Commits
  • b4fe94f chore(release): publish 7.14.1
  • dfc4469 chore(release): publish 7.14.0
  • 1212a8f chore(release): publish 7.13.1
  • 8a178ed chore(release): publish 7.13.0
  • c9a6dd9 feat(parser, typescript-estree): export withoutProjectParserOptions utility (...
  • 7e93b28 chore(release): publish 7.12.0
  • 2bbf656 fix(types): correct typing ParserOptions (#9202)
  • See full diff in compare view


Updates @vscode/vsce from 2.26.1 to 2.29.0

Release notes

Sourced from @​vscode/vsce's releases.

v2.29.0

Changes:

Feature Requests:

  • #1006: Expose enabledApiProposals as a property

Others:

This list of changes was auto generated.

v2.28.1-0

Changes:

Feature Requests:

  • #1006: Expose enabledApiProposals as a property

Others:

This list of changes was auto generated.

v2.28.0

Changes:

Feature Requests:

  • #993: Support signing related features

Others:

... (truncated)

Commits


Updates esbuild from 0.21.4 to 0.22.0

Release notes

Sourced from esbuild's releases.

v0.22.0

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.21.0 or ~0.21.0. See npm's documentation about semver for more information.

  • Omit packages from bundles by default when targeting node (#1874, #2830, #2846, #2915, #3145, #3294, #3323, #3582, #3809, #3815)

    This breaking change is an experiment. People are commonly confused when using esbuild to bundle code for node (i.e. for --platform=node) because some packages may not be intended for bundlers, and may use node-specific features that don't work with a bundler. Even though esbuild's "getting started" instructions say to use --packages=external to work around this problem, many people don't read the documentation and don't do this, and are then confused when it doesn't work. So arguably this is a bad default behavior for esbuild to have if people keep tripping over this.

    With this release, esbuild will now omit packages from the bundle by default when the platform is node (i.e. the previous behavior of --packages=external is now the default in this case). Note that your dependencies must now be present on the file system when your bundle is run. If you don't want this behavior, you can do --packages=bundle to allow packages to be included in the bundle (i.e. the previous default behavior). Note that --packages=bundle doesn't mean all packages are bundled, just that packages are allowed to be bundled. You can still exclude individual packages from the bundle using --external: even when --packages=bundle is present.

    The --packages= setting considers all import paths that "look like" package imports in the original source code to be package imports. Specifically import paths that don't start with a path segment of / or . or .. are considered to be package imports. The only two exceptions to this rule are subpath imports (which start with a # character) and TypeScript path remappings via paths and/or baseUrl in tsconfig.json (which are applied first).

  • Drop support for older platforms (#3802)

    This release drops support for the following operating systems:

    • Windows 7
    • Windows 8
    • Windows Server 2008
    • Windows Server 2012

    This is because the Go programming language dropped support for these operating system versions in Go 1.21, and this release updates esbuild from Go 1.20 to Go 1.22.

    Note that this only affects the binary esbuild executables that are published to the esbuild npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.21). That might look something like this:

    git clone https://github.com/evanw/esbuild.git
cd esbuild
go build ./cmd/esbuild
./esbuild.exe --version

    In addition, this release increases the minimum required node version for esbuild's JavaScript API from node 12 to node 18. Node 18 is the oldest version of node that is still being supported (see node's release schedule for more information). This increase is because of an incompatibility between the JavaScript that the Go compiler generates for the esbuild-wasm package and versions of node before node 17.4 (specifically the crypto.getRandomValues function).

  • Update await using behavior to match TypeScript

    TypeScript 5.5 subtly changes the way await using behaves. This release updates esbuild to match these changes in TypeScript. You can read more about these changes in microsoft/TypeScript#58624.

  • Allow es2024 as a target environment

    The ECMAScript 2024 specification was just approved, so it has been added to esbuild as a possible compilation target. You can read more about the features that it adds here: https://2ality.com/2024/06/ecmascript-2024.html. The only addition that's relevant for esbuild is the regular expression /v flag. With --target=es2024, regular expressions that use the /v flag will now be passed through untransformed instead of being transformed into a call to new RegExp.

  • Publish binaries for OpenBSD on 64-bit ARM (#3665, #3674)

    With this release, you should now be able to install the esbuild npm package in OpenBSD on 64-bit ARM, such as on an Apple device with an M1 chip.

    This was contributed by @​ikmckenz.

  • Publish binaries for WASI (WebAssembly System Interface) preview 1 (#3300, #3779)

    The upcoming WASI (WebAssembly System Interface) standard is going to be a way to run WebAssembly outside of a JavaScript host environment. In this scenario you only need a .wasm file without any supporting JavaScript code. Instead of JavaScript providing the APIs for the host environment, the WASI standard specifies a "system interface" that WebAssembly code can access directly (e.g. for file system access).

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.22.0

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.21.0 or ~0.21.0. See npm's documentation about semver for more information.

  • Omit packages from bundles by default when targeting node (#1874, #2830, #2846, #2915, #3145, #3294, #3323, #3582, #3809, #3815)

    This breaking change is an experiment. People are commonly confused when using esbuild to bundle code for node (i.e. for --platform=node) because some packages may not be intended for bundlers, and may use node-specific features that don't work with a bundler. Even though esbuild's "getting started" instructions say to use --packages=external to work around this problem, many people don't read the documentation and don't do this, and are then confused when it doesn't work. So arguably this is a bad default behavior for esbuild to have if people keep tripping over this.

    With this release, esbuild will now omit packages from the bundle by default when the platform is node (i.e. the previous behavior of --packages=external is now the default in this case). Note that your dependencies must now be present on the file system when your bundle is run. If you don't want this behavior, you can do --packages=bundle to allow packages to be included in the bundle (i.e. the previous default behavior). Note that --packages=bundle doesn't mean all packages are bundled, just that packages are allowed to be bundled. You can still exclude individual packages from the bundle using --external: even when --packages=bundle is present.

    The --packages= setting considers all import paths that "look like" package imports in the original source code to be package imports. Specifically import paths that don't start with a path segment of / or . or .. are considered to be package imports. The only two exceptions to this rule are subpath imports (which start with a # character) and TypeScript path remappings via paths and/or baseUrl in tsconfig.json (which are applied first).

  • Drop support for older platforms (#3802)

    This release drops support for the following operating systems:

    • Windows 7
    • Windows 8
    • Windows Server 2008
    • Windows Server 2012

    This is because the Go programming language dropped support for these operating system versions in Go 1.21, and this release updates esbuild from Go 1.20 to Go 1.22.

    Note that this only affects the binary esbuild executables that are published to the esbuild npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.21). That might look something like this:

    git clone https://github.com/evanw/esbuild.git
cd esbuild
go build ./cmd/esbuild
./esbuild.exe --version

    In addition, this release increases the minimum required node version for esbuild's JavaScript API from node 12 to node 18. Node 18 is the oldest version of node that is still being supported (see node's release schedule for more information). This increase is because of an incompatibility between the JavaScript that the Go compiler generates for the esbuild-wasm package and versions of node before node 17.4 (specifically the crypto.getRandomValues function).

  • Update await using behavior to match TypeScript

    TypeScript 5.5 subtly changes the way await using behaves. This release updates esbuild to match these changes in TypeScript. You can read more about these changes in microsoft/TypeScript#58624.

  • Allow es2024 as a target environment

    The ECMAScript 2024 specification was just approved, so it has been added to esbuild as a possible compilation target. You can read more about the features that it adds here: https://2ality.com/2024/06/ecmascript-2024.html. The only addition that's relevant for esbuild is the regular expression /v flag. With --target=es2024, regular expressions that use the /v flag will now be passed through untransformed instead of being transformed into a call to new RegExp.

  • Publish binaries for OpenBSD on 64-bit ARM (#3665, #3674)

    With this release, you should now be able to install the esbuild npm package in OpenBSD on 64-bit ARM, such as on an Apple device with an M1 chip.

    This was contributed by @​ikmckenz.

  • Publish binaries for WASI (WebAssembly System Interface) preview 1 (#3300, #3779)

... (truncated)

Commits


Updates mocha from 10.4.0 to 10.5.2

Release notes

Sourced from mocha's releases.

v10.5.2

What's Changed

New Contributors

Full Changelog: https://github.com/mochajs/mocha/compare/v10.5.1...v10.5.2

v10.5.1

What's Changed

New Contributors

Full Changelog: https://github.com/mochajs/mocha/compare/v10.5.0...v10.5.1

v10.5.0

:tada: Enhancements

:bug: Fixes

:nut_and_bolt: Other

Changelog

Sourced from mocha's changelog.

10.5.2 / 2024-05-25

:bug: Fixes

10.5.1 / 2024-05-24

:bug: Fixes

10.5.0 / 2024-05-24

:tada: Enhancements

:bug: Fixes

:nut_and_bolt: Other

Commits
  • b2a6358 Release 10.5.2
  • a3bb86d docs: add 10.5.2 to CHANGELOG.md
  • 02c04c4 fix: better tracking of seen objects in error serialization (#5032)
  • 103c56b Release v10.5.1
  • 545b66d docs: add 10.5.1 to CHANGELOG.md
  • dbe229d fix: Add error handling for nonexistent file case with --file option (#5086)
  • b9ce511 Release v10.5.0
  • 12c88a7 Docs: add 10.5.0 to CHANGELOG.md
  • b6aa7e8 chore: rename 'master' to 'main' in docs and tooling (#5130)
  • 67a8124 fix: include stack in browser uncaught error reporting (#5107)
  • Additional commits viewable in compare view


Updates @types/mocha from 10.0.6 to 10.0.7

Commits


Updates typescript from 5.4.5 to 5.5.2

Release notes

Sourced from typescript's releases.

TypeScript 5.5

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

TypeScript 5.5 RC

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

TypeScript 5.5 Beta

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

Commits
  • 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 (#...
  • 39c9eeb Pick #58857 to release-5.5 (#58858)
  • 2b0009c 🤖 Pick PR #58846 (Ensure the updates with crashes rev...) into release-5.5 (#...
  • Additional commits viewable in compare view


Updates vscode-extension-tester from 8.2.0 to 8.3.1

Release notes

Sourced from vscode-extension-tester's releases.

v8.3.1

What's Changed

🚀 Features

📦 Dependencies

Other Changes

Full Changelog: https://github.com/redhat-developer/vscode-extension-tester/compare/v8.3.0...v8.3.1

v8.3.0

What's Changed

🚀 Features

📦 Dependencies

... (truncated)

Commits
  • 44f5969 chore(release): Publish v8.3.1 (#1388)
  • 84cd60f feat: bump vscode-max version from 1.90.0 to 1.90.2 (#1376)
  • 2b554c5 build(deps): bump glob from 10.4.1 to 10.4.2 (#1372)
  • a151c54 build(deps): bump @​vscode/vsce from 2.27.0 to 2.29.0 (#1375)
  • 75b755d build(deps): bump c8 from 10.1.1 to 10.1.2 (#1362)
  • 2c16a5c chore(release): Publish v8.3.0 (#1361)
  • 42716d9 build: Use Node 20 as default supported version (#1350)
  • 690d143 build(deps): bump c8 from 9.1.0 to 10.1.1 (#1360)
  • d7c3657 fix: Add chromedriver download url for version 122+
  • 9792abb feat: Add support for VS Code 1.90.x
  • Additional commits viewable in compare view


Dependabot will resolve any conflicts with this PR a...

Description has been truncated

DavyLandman commented 1 week ago

@dependabot show tar ignore conditions

dependabot[bot] commented 1 week ago

No ignore conditions found for the dependency tar

DavyLandman commented 1 week ago

@dependabot help

sonarcloud[bot] commented 1 week ago

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud