Skip to content

Latest commit

 

History

History
296 lines (194 loc) · 12.6 KB

File metadata and controls

296 lines (194 loc) · 12.6 KB

0.25.0

0.24.0

0.23.0

  • Maven: Support for repositories defined in pom.xml (not only settings and central)

  • Maven: Support for local repository (case when a package is not in a repository but only in .m2/repository)

  • Maven: Better tagged version

  • Maven: Show when a package is not found

  • Maven: Use maven binary from path to get effective settings based

  • DotNet: Adds configuration options which allow multiple custom NuGet feeds

  • Bower: Will be removed in the next release

Maven work is all thanks to https://github.com/fcrespo82

DotNet work is all thanks to https://github.com/Hoffs

0.22.0

0.21.2

0.21.1

0.21.0

0.20.1

0.20.0

0.19.1

  • Fixes a case where pre releases were being treated as older versions

0.19.0

0.18.1

  • Fixed unicode arrows not showing on osx and some linux dists

  • Changelogs viewed from vscode extension panel has a markdown table bug.

    The formatted changelog for 0.18.0 is here

0.18.0

  • Added clearer matching reasons

    Label Shown When the version entered
    Prerelease is ahead of the latest version
    Latest matches the latest
    Satisfies latest is a range that matches the latest
    Fixed to x.x.x is fixed and not the latest
    No match found: x.x.x was found in the provider registry
    Invalid version entered was invalid
  • Clearer outdated statuses

    Colour Text shown Status
    green x.x.x installed Installed at latest
    yellowgreen x.x.x prerelease installed Installed is a prerelease ahead of latest
    orange x.x.x installed, npm update needed Installed but different to the entered version
    orange x.x.x installed Older than the latest
    red Missing install Not installed
  • Added nuget ranges and floating versions for dotnet

  • Tags are sorted in recent version order

  • Fixed git+https github urls breaking all codelenses for npm

  • Fixes invalid version entries breaking all codelens for npm

0.17.2

  • Dub now correctly identifies packages that are not found. Thanks to @WebFreak001
  • Dub install status decorations are now showing correctly. Thanks again to @WebFreak001
  • Jspm: Handles scenarios where no code lenses would render when an invalid registry was given. Thanks to @eamodio
  • Npm: Handles unsupported protocols which prevented code lenses from rendering.

0.17.1

  • Fixed issue where tagged versions shown were older than the required version entered. (NPM and DotNet)

    Old horror before this fix

    image

    Now shows as

    image

  • Some packages in NPM have multiple tags with the same version as what 'latest' provides. When this is the case these tags are not shown.

  • Fixed edge case where many tagged versions caused install decorations to appear on wrong line

0.17.0

  • Added tagged version support to dotnet projects (i.e. 1.2.3-beta.1, 1.2.3-rc.1)

    image

    To filter out packages that have many unwanted tagged versions you can set a preferred list using versionlens.dotnet.tagFilter

  • Latest version will show by default instead of being hidden behind the tagged versions option

    image

  • Fixed non-existing version detection

0.16.2

  • Fixes issue where dependency decorations were being stuck on the wrong line after a mutli line edit.
  • Made dependency colours configurable in user settings. Will help if the default colours are difficult to see for a specific theme (CSS colours are valid entries)
    • versionlens.missingDependencyColour: Default 'red'
    • versionlens.outdatedDependencyColour: Default 'orange'
    • versionlens.installedDependencyColour: Default 'green'

0.16.1

  • Fixes a bug where dependency decorations could leak in to wrong documents

0.16.0

  • Added outdated information for npm

    image

  • Added 'latest' to the dist tags for npm and jspm. This gives the ability to always see the latest version regardless of what version is matched in the package.

    image

  • Fixes an edge case where npm view doesn't return the list of versions in chronological order. The only edge case found so far is when "x" is sepcified as the version

  • Added fsharp project extensions for dotnet core

    image

  • Stopped editor toolbar icons showing in diff mode

0.15.0

  • Added two new icon tools to the the editor toolbar

    image

    • You can show or hide versions. versionlens.showVersionLensesAtStartup defaults to true
    • You can show or hide tagged versions. versionlens.showTaggedVersionsAtStartup defaults to false
    • versionlens.npm.showTaggedVersions has been dropped in favour of this new change
  • github.compareOptions is now called github.taggedCommits.

    latest will always be the latest commit. This field now only accepts ['Release', 'Tag'] which is the default filter

0.14.1

  • Fixed a case where npm view doesn't return latest tag as the first entry.

0.14.0

  • Added ability to view versions associated with dist tags for npm and jspm.

    Example:

    image

    • To enable set versionlens.npm.showTaggedVersions: true

    • To filter out packages that have many unwanted dist tags you can set a preferred list using versionlens.npm.distTagFilter.

      Example: versionlens.npm.distTagFilter: ['alpha', 'beta', 'legacy', 'next'] will only show and order the dist tags as 'alpha', 'beta', 'legacy' and 'next'

  • Renamed 'statisfies' to 'Matches'

  • Fixed the ordering of github versions to always be ordered as releases, tags then commits

  • Removed ability to update all packages. Sometimes this feature never worked because you first had to scroll all the packages in to view. Will work on a better method for this feature in the future.

0.13.0

  • Added dotnet core csproj file support. Thanks to @eamodio

0.12.2

  • Fixes an issue where ranged versions (i.e. 1.x) were showing the incorrect update verion for npm and jspm
  • Moved error messages to the console. They should no longer appear as a code lens

0.12.1

  • Fixes an issue where code lenses were not showing for jspm in package.json

0.12.0

  • Adds ability to provide github access token to avoid github api rate limiting

    Tokens can be provided by setting versionlens.github.accessToken in your user settings. To generate a token see https://help.github.com/articles/creating-an-access-token-for-command-line-use/#creating-a-token

    When no token is provided then access to the api will be rate limited to 60 requests every 10 minutes or so.

  • Adds indication for github packages that dont exist

  • Project dependency properties can now be customised via vscode settings. The default settings keep the previoussetup so nothing will break.

    // vscode settings.json example
    {
      "versionlens.npm.dependencyProperties": [
        "dependencies",
        "devDependencies",
        "peerDependencies",
        "optionalDependencies",
        "myCustomDependencies"
      ]
    }

0.11.0

  • Can now choose to update all packages within a dependency section. i.e. update all beneath devDependencies.

    update-all-example

    Note

    • Because code lenses are not generated until they are viewed in the editor then only code lenses that have been viewed since opening the document can be updated. If you have many dependencies that go off the screen then just scroll them all in to view once before running the update all command for maximum coverage.
    • This functionality ignores github and file package entries.
  • Now checks if an npm file: package path exists and provides indication when the resource does not exist.

    file-existence

0.10.0

  • Added github commitish support for npm, jspm and bower. Doesn't support pre-releases yet.

    npm-comittish

    Also supports semver releases\tags

    npm-comittish2

0.9.1

  • Fixes invalid message when using tags i.e. @next

0.9.0

  • Github and local file system packages are now treated as clickable links that browse to their respective destinations. (git urls are not implemented yet)

0.8.0

  • Added support for npm private packages and private registries

0.7.1

  • Replaces update arrow indicator to be a unicode charachter due to change in vscode 1.7. See microsoft/vscode#13714 for more info.

0.7.0

  • Adds support for preserving some semver operators when updating

0.6.0

  • Added jspm package support

0.5.0

  • Added npm scoped packages support

0.4.3

  • Fixes versionlens for dub sub packages

0.4.2

0.4.1

  • Replaces internal json module with external
  • Replaces internal request module with external

0.4.0

  • Adds dotnet project.json support
  • Fixes issue when a child version entry is not present

0.3.0

  • Adds dub dub.json support