Hello Hamza,

I am able to reproduce this and I've filed PG-1317 to fix it.

Hello Steven,

Try visiting this page in a browser: http://<ProGet hostname>/feeds/<feed name>/NuGet.Frameworks/4.7.0-rtm.5148

There should be an error message like this:

The version number provided is invalid, but would be valid if this NuGet feed were migrated to SemVer2.

You can migrate a legacy NuGet feed to SemVer2 by clicking the button at the top of the feed management page.

Hello Frank,

Are the remaining packages marked as Package Source: Remote Connector (cached) in the left sidebar?

Hello J,

ProGet assumes it's in a schema named dbo. By default, that's what SQL Server uses. To change the default schema back to dbo, run this command:

ALTER USER [proget] WITH DEFAULT_SCHEMA [dbo]

Hello Pedro,

Docker feeds appear to have been missed when the api user was added for feed authentication. I've filed PG-1295 to fix that.

ProGet 5.1.0 is not released on Docker Hub, but you can build the image locally with this command:

docker build -t inedo/proget:5.1.0 --build-arg PROGET_VERSION=5.1.0 github.com/Inedo/proget-docker

Hello Tony,

I've filed PG-1294 to fix this. As a workaround, you can access the package directly by version number even without this fix.

Hello Tom and Brett,

The endpoint being requested seems simple enough. For example, here's what it requests for -StartWith Inedo..

I've filed PG-1281 to add an implementation of this endpoint.

Hello Timofey,

I've filed PG-1280 to hide the build metadata from NuGet version numbers when they are displayed in titles.

Hello Ludovic,

This appears to happen when there is no version of your package tagged as latest. To fix it, click the Edit Details button on the latest version of your package and add a tag named latest (all lower-case).

I've filed PG-1279 to fix this happening in the first place.

Hello Jasper,

I don't have a Linux installation of ProGet in front of me, but it's possible that this would work if you renamed the feed to dspdocker (with no capital letters).

Hello Attila,

This is indeed a bug. I've filed PG-1272 to fix this.

Hello Tobias,

PG-1270 will make local packages appear before remote packages in the list, as well as making connector packages appear in the same order that they would appear in the connector.

Hello Fabrice,

I looked at the code and it seems that only NuGet and UPack feeds look at those headers. I've filed PG-1271 to make npm feeds also record deployments.

Hello Yutaccho,

To help me track down the exact cause of this issue, does using a forward slash instead of a backslash in the vsix manifest's <Icon> element cause ProGet to display the correct icon?

Hello Lev,

A possible reason this might be happening is if Apache is caching the 404 error returned by Docker when the client checks for an existing layer and then returning the cached error after the layer is uploaded and the blob URL becomes valid.

Hello Chris,

I don't think Bower feeds store anything on the filesystem (it's all in the database). I've filed PG-1256 to add support for Maven feeds being stored in package stores.

Hello Rob,

I've released version 1.0.1 of the TeamCity extension, which should fix this (or at least give a more sensible error message). It should be available in /administration/extensions.

Hello Subash,

To check whether any connectors are unhealthy, you could use a PowerShell script like this:

$someConnectorsUnhealthy = (
    Invoke-RestMethod 'https://devget.syhapp.com:8798/api/json/Connectors_GetConnectors?API_Key=*******&Feed_Id=***' |
    Where-Object { $_.Status_Code -ne 'H' }).Count -gt 0

After this, $someConnectorsUnhealthy is $True if any connectors for that feed are not in a healthy state, and $False if all connectors are healthy.

If your API key contains = or +, it needs to be URL-encoded, with = replaced by %3D and + replaced by %2B. Alternatively, you can change the API key to be URL-safe.

Hello Dmytro,

I've filed PG-1252 to address this.

Hello Jon,

Is the Approval Required event listener filtered by pipeline stage?

Approval Required listens for Build Promotion Completed events, so the pipeline stage filter should have the name of the stage of the pipeline immediately before the approval gate, not the stage that is blocked by the approval gate.