Skip to content
This repository has been archived by the owner on Mar 10, 2022. It is now read-only.

chore(deps): update dependency semantic-release-vsce to v5 #227

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 1, 2022

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
semantic-release-vsce ^3.0.1 -> ^5.0.8 age adoption passing confidence

Test plan: CI should pass with updated dependencies. No review required: this is an automated dependency update PR.


Release Notes

felipecrs/semantic-release-vsce

v5.0.8

Compare Source

5.0.8 (2022-02-22)
Dependencies

This release is also available on:

v5.0.7

Compare Source

5.0.7 (2022-02-12)
Dependencies
  • deps: bump follow-redirects from 1.14.7 to 1.14.8 (#​251) (ca4a815)

This release is also available on:

v5.0.6

Compare Source

5.0.6 (2022-02-03)
Dependencies
  • deps: refresh dependencies (38348b0)

This release is also available on:

v5.0.5

Compare Source

5.0.5 (2022-02-03)
Dependencies

This release is also available on:

v5.0.4

Compare Source

5.0.4 (2022-02-02)
Dependencies

This release is also available on:

v5.0.3

Compare Source

5.0.3 (2022-02-01)
Dependencies

This release is also available on:

v5.0.2

Compare Source

5.0.2 (2022-01-25)
Bug Fixes

v5.0.1

Compare Source

5.0.1 (2022-01-21)
Bug Fixes

v5.0.0

Compare Source

⚠ BREAKING CHANGES
  • drop support for VSCE_TOKEN (#​234)

    • As this was already deprecated, the VSCE_TOKEN is not supported anymore in favor of VSCE_PAT which is already supported by vsce
      itself. If you have a VSCE_TOKEN set, please unset it and set VSCE_PAT instead.
  • drop yarn option (#​233)

    {
        "vsce": {
            "yarn": true
        }
    }
  • set minimum semantic-release version as 18 (#​210)

    • This requires that you upgrade your semantic-release to at least version 18 before using together with this package.
  • set minimum node version as 14 (#​229)

    • This drops support for Node 10 and 12 because vsce itself also did. Make sure your pipeline now runs in an environment with Node 14 or higher.
Build System
Code Refactoring

v4.0.1

Compare Source

v4.0.0

Compare Source

v3.5.0

Compare Source

Features

v3.4.1

Compare Source

3.4.1 (2021-06-13)
Bug Fixes

v3.4.0

Compare Source

Features
  • refactor verify logic to drop one dependency (33f9f78)
  • use vsce to bump version (db9132d)
Bug Fixes
  • extension being packaged twice (f9768d6)

v3.3.1

Compare Source

3.3.1 (2021-06-12)
Bug Fixes

v3.3.0

Compare Source

Features

v3.2.0

Compare Source

Features

Configuration

📅 Schedule: "on the 1st through 7th day of the month" in timezone America/Los_Angeles.

🚦 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, click this checkbox.

This PR has been generated by WhiteSource Renovate. View repository job log here.

@renovate
Copy link
Contributor Author

renovate bot commented Feb 1, 2022

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm WARN using --force Recommended protections disabled.
npm notice 
npm notice New minor version of npm available! 8.3.1 -> 8.5.3
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v8.5.3>
npm notice Run `npm install -g [email protected]` to update!
npm notice 
npm WARN using --force Recommended protections disabled.
chmod: cannot access '/home/ubuntu/.npm': No such file or directory
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/semantic-release
npm ERR!   dev semantic-release@"^17.3.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer semantic-release@">=18" from [email protected]
npm ERR! node_modules/semantic-release-vsce
npm ERR!   dev semantic-release-vsce@"^5.0.8" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate-cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2022-03-07T20_25_49_378Z-debug-0.log

@renovate renovate bot force-pushed the renovate/semantic-release-vsce-5.x branch 4 times, most recently from a1a618e to f6a7c2b Compare February 3, 2022 20:13
@renovate renovate bot force-pushed the renovate/semantic-release-vsce-5.x branch from f6a7c2b to 197bc97 Compare February 12, 2022 18:47
@renovate renovate bot force-pushed the renovate/semantic-release-vsce-5.x branch 2 times, most recently from c1c21f1 to 3f6f530 Compare March 1, 2022 13:06
@renovate renovate bot force-pushed the renovate/semantic-release-vsce-5.x branch from 3f6f530 to d432911 Compare March 7, 2022 20:26
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant