5.0.8 (2022-02-22)

Dependencies

• deps: bump fs-extra from 10.0.0 to 10.0.1 (#256) (f79adbb)

This release is also available on:

• npm package (@latest dist-tag)

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:

• npm package (@latest dist-tag)

5.0.6 (2022-02-03)

Dependencies

• deps: refresh dependencies (38348b0)

This release is also available on:

• npm package (@latest dist-tag)

5.0.5 (2022-02-03)

Dependencies

• deps: bump vsce from 2.6.6 to 2.6.7 (#249) (778da5c)

This release is also available on:

• npm package (@latest dist-tag)

5.0.4 (2022-02-02)

Dependencies

• deps: bump vsce from 2.6.5 to 2.6.6 (#246) (5badb9c)

This release is also available on:

• npm package (@latest dist-tag)

5.0.3 (2022-02-01)

Dependencies

• deps: bump vsce from 2.6.4 to 2.6.5 (#242) (2d6d7ef)

This release is also available on:

• npm package (@latest dist-tag)

5.0.2 (2022-01-25)

Bug Fixes

• bump vsce from 2.6.3 to 2.6.4 (#241) (870a40d)

5.0.1 (2022-01-21)

Bug Fixes

• upgrade ovsx from 0.2.1 to 0.3.0 (#240) (27456fe)

5.0.0 (2022-01-18)

⚠ 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)

  • As vsce now supports configuration through the package.json file (see https://github.com/microsoft/vscode-vsce/issues/548), this option was dropped to simplify the codebase. One should either rely on the vsce automatically detecting when to use yarn (see https://github.com/microsoft/vscode-vsce/issues/480), or add the following to package.json:

  {
      "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

• deps: drop support for Node 10 and 12 (#229) (b0787f9)
• deps: set minimum semantic-release as 18 (#210) (4dd5de0)

Code Refactoring

• drop yarn option (#233) (3ae8a57)
• drop support for VSCE_TOKEN (#234) (a5e5fe5)

3.5.0 (2021-09-13)

Features

• support publishing to Open VSX (#169) (4952226), closes #62

3.4.1 (2021-06-13)

Bug Fixes

• set minimun version of vsce to 1.93.0 (#153) (4b5c9b2)

3.4.0 (2021-06-13)

Features

• refactor verify logic to drop one dependency (33f9f78)
• use vsce to bump version (db9132d)

Bug Fixes

• extension being packaged twice (f9768d6)

3.3.1 (2021-06-12)

Bug Fixes

• upgrade dependencies (6440861)

3.3.0 (2021-03-11)

Features

• add support for VSCE_PAT env var and deprecate VSCE_TOKEN (#109) (fbe1ea9), closes #84

3.2.0 (2021-03-01)

Features

• verify if vsce pat is valid or not (#105) (f116cb4), closes #89

3.1.3 (2021-01-18)

Dependencies

• remove unused semver and node-fetch dependencies (#74)
• remove unneeded dependency commander (040cb6bbadd86a8ea5206ae6272789d2693186f6)

3.1.1 (2021-01-16)

Bug Fixes

• package output not being set (20bcb40)

3.1.0 (2021-01-16)

Features

• add support to yarn (49e6f8c), closes #60
• allow to package without custom output path (ce560dd)

3.0.1 (2020-02-16)

Bug Fixes

• broken verify condition (#55) (8877cd0)

3.0.0 (2020-02-14)

• Merge pull request #53 from JohnstonCode/update-deps-14-02-20 (a5c7c28), closes #53

BREAKING CHANGES

• now requires node >=10.18 and semantic-release >=16.0.0