-
Notifications
You must be signed in to change notification settings - Fork 4.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
P.S.A. Packages with explicit agreements in manifests removed #131328
Comments
Affected Packages
|
Removing these packages caused some issues for our organization, as we were relying on some of the packages for automated deployments that started failing while I was on holiday at the end of the year. I think it would have been best to wait until after the holidays to make this change to give everyone some time to make adjustments without running into change freezes or having people out on holiday. |
@denelon Are the relevant teams at Microsoft informed about fixing their respective installers? |
Any update? |
When is the fix (short or long term) coming in? I see the EDIT: I realize that there is the |
The |
Oh ok, should I keep my PR as a draft or should I close and re-open once the solution's out? |
Guys, any update on this issue? |
Hey everyone, we have the updated policy implemented for the community repository. We're now allowing packages to be added back with agreements with explicit switches being passed to installers. |
I'm going to go ahead and close this issue since we have the ability to accept these packages back into the community repository, but I will keep this message pinned until the packages have been added back. |
All removed packages have been restored. I'm unpinning this issue now. |
Several packages were passing explicit arguments representing agreements to the installers to achieve a silent install. These packages are being evaluated to see if they will succeed with a non-interactive configuration with those explicit arguments removed. If they will not succeed, they will be removed.
We are working on a short-term solution to allow agreements in packages for the community repository. We will require agreement Title(s) and URL(s) when these switches are required. The agreement text will still be gated by the verified developer feature.
The text was updated successfully, but these errors were encountered: