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 dependency @vscode/test-electron to v2.4.1 - autoclosed #70

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 9, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@vscode/test-electron 2.2.2 -> 2.4.1 age adoption passing confidence

Release Notes

Microsoft/vscode-test (@​vscode/test-electron)

v2.4.1

Compare Source

  • Throw a typed TestRunFailedError on failure instead of a string.

v2.4.0

Compare Source

  • Allow installing unreleased builds using an -unreleased suffix, such as insiders-unreleased.
  • Allow passing different data directories in runVSCodeCommand, using it for extension development.
  • Improve the appearance progress reporting.

v2.3.10

Compare Source

v2.3.9

  • Fix archive extraction on Windows failing when run under Electron

v2.3.8

  • Fix archive extraction on macOS and Linux sometimes failing

v2.3.7

Compare Source

  • Remove detection for unsupported win32 builds
  • Add length and hash validation for downloaded builds

v2.3.6

Compare Source

  • Fix windows sometimes failing on EPERM in download (again)

v2.3.5

Compare Source

  • Fix windows sometimes failing on EPERM in download

v2.3.4

Compare Source

  • Fix "insiders" string not matching correctly

v2.3.3

Compare Source

  • Disable GPU sandbox by default, fixing failures in some CI's.

v2.3.2

Compare Source

  • Fix download method not working for the vscode cli.

v2.3.0

Compare Source

  • Automatically use the most recent version matching engines.vscode in extensions' package.json
  • Allow insiders versions to be specified, such as version: "1.76.0-insider"
  • Reduce the likelihood of 'broken' installations on interrupted downloads
  • Remove dependency on outdated unzipper module

v2.2.3

Compare Source

  • Fix tests sometimes hanging on windows

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

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


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/vscode-test-electron-2.x-lockfile branch from c325217 to 304b8d1 Compare May 13, 2024 22:15
@renovate renovate bot changed the title Update dependency @vscode/test-electron to v2.3.9 Update dependency @vscode/test-electron to v2.3.10 May 13, 2024
@renovate renovate bot force-pushed the renovate/vscode-test-electron-2.x-lockfile branch from 304b8d1 to 5e94e6e Compare May 29, 2024 20:04
@renovate renovate bot changed the title Update dependency @vscode/test-electron to v2.3.10 Update dependency @vscode/test-electron to v2.4.0 May 29, 2024
@renovate renovate bot force-pushed the renovate/vscode-test-electron-2.x-lockfile branch from 5e94e6e to e6c3932 Compare July 6, 2024 00:35
@renovate renovate bot changed the title Update dependency @vscode/test-electron to v2.4.0 Update dependency @vscode/test-electron to v2.4.1 Jul 6, 2024
@renovate renovate bot changed the title Update dependency @vscode/test-electron to v2.4.1 Update dependency @vscode/test-electron to v2.4.1 - autoclosed Dec 8, 2024
@renovate renovate bot closed this Dec 8, 2024
@renovate renovate bot deleted the renovate/vscode-test-electron-2.x-lockfile branch December 8, 2024 18:39
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