awesome-repositories.com
Blog
awesome-repositories.com

Entdecke die besten Open-Source-Repositories mit KI-gestützter Suche.

EntdeckenKuratierte SuchenOpen-Source-AlternativenSelf-hosted SoftwareBlogSitemap
ProjektÜber unsRanking-MethodikPresseMCP-Server
RechtlichesDatenschutzAGB
© 2026 Bringes Technology SRL·VAT RO45896025·hello@awesome-repositories.com
·

68 Repos

Awesome GitHub RepositoriesDependency Versioning

Managing and updating semantic version strings for project dependencies within a manifest.

Distinct from Version Upgrades: Focuses on updating version strings in manifest files rather than general system software installation upgrades

Explore 68 awesome GitHub repositories matching devops & infrastructure · Dependency Versioning. Refine with filters or upvote what's useful.

Awesome Dependency Versioning GitHub Repositories

Finde die besten Repos mit KI.Wir suchen mit KI nach den am besten passenden Repositories.
  • homebrew/legacy-homebrewAvatar von Homebrew

    Homebrew/legacy-homebrew

    26,849Auf GitHub ansehen↗

    This project is a command line package manager and dependency management engine used for installing, updating, and removing software packages across different operating systems. It functions as a package recipe system and software repository administrator, utilizing declarative scripts to define software sources, build arguments, and installation steps. The system operates as a binary distribution platform that compiles source code into pre-compiled binaries and distributes them through remote repositories. It includes an automated version tracker that monitors upstream software releases and

    Forks, commits, and pushes version updates for installation recipes via automated workflows.

    Auf GitHub ansehen↗26,849
  • npm/npmAvatar von npm

    npm/npm

    17,620Auf GitHub ansehen↗

    npm is a JavaScript package manager and dependency management tool. It serves as a command line interface for interacting with a central registry of shareable JavaScript code modules, allowing for the installation and management of third-party libraries. The project handles Node.js package distribution by publishing code to a registry and managing project environment versioning to prevent breaking changes. It provides the necessary infrastructure for JavaScript dependency management and frontend build automation. Core capabilities include the ability to install project dependencies, resolve

    Manages and updates semantic version strings for project dependencies within the manifest to prevent breaking changes.

    Auf GitHub ansehen↗17,620
  • homebrew/homebrew-coreAvatar von Homebrew

    Homebrew/homebrew-core

    15,383Auf GitHub ansehen↗

    This project is a Ruby-based package definition repository that functions as a cross-platform package manager and software dependency resolver for macOS and Linux. It provides a centralized system for installing, updating, and managing software through a Git-based distribution model. The system distinguishes itself through a binary package distribution network that produces pre-compiled bottles to avoid local compilation from source. It utilizes a Ruby-based domain specific language to define installation recipes and employs a distributed version control architecture to synchronize these defi

    Implements rules to prevent specific software packages from being automatically upgraded.

    Rubycoreformulaehacktoberfest
    Auf GitHub ansehen↗15,383
  • golang/depAvatar von golang

    golang/dep

    12,737Auf GitHub ansehen↗

    This project is a dependency management tool for Go designed to track and lock package versions to ensure reproducible builds across different environments. It functions as a version lock file manager, recording complete snapshots of the dependency graph to prevent version drift, and as a semantic version constraint resolver that calculates compatible package versions. The tool orchestrates a local vendor directory, mirroring external source code to enable offline builds and source auditing. It utilizes a combination of static analysis to discover required libraries and a logic engine to inte

    Provides utilities for refreshing pinned package versions to the latest compatible releases based on defined constraints.

    Godependency-managergolangpackage-manager
    Auf GitHub ansehen↗12,737
  • emdash-cms/emdashAvatar von emdash-cms

    emdash-cms/emdash

    10,887Auf GitHub ansehen↗

    EmDash is an open-source content management system built on Astro that combines a visual admin panel with a plugin-driven architecture and server-side rendering. It provides a complete content management system with structured content modeling, a rich text editor using Portable Text format, and a TypeScript API for type-safe content queries. The system supports authentication through passkeys, OAuth 2.1, and external providers, with role-based access control and fine-grained permission scopes. What distinguishes EmDash is its plugin development framework, which supports both native plugins ru

    Updates plugin packages and core CMS to latest versions, then rebuilds the site.

    TypeScriptastrocmsemdash
    Auf GitHub ansehen↗10,887
  • aosp-mirror/platform_frameworks_baseAvatar von aosp-mirror

    aosp-mirror/platform_frameworks_base

    10,812Auf GitHub ansehen↗

    This project provides the core framework and system API layer for the Android operating system. It consists of the fundamental Java and C++ libraries that define system behavior and establish the interface contracts required for system applications and hardware abstraction. The project includes a runtime optimizer used to reduce startup time and improve execution speed by pre-compiling methods and configuring boot images. It also features a software quality toolchain that enforces code formatting, audits commit metadata, and manages API compatibility to ensure stable interface contracts acros

    Relocates external library packages to internal namespaces during the build process to prevent classpath conflicts.

    Java
    Auf GitHub ansehen↗10,812
  • google/osv-scannerAvatar von google

    google/osv-scanner

    10,565Auf GitHub ansehen↗

    osv-scanner is a software composition analysis tool and vulnerability scanner that checks project dependencies and container images against the Open Source Vulnerabilities database. It functions as a dependency remediation tool and can be integrated into custom Go applications as a programmable security library. The project distinguishes itself through a remediation workflow that includes an interactive terminal user interface and automated scripting for upgrading vulnerable packages in lockfiles and manifests. It employs call-graph reachability analysis to determine if vulnerable code is act

    Forces a specific dependency version in a manifest to resolve vulnerabilities when automatic updates fail.

    Goscannersecurity-auditsecurity-tools
    Auf GitHub ansehen↗10,565
  • lsposed/magiskonwsalocalAvatar von LSPosed

    LSPosed/MagiskOnWSALocal

    10,535Auf GitHub ansehen↗

    MagiskOnWSALocal is a toolkit and set of scripts designed to integrate root access and Google Apps into the Windows Subsystem for Android. It functions as a customization utility to provide administrative control over the virtualized Android environment. The project enables the installation of Magisk root binaries and the integration of Google Play Store services. It includes capabilities for removing default application marketplaces and modifying system settings to customize the subsystem. The toolset manages subsystem maintenance through version updates that preserve user data. It also pro

    Provides script-based capability to install newer system versions while preserving user data.

    Shellandroidgoogle-appsmagisk
    Auf GitHub ansehen↗10,535
  • tjunnone/npm-check-updatesAvatar von tjunnone

    tjunnone/npm-check-updates

    10,264Auf GitHub ansehen↗

    npm-check-updates is a command line utility and package version manager used to find and apply newer versions of dependencies within npm package manifests. It functions as a dependency version validator that identifies outdated packages and updates version strings in the project manifest to the latest available releases. The tool features an interactive CLI for selecting specific packages to upgrade through a prompt-based interface. It distinguishes itself by enforcing version cooldown periods to restrict the adoption of very recent releases and providing a mechanism to iteratively install up

    Overwrite version strings in a package file to the latest available versions while preserving semantic versioning policies.

    TypeScript
    Auf GitHub ansehen↗10,264
  • thoughtbot/guidesAvatar von thoughtbot

    thoughtbot/guides

    9,556Auf GitHub ansehen↗

    This project is a software engineering style guide and a curated collection of architectural patterns and coding standards. It provides a multi-language coding standard to ensure maintainable software across Ruby, Python, JavaScript, and Swift. The project establishes a development workflow specification for version control, continuous integration, and peer review to maintain a linear project history. It also includes a web accessibility framework based on ARIA and WCAG standards, using design tokens and semantic HTML patterns to build inclusive interfaces. The guides cover a broad range of

    Defines strategies for versioning gem dependencies and testing against multiple environments.

    Ruby
    Auf GitHub ansehen↗9,556
  • release-it/release-itAvatar von release-it

    release-it/release-it

    8,975Auf GitHub ansehen↗

    release-it is a Git release automation tool designed to coordinate software versioning, changelog generation, and package publishing. It functions as a semantic versioning manager that increments project versions and updates configuration files based on semantic standards or custom schemes. The project distinguishes itself through a plugin-based extension system that allows for custom versioning and publishing logic. It supports complex project structures via monorepo versioning automation to synchronize internal dependencies across multiple workspaces. The tool covers a broad range of capab

    Synchronizes version bumps across multiple workspaces and updates internal dependencies within monorepo structures.

    JavaScriptautomationbumpchangelog
    Auf GitHub ansehen↗8,975
  • theme-next/hexo-theme-nextAvatar von theme-next

    theme-next/hexo-theme-next

    8,261Auf GitHub ansehen↗

    NexT is a responsive, elegant static blog theme for Hexo that generates HTML pages from Markdown posts. It is designed as a pre-built visual design for the Hexo framework, producing mobile-friendly layouts that adapt across devices with support for dark mode and multiple visual schemes. The theme distinguishes itself through extensive customization options, including five built-in code highlighting themes for technical blog posts and a multilingual interface supporting over 15 languages. It offers configuration flexibility by allowing theme settings to be stored either in the main Hexo config

    Provides guidance for updating Hexo and its plugins to versions compatible with the latest theme release.

    Stylushexohexo-themetheme-next
    Auf GitHub ansehen↗8,261
  • masterminds/glideAvatar von Masterminds

    Masterminds/glide

    8,095Auf GitHub ansehen↗

    Glide is a Go dependency management tool that fetches, pins, and vendors external packages to enable reproducible builds across environments. It stores project-specific copies of Go packages in a vendor directory, isolating dependencies per project to avoid version conflicts, and supports fetching packages from Git, Mercurial, Bazaar, and Subversion repositories. The tool resolves dependency versions using semantic versioning ranges and operators, and generates a lock file that records exact commit IDs for all transitive dependencies. Glide distinguishes itself with an interactive version wiz

    Restricts acceptable dependency versions using operators like greater-than, less-than, and wildcards.

    Gogogolangpackage-management
    Auf GitHub ansehen↗8,095
  • jazzband/pip-toolsAvatar von jazzband

    jazzband/pip-tools

    8,005Auf GitHub ansehen↗

    pip-tools is a set of utilities for Python dependency pinning, lockfile management, and virtual environment synchronization. It functions as a requirement compiler that resolves high-level package declarations into a pinned list of specific versions and content hashes to ensure repeatable builds across different environments. The tool differentiates itself by providing a mechanism to refresh locked dependencies to their latest compatible versions without manual editing. It supports a layered dependency workflow, allowing one requirements file to act as a constraint for another to maintain com

    Provides utilities to refresh pinned package versions to the latest compatible releases.

    Python
    Auf GitHub ansehen↗8,005
  • nvie/pip-toolsAvatar von nvie

    nvie/pip-tools

    8,005Auf GitHub ansehen↗

    pip-tools is a set of command line utilities for compiling high-level Python dependency lists into pinned requirements files. It functions as a dependency lock tool and requirements compiler that resolves transitive dependencies to produce a deterministic list of packages. The project enables the maintenance of separate production and development dependency layers through layered requirement constraints. It supports targeted package upgrades and the generation of content hashes to verify package integrity during installation. The toolset covers dependency locking, version updates, and virtua

    Refreshes pinned package versions to the latest compatible releases based on defined version constraints.

    Python
    Auf GitHub ansehen↗8,005
  • conventional-changelog/standard-versionAvatar von conventional-changelog

    conventional-changelog/standard-version

    7,971Auf GitHub ansehen↗

    Standard-version is a semantic versioning release automation tool and Git versioning manager. It calculates the next semantic version by parsing commit messages that follow the Conventional Commits specification and automates the process of updating project files and creating signed Git tags. The tool distinguishes itself by generating formatted changelogs automatically from commit history and providing a release process simulation to preview version bumps without modifying files or Git history. It supports pre-release version management for experimental builds and allows for manual version o

    Allows specification of which files to read and update using built-in or custom version tools.

    JavaScriptchangelogcligit
    Auf GitHub ansehen↗7,971
  • operator-framework/operator-sdkAvatar von operator-framework

    operator-framework/operator-sdk

    7,658Auf GitHub ansehen↗

    The Operator SDK is a framework for building, packaging, and managing custom controllers that extend the Kubernetes API. It serves as a toolset for defining new API types and implementing reconcile loops to automate the lifecycles of complex applications. The project provides specialized support for creating operators based on Helm charts or Ansible playbooks, allowing users to maintain a desired cluster state using existing automation tools. It includes a dedicated system for packaging controllers into standardized container image bundles for distribution via the Operator Lifecycle Manager.

    Updates project dependencies and build manifests to ensure compatibility with newer cluster versions.

    Gokubernetesoperatorsdk
    Auf GitHub ansehen↗7,658
  • google/closure-compilerAvatar von google

    google/closure-compiler

    7,663Auf GitHub ansehen↗

    This project is a JavaScript optimizer, minifier, module bundler, transpiler, and static analysis tool. It provides a compilation pipeline designed to shrink file sizes and improve runtime performance. The system utilizes a multi-pass compilation process to perform dead code elimination, global name mangling, and static type inference. It identifies unreachable functions and unused variables to reduce the final output size and detects potential runtime errors without executing the code. The tool manages assets through dependency resolution, code chunking, and bundle management. It ensures co

    Renames third-party library packages to prevent version conflicts when multiple versions of a dependency are used.

    JavaScript
    Auf GitHub ansehen↗7,663
  • vladmandic/sdnextAvatar von vladmandic

    vladmandic/sdnext

    7,139Auf GitHub ansehen↗

    SD.Next is an all-in-one web interface and multi-backend inference engine for generating, editing, and processing images and videos using diffusion models. It functions as a comprehensive tool for diffusion model management and an automated image processing pipeline for bulk operations. The project is distinguished by its hardware-backend abstraction layer, which provides automatic detection and acceleration for NVIDIA CUDA, AMD ROCm, Intel OpenVINO, and DirectML. It features a headless generative API and a programmatic command interface, allowing users to trigger tasks via REST API or CLI wi

    Forces specific versions of the Torch library to ensure compatibility with older hardware.

    Pythonai-artcaptiondiffusers
    Auf GitHub ansehen↗7,139
  • serpentai/serpentaiAvatar von SerpentAI

    SerpentAI/SerpentAI

    6,979Auf GitHub ansehen↗

    SerpentAI is a game AI development kit and computer vision framework designed for building autonomous agents that interact with video games. It serves as a game input automation tool and a machine learning model integration engine, allowing developers to create agents that perceive game states and execute actions. The framework utilizes a plugin-based agent architecture to provide modular extensions for game-specific logic and behaviors. It features a specialized system for training, bundling, and deploying machine learning classifiers to recognize visual contexts and game states in real time

    Provides utilities for updating the framework to the latest compatible releases from a package registry.

    Pythonartificial-intelligencecomputer-visiondeep-learning
    Auf GitHub ansehen↗6,979
Vorherige123…4Nächste
  1. Home
  2. DevOps & Infrastructure
  3. Version Upgrades
  4. Dependency Versioning

Unter-Tags erkunden

  • Automated Recipe UpdatesAutomatic updates of package source URLs and checksums in installation recipes when new versions are released. **Distinct from Dependency Version Updates:** Updates the recipe definition itself rather than just bumping a pinned version in a lockfile.
  • Component Version Upgrades1 Sub-TagProcesses for updating specific software components to maintain security and community synchronization. **Distinct from Dependency Version Updates:** Distinct from dependency version updates [f14_mt4], which focus on package manifest constraints, this is about operational component patching.
  • Dependency RenamingRenaming of third-party packages to avoid conflicts when multiple versions of the same dependency are required. **Distinct from Dependency Versioning:** Focuses on renaming packages for conflict resolution rather than updating semantic version strings.
  • Dependency Version Updates3 Sub-TagsUtilities for refreshing pinned package versions to the latest compatible releases. **Distinct from Dependency Versioning:** Specifically focuses on updating pinned versions based on constraints rather than just managing version strings.
  • Environment Dependency TrackingCaptures specific versions of installed libraries and hardware details to ensure environment reproducibility. **Distinct from Dependency Versioning:** Distinct from Dependency Versioning: focuses on recording the actual state of the environment for a specific run rather than managing manifest files.
  • Gradle Version Catalogs1 Sub-TagCentralized dependency management using a Gradle version catalog for consistent library and plugin versions. **Distinct from Dependency Versioning:** Distinct from Dependency Versioning: focuses on Gradle's version catalog feature for centralized management, not general version string updates.
  • Interactive Version ResolversWalks through each dependency, detects semantic versioning, and prompts the user to choose version ranges for the manifest file. **Distinct from Dependency Versioning:** Distinct from Dependency Versioning: adds an interactive wizard that prompts the user for version choices rather than automatically updating version strings.
  • Monorepo Versioning3 Sub-TagsAutomates version increments across multiple workspaces and synchronizes internal dependency versions. **Distinct from Dependency Versioning:** Specifically handles multi-package synchronization in monorepos rather than single-manifest dependency updates.
  • Update ExclusionsRules for preventing specific dependencies or version ranges from being upgraded. **Distinct from Dependency Versioning:** Focuses on ignoring specific packages during updates, not general semantic version management.
  • Version ConstraintsSpecifying acceptable version ranges using operators to prevent breaking changes in dependencies. **Distinct from Dependency Versioning:** Focuses on the definition of constraints (e.g., >=1.2,<2.0) rather than the act of updating the version string.
  • Version Dependency SuppressionOmits the Dependencies field from the version output unless the verbose flag is used. **Distinct from Dependency Versioning:** Distinct from Dependency Versioning: focuses on conditionally suppressing dependency display in version output, not managing version strings.
  • Version Monitoring ToolsTracks package registries for new dependency versions and calculates compatibility scores from public CI results. **Distinct from Dependency Versioning:** Distinct from Dependency Versioning: focuses on proactive monitoring and compatibility assessment rather than just managing version strings in manifests.
  • Version OverridesCapabilities to force a specific dependency version, superseding all other constraints in the dependency graph. **Distinct from Dependency Versioning:** Distinct from Dependency Versioning: focuses on the act of overriding/forcing a version to resolve conflicts, not general manifest management.
  • Version Range ConstraintsSpecification of compatible version ranges using operators to ensure dependency stability. **Distinct from Dependency Versioning:** Focuses on defining the constraints themselves rather than the process of upgrading version strings.
  • Version-Based Filtering1 Sub-TagFiltering dependencies based on name, type, or semantic version level to determine update eligibility. **Distinct from Dependency Versioning:** Specifically filters which dependencies are eligible for updates based on metadata and version level.
  • Versioned Library Dependency DeclarationsDeclares which version of a library a service depends on using a decorator on the namespace or version enum. **Distinct from Dependency Versioning:** Distinct from Dependency Versioning: focuses on declaring library version dependencies in API definitions, not general manifest version strings.
  • Versioned Package Dependency DeclarationsStates that a namespace or versioning enum member relies on a specific version of another versioned package. **Distinct from Dependency Versioning:** Distinct from Dependency Versioning: focuses on declaring dependencies on specific versions of versioned packages, not general version string management.
  • Vulnerability Window MappingAnalysis of dependency version relationships to identify specific release windows susceptible to known vulnerabilities. **Distinct from Dependency Versioning:** Focuses on security vulnerability windows rather than general version string management or updates.