MyGet 2.1 was released on February 12, 2016.
This 2.1 release of MyGet again adds some new functionality to the service. Major highlights of this release are:
This means, from now on, you can now also use MyGet to host your symbols, publicly or secured.
MyGet (all plans)
The following applies to all MyGet plans:
MyGet (paid plans)
Obviously all paid plans also get the enhancements made available on the free plan. The following applies to the MyGet Starter and Professional plans:
- Security: Feed privilege claim tokens now expire after 15 days when unused
- Billing: we now allow for yearly billing to reduce the administrative overhead of billing cycles
The enterprise plan has all functionality from the paid subscription plans, and more! The following applies only to the MyGet Enterprise plan:
- Support for restricting feed creation to administrators only
MyGet Build Services
- Support for explicitly publishing artifacts using service messages
- Support for BitBucket API v2.0 and switch to OAuth 2.0
- Support for xUnit v2.0
- Support GitLab POST hooks
- Performance improvements in build hook payload parsers
- Web Hooks: new Build Queued web hook
- New option: toggle access to build log for feed consumers
- Various performance improvements in the web site
- Bower: license analysis now also checks Bower package licenses
- Usernames on feed security page now link to the user profile page
- npm: proxy dist-tags from upstream when available
- Fixed a bug where in some cases uploading a ZIP file Bower package threw an exception
- Fixed a bug where in some cases pushing an npm package upstream to npmjs.com failed
- Fixed a bug where editing a package source was not possible when the package source is unavailable
We love hearing from you, so keep that feedback coming! MyGet is built for you!
21. February 2016 07:18
Feature . NuGet
Every once in a while, our support gets a question that is similar to the following:
When requesting the package details for some versions of the NuGet packages in our feed it seems like the service encounters an error preparing the ATOM document, also resulting in NuGet failing to download the package.
Here's an example URL: https://www.myget.org/F/chucknorris/api/v2/Packages(Id='MyPackage',Version='1.2.20160209.1-master')
Is something wrong with MyGet? Definitely not! Let’s look at the packages for this feed:
- MyPackage 1.2.20160209.1-master
- MyPackage 1.2.20160209.1-dev
Can you spot the error? It’s very subtle, so let us help here. The version number has three dots (“.”) in it, which means it should be treated as a major.minor.patch.build type of version number, which is numeric. MyGet takes the hint and will strip off the –master and –dev in the above versions, treating both packages as one.
Clearly, the intention here was to use Semantic Versioning (SemVer): the –master and –dev suffixes to the version number were intended to provide a label in the version number. But semantic versioning is in the form of major.minor.patch-label, which means one dot less in the version number should be used. So in this case, the packages should be re-versioned and re-uploaded with the correct version number.
Don’t you guys have validation for this? is one of the questions we’d expect. We do, but it’s opt-in because many of our users start out with non-SemVer packages on their feeds and we don’t want to block those from being uploaded either. From a feed’s Package Settings tab, enable the Forbid packages which are non-compliant with Semantic Version? option.
This will prevent malformed semantic versions from being uploaded to your feed and prevent the above error from ever happening to you.
11. February 2016 08:15
Bower . Feature . Npm . NuGet . Vsix
Wouldn’t it be awesome if creating a NuGet, npm, Bower or VSIX feed was as easy as just copying packages into a Dropbox folder? Awesomeness is here: we’ve added Dropbox as a package source type to MyGet. This allows us to link a Dropbox folder to a MyGet feed and automatically upload packages so they can be consumed with the popular package managers out there.
The Dropbox package source makes it easy to move packages into MyGet. For example, migrating from a network share to MyGet is as easy as copy-paste. Have a build server that drops artifacts into a Dropbox folder? MyGet will add the synchronized artifacts to your feed. Right now we download packages from Dropbox on a schedule (every 15 minutes).
Give it a try and let us know how it goes – feedback is welcome through the comments below or via the MyGetTeam Twitter account.