You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This repository uses a very old form of the Arcade SDK publishing infrastructure. That infra is planned to be removed from the Arcade SDK by the end of the first half of January 2020. The repository build definition(s) need to be updated to use the new publishing infrastructure, otherwise its official builds will fail to publish. It’s a simple process, documentation about it is here. If you have any question or problem please reach out to @JohnTortugo, @riarenas, @mmitche or .NET Core Engineering
Once we remove the old infrastructure you might not be able to get an updated Arcade SDK (or Arcade updates at all) if you’re not using the new publishing infrastructure.
The text was updated successfully, but these errors were encountered:
adaggarwal
transferred this issue from dotnet/source-build-reference-packages
Jan 13, 2020
adaggarwal
changed the title
Use new Arcade SDK publishing infrastructure
[Ref Packages] Use new Arcade SDK publishing infrastructure
Jan 13, 2020
adaggarwal
changed the title
[Ref Packages] Use new Arcade SDK publishing infrastructure
[source-build-reference-packages] Use new Arcade SDK publishing infrastructure
Jan 13, 2020
This repository uses a very old form of the Arcade SDK publishing infrastructure. That infra is planned to be removed from the Arcade SDK by the end of the first half of January 2020. The repository build definition(s) need to be updated to use the new publishing infrastructure, otherwise its official builds will fail to publish. It’s a simple process, documentation about it is here. If you have any question or problem please reach out to @JohnTortugo, @riarenas, @mmitche or .NET Core Engineering
Once we remove the old infrastructure you might not be able to get an updated Arcade SDK (or Arcade updates at all) if you’re not using the new publishing infrastructure.
The text was updated successfully, but these errors were encountered: