[PR #1436] Onboard onto Central Package Management #1367

New issue

Open

opened 2026-02-26 09:34:34 +03:00 by kerem · 0 comments

kerem commented

2026-02-26 09:34:34 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/NickeManarin/ScreenToGif/pull/1436
Author: @dfederm
Created: 2/18/2026
Status: 🔄 Open

Base: master ← Head: feature/cpm

📝 Commits (1)

c2b03d6 Onboard onto Central Package Management

📊 Changes

6 files changed (+38 additions, -16 deletions)

View changed files

➕ Directory.Packages.props (+22 -0)
📝 Other/Translator/Translator.csproj (+4 -4)
📝 ScreenToGif.Test/ScreenToGif.Test.csproj (+4 -4)
📝 ScreenToGif.Util/ScreenToGif.Util.csproj (+3 -3)
📝 ScreenToGif.ViewModel/ScreenToGif.ViewModel.csproj (+1 -1)
📝 ScreenToGif/ScreenToGif.csproj (+4 -4)

📄 Description

This pull request introduces the NuGet Central Package Management feature to streamline dependency management. Key benefits and changes include:

Centralized Version Management: All NuGet package versions are now managed centrally in the Directory.Packages.props file. This ensures consistency across all projects in the repository.
Simplified Project Files: The individual project files are simplified, as they no longer need to specify version numbers for NuGet packages. This change reduces duplication and the potential for version conflicts.
Ease of Updating Dependencies: Updating a package version is now a matter of changing it in one place, making the process of keeping dependencies up-to-date more straightforward and less error-prone.

By implementing Central Package Versioning, you're taking a significant step towards more efficient and reliable dependency management. This change will be particularly beneficial to assist with tools like Dependabot. These tools automate dependency updates, and having a centralized versioning system significantly enhances their effectiveness, ensuring a smooth and consistent update process.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/NickeManarin/ScreenToGif/pull/1436 **Author:** [@dfederm](https://github.com/dfederm) **Created:** 2/18/2026 **Status:** 🔄 Open **Base:** `master` ← **Head:** `feature/cpm` --- ### 📝 Commits (1) - [`c2b03d6`](https://github.com/NickeManarin/ScreenToGif/commit/c2b03d6263153a2a6485fa0c868160bbd80f30c8) Onboard onto Central Package Management ### 📊 Changes **6 files changed** (+38 additions, -16 deletions) <details> <summary>View changed files</summary> ➕ `Directory.Packages.props` (+22 -0) 📝 `Other/Translator/Translator.csproj` (+4 -4) 📝 `ScreenToGif.Test/ScreenToGif.Test.csproj` (+4 -4) 📝 `ScreenToGif.Util/ScreenToGif.Util.csproj` (+3 -3) 📝 `ScreenToGif.ViewModel/ScreenToGif.ViewModel.csproj` (+1 -1) 📝 `ScreenToGif/ScreenToGif.csproj` (+4 -4) </details> ### 📄 Description This pull request introduces the NuGet [Central Package Management](https://learn.microsoft.com/en-us/nuget/consume-packages/Central-Package-Management) feature to streamline dependency management. Key benefits and changes include: - **Centralized Version Management**: All NuGet package versions are now managed centrally in the `Directory.Packages.props` file. This ensures consistency across all projects in the repository. - **Simplified Project Files**: The individual project files are simplified, as they no longer need to specify version numbers for NuGet packages. This change reduces duplication and the potential for version conflicts. - **Ease of Updating Dependencies**: Updating a package version is now a matter of changing it in one place, making the process of keeping dependencies up-to-date more straightforward and less error-prone. By implementing Central Package Versioning, you're taking a significant step towards more efficient and reliable dependency management. This change will be particularly beneficial to assist with tools like Dependabot. These tools automate dependency updates, and having a centralized versioning system significantly enhances their effectiveness, ensuring a smooth and consistent update process. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>