As MyGet is a software-as-a-service leveraging a subscription model, we're transitioning our versioning scheme towards a format that is more understandable: YYYY.R. As such, these release notes comprise our first milestone of 2017, hence the version number 2017.1.
The MyGet 2017.1 milestone was tagged on June 1st, 2017.
MyGet again adds some new functionality to the service. The following are the major highlights of this milestone.
We've built a MyGet Credential Provider for Visual Studio 2017! This extension allows you to authenticate against your MyGet feeds using OAuth. Install it from the Visual Studio Gallery!
We added Maven support, and welcome Java/Android developers to the MyGet family! (Announcement | Docs)
We've built a web utility to help you learn and adopt Semantic Versioning: check out our MyGet SemVer Explorer!
We've partnered with OSSIndex.net to check for potential package vulnerabilities on your MyGet feeds! (Announcement | Docs)
MyGet (all plans)
The following applies to all MyGet plans:
- NPM: added support for token authentication
- NPM: added support for upstream token authentication, which now also supports Telerik's NPM registry as an upstream package source
- NPM: added support for the fast search endpoint
- NPM: added support for package deprecation
- NPM: added support for package tagging
- NPM: added support for dist-tag
- NuGet: added support for NuGet's SemVer2 protocol, and added support for modifying build metadata on push upstream dialog
- Maven: introduced support for Maven artifacts
- Maven: introduced support for Android AAR artifacts
- Symbols: added a toggle to support pushing symbols upstream as well
- Symbols: when the upstream target feed is a MyGet feed, we automatically also push the symbols upstream
- Usability: no longer show symbols packages separately on the Gallery's feed details view
- Usability: minor modifications to the Gallery feed details UI to improve the user experience
- Usability: added a download all button to the packages dropdown in build results view
- Usability: hide pre-authenticated feed endpoints from Feed Details view when the feed is not a private feed
- Usability: added a copy-to-clipboard button to the connection details popup on Gallery feeds
- Security: we've built a MyGet Credential Provider for Visual Studio 2017! This extension allows you to authenticate against your MyGet feeds using OAuth.
- Security: we've consolidated the login page: one page to rule them all!
- Security: we no longer display access tokens (you can still copy them though)
- Security: improved auditing
- Security: added support for feed and privilege scopes to access tokens / api keys (in addition to expiration support which we already had)
- Integrations: SymbolSource.org integration has been retired in favor of MyGet's own Symbols functionality
- Integrations: added OSSIndex.net integration to detect package vulnerabilities and report them on your feed details view
The enterprise plan has all functionality from the paid subscription plans, and more! The following applies only to the MyGet Enterprise plan:
- Usability: the Gallery index is now the default landing page when authenticated on MyGet Enterprise
- Security: added support for marking users as external to the tenant. This prevents the external user from accessing Enterprise feeds, unless privileges are explicitly assigned at the feed level. (see Feed Types)
MyGet Build Services
- Added support for Visual Studio 2017, .NET Core and the new PackageReference project format (Announcement)
- AssemblyInfo patching now supports globbing patterns (like
Bug Fixes & Other Improvements
- MyGet has been upgraded to run on .NET Framework 4.6.2, which seemed to have positive effect on performance
- Overwriting source symbols is now blocked when forbid overwrite is enabled on the feed
- Fixed a bug in semantic version range parsing of npm dependencies (tilde and carret ranges)
- Show quota per feed on user profile page (helps answer the question: 'which of my feeds consumes most?')
- Fixed an issue caused by breaking changes in VSTS API (repository
remoteUrl returned by VSTS API no longer contained VSTS collection name)
- Fixed an issue in the Gallery index view related to feed icons
- Fixed an issue that caused an HTTP 500 when a nuspec contained some invalid data
- Fixed an issue that caused NPM push upstream to fail when no package description was given
- Fixed an issue with the symbols code browser when a file was not found or could not be displayed
- NuGet: allow packages.config files to be uploaded without version number specified
Please tell us how we're doing by taking 10 seconds of your time to answer a single question (and optionally provide any feedback you want). We love hearing from you, so keep that feedback coming! MyGet is built for you!