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
Is your feature request related to a problem? Please describe.
Currently, when a patch is done on a repository (e.g. JNet) the other repositories (e.g. KNet) needs an official delivery to check for issues solved. If GitHub stores packages with patches added in the meantime, at the same latest version, the other repositories can use GitHub as a source instead of NuGet.org.
Describe the solution you'd like
Within the build.yaml, after the packages were built, upload them on GitHub.
Describe alternatives you've considered
Another option is to create pre-release version, however they need a change in many files between and indeed a less automatic management.
Additional context
N/A
The text was updated successfully, but these errors were encountered:
It is not possible to use GitHub NuGet registry without previously removes the uploaded package; indeed it is only possible to remove the entire package on web UI, not a single version. Another option can be to use the uploaded artifact using the counterpart action https://github.com/actions/download-artifact: a check shall be done to verify how to identify the last run-id when the action runs cross-repository.
masesdevelopers
changed the title
Avoid to use GitHub as official repository of images for NuGet packages
Workflows can use latest builds to compile and test current version
Jul 3, 2024
Is your feature request related to a problem? Please describe.
Currently, when a patch is done on a repository (e.g. JNet) the other repositories (e.g. KNet) needs an official delivery to check for issues solved. If GitHub stores packages with patches added in the meantime, at the same latest version, the other repositories can use GitHub as a source instead of NuGet.org.
Describe the solution you'd like
Within the build.yaml, after the packages were built, upload them on GitHub.
Describe alternatives you've considered
Another option is to create pre-release version, however they need a change in many files between and indeed a less automatic management.
Additional context
N/A
The text was updated successfully, but these errors were encountered: