Support

• N

  [feature] ProGet: Send test notifications from 'Notifiers & Webhooks'
  • Nils Nilsson  

  6
  1
  Votes
  6
  Posts
  19
  Views

  

  @sigurd-hansen_7559 wow very cool! We didn't anticipate anyone would customize these templates beyond adding a variable or two, so it it didn't seem to make a lot of sense to invest in a proper editor (like we have in the other products) Anyway, it'd be interesting to see what kind of templates you develop.
• A

  Support for Azure Key Vault references in Connector credentials
  • alkhleif_2585  

  2
  0
  Votes
  2
  Posts
  3
  Views

  

  Hi @alkhleif_2585 , There isn't much demand for this kind of feature (I think we've only seen one or two requests for this over very many years) so it's not on our roadmap. And it's unlikely we will add it to the roadmap considering that it would be quite costly to build, support, and maintain. Especially considering that we'd need to support all of the major "vaults" out there as well. It doesn't seem to add much value to ProGet as these types of read-only credentials can be very long living (several years) without any security risk, and take just a few minutes to rotate when needed. That being said, you could probably write a "sync script" pretty easily that continuously updates the connector credentials by connecting to the vault and then updating it via the API. Cheers, Steve
• J

  Cargo feed returning 500 Internal Server Error
  proget error 500 cargo • • joris.guex  

  3
  0
  Votes
  3
  Posts
  16
  Views

  J

  Hi @atripp, We have now updated to ProGet 2026.3 and can confirm this is now working as expected. Thank you for your prompt help.
• V

  Issue with Composer Connector: ProGet blocks non-standard version names from Packagist
  • vdubrovskyi_1854  

  2
  0
  Votes
  2
  Posts
  8
  Views

  

  Hi @vdubrovskyi_1854 , Without knowing which specific package you're referring to, it's hard to give a more specific example. Historically, Packagist was effectively a database of "GitHub Repository pointers" and Composer was effectively just a wrapper around the Git client. They can both still operate in that mode, and needs to for older, non-standard packages. I suspect that's the type of package you're referring to here. ProGet's Composer feeds work with "packages" (i.e. not the GitHub pointers), which account for nearly all of the modern packages on Packagist.org. For the small number of packages that don't follow the standard (mostly older, legacy packages), you'll need to download them, properly package them, and then upload them to follow the standard. Unfortunately there's no technically feasible/sensible way to solve this problem - since it would require ProGet to serve as a GitHub pointer database, which just doesn't make sense. Cheers, Steve
• J

  Block recently published - Metadata filter ?
  • jens.viebig_4541  

  1
  1
  Votes
  1
  Posts
  9
  Views

  No one has replied

• 

  Unable to login with Active Directory with Proget 2026.1
  • aristo_4359  

  7
  0
  Votes
  7
  Posts
  43
  Views

  

  @pg_user_8607 Given the fix is about searching in AD I think the pull request is indeed related, as there is no other error I can find other than unable to find the user(s) in the User Directories Test.
• 

  After upgrading to 2026 https no longer works
  • Valentijn  

  5
  1
  Votes
  5
  Posts
  41
  Views

  

  Hi, I was on a short vacation but today I upgraded to 2026.3 (build 14) without any problems. This probably fixed it: PG-3299 2026.3 FIX: Hostname based binding fails when hosting on Windows with HTTP.SYS Kind regards, Valentijn
• B

  Scheduled Task is failing due to invalid script identifier
  • brandon_owensby_2976  

  3
  0
  Votes
  3
  Posts
  23
  Views

  B

  Hi Alana, Just wanted to let you know that restarting the service did fix the issue. Thank you for the suggestion. Brandon
• A

  Malformed upload-time (2-digit fractional seconds) breaks pip ≥ 25.3 on Python 3.10
  • appplat_4310  

  3
  0
  Votes
  3
  Posts
  18
  Views

  A

  Hi @gdivis , thanks for the quick turnaround. Everything is working as expected with the new version. Cheers
• 0

  PEP 700 conformance for PyPI feeds
  • 0xFFFFFFFF  

  13
  0
  Votes
  13
  Posts
  99
  Views

  

  @Ashley thanks for letting us know!
• B

  Git Repository Monitor - Create build when a PR is created/updated
  • brandon_owensby_2976  

  7
  0
  Votes
  7
  Posts
  24
  Views

  

  Hi @brandon_owensby_2976 , Thanks for the feedback, we appreciate it :) There's definitely a value in building before merging; if you haven't already, I'd check out that feature branch article, as it outlines the pattern we use for it. In general, the way I would try to configure is: consider using a releaseless-build if you don't yet know the release it's targeting use a different piepline so it's visually clear; the stages may be Build -> Test -> Merge clean up the builds aftewards That said, this isn't the most popular workflow in BuildMaster, so it may not be the most intuitive to implement or feel a bit clunky. We don't have a lot of public examples, but the inedo-docs application is the closest to a Gitflow, releaseless type of workflow. Commits to master branch auto-deploy to live site, where as branches can only go to test: https://buildmaster.inedo.com/applications/136/overview No idea if that's helpful, but just FYI Cheers, Alana
• B

  BuildMaster - api/json/SecureResource_GetSecureResources fails with 500 Internal Server Error
  • brandon_owensby_2976  

  2
  0
  Votes
  2
  Posts
  11
  Views

  

  Hi @brandon_owensby_2976 , Looks like this is a regression in BuildMaster 2025 from a library upgrade; we will address it via BM-4017 in an upcoming release, either this Friday or the following cycle. Thanks, Alana
• P

  Container image size calculation does not always work
  • pg_user_8607  

  3
  0
  Votes
  3
  Posts
  10
  Views

  P

  Thank you very much for the detailed answer!
• P

  SCA page throws an exception for anonymous users
  • pg_user_8607  

  2
  0
  Votes
  2
  Posts
  11
  Views

  

  Hi @pg_user_8607 , Thanks for the bug report; this will be fixed via PG-3296 in the next maintenance release (scheduled next Friday). It was a problem in the redirect to the /log-in page, so of course if you log-in first, the error will not occur. Cheers, Alana
• C

  ProGet 2026.1 (PostgreSQL) — Two issues with vulnerability management
  • cssccmgroup_4090  

  4
  0
  Votes
  4
  Posts
  19
  Views

  

  Hi @cssccmgroup_4090, I created a private ticket on your behalf. You can see it by navigating to https://my.inedo.com/tickets. Please upload the SBOM through that ticket. Thanks, Dan
• D

  PostgreSQL DB Location
  • david.williams_3389  

  3
  0
  Votes
  3
  Posts
  12
  Views

  D

  Hi Alana Thanks for confirming that. It was just our preference with the way we organise things, not a big deal.
• 

  This topic is deleted!
  • InteXX  

  1
  0
  Votes
  1
  Posts
  2
  Views

  No one has replied

• V

  Composer Feed: InvalidPackageException (Missing required property: name) when caching zip artifact causes 404
  • vdubrovskyi_1854  

  2
  0
  Votes
  2
  Posts
  10
  Views

  

  Hi @vdubrovskyi_1854 , Thanks for the detailed reproduction information; I debugged/fixed this, and it will be in the next maintenance release of ProGet via PG-3290, scheduled for Friday of this week. As for the underlying issue, the problem was that there were two composer.json files in the zip file. ProGet was opening build/composer.json instead. I didn't test a work-around, but in theory you should be able to just download the zip file directly, delete build/composer.json from it, and upload it to ProGet. I also updated the error message to make somethign like this a little easier to track if it comes up again ("An unexpected error occurred: Error parsing "voku-simple_html_dom-716822e/build/composer.json" as a Composer manifest file (Missing required property: name).") Cheers, Alana
• B

  SBOM/RMetadata support for pypi feed type
  • brodie.mclennan_5777  

  3
  0
  Votes
  3
  Posts
  29
  Views

  B

  Thanks for the quick turn around. We are happy to wait for next release, and can report back if we find any further issues.
• N

  Project-scoped permissions not working as expected
  • Nils Nilsson  

  2
  0
  Votes
  2
  Posts
  18
  Views

  

  Hi @Nils-Nilsson, Thanks for bringing this to our attention. This looks to be a regression that happened right before release. I have created a ticket, PG-3289, to track the fix and we will release it this Friday in ProGet 2026.2. Thanks, Rich