dependency-manager
A package manager or package management system is a collection of software tools that automate the process of installing, upgrading, configuring, or removing computer programs for a computer's operating system in a consistent manner.
Here are 280 public repositories matching this topic...
-
Updated
Sep 5, 2020 - Go
-
Updated
Oct 12, 2020 - Ruby
- /pnpm/packages/audit - #2862
- /pnpm/packages/package-store a86209b67fccc37c5b017dd9ce61d2b3f9a55789
- /pnpm/packages/cafs #2867
- /pnpm/packages/client pnpm/pnpm#2877
- /pnpm/packages/fetch pnpm/pnpm#2878
- /pnpm/packages/filter-lockfile #2887
- /pnpm/packages/filter-workspace-packages #2887
- /pnpm/packages/
-
Updated
Sep 25, 2020 - Ruby
-
Updated
Oct 8, 2020 - TypeScript
What would you like Renovate to be able to do?
I would like Renovate to renovate the .bazelversion file, which is a file that says what Bazel version the project is using. This file is consumed by Bazelisk to fetch and run the correct Bazel version.
Did you already have any implementation ideas?
- Check what the [latest releas
Is your feature request related to a problem? Please describe.
Not related to a problem
Describe the solution you'd like
We opened #808 to discuss how we might use GitHub actions. At the time, this repo didn't have actions enabled. Now that it does, we should try them out for some of the things in that thread.
_Edit from @arschles - we have focused this issue to just the twitte
-
Updated
May 30, 2020 - JavaScript
-
Updated
Oct 8, 2020 - CMake
-
Updated
Aug 25, 2020 - Swift
-
Updated
Oct 6, 2020 - Python
-
Updated
Sep 10, 2020
-
Updated
Feb 5, 2019 - C#
-
Updated
Oct 1, 2020 - Ruby
-
Updated
Dec 20, 2019 - Python
-
Updated
Oct 6, 2020 - CMake
-
Updated
Oct 8, 2020 - Python
-
Updated
May 16, 2020 - Python
fury layer init --git should initialize a Git repo in the layer directory, and fury layer init --github-actions should set up CI for the repo with Github Actions. We can add support for Travis, Jenkins and anything else later.
-
Updated
Apr 23, 2018 - Python
stefanmaric / g
-
Updated
May 11, 2020 - Shell
-
Updated
Oct 5, 2020 - PowerShell
-
Updated
Oct 13, 2020 - Python
-
Updated
Sep 10, 2020 - Dockerfile
Currently build agents run mbt version command at the end of the build. We should add a smoke test for each command (mbt describe | build | apply) to this list for release builds.


So if you happen to insert invalid version string when requiring package, it will still write it into
composer.jsonand nothing works after that. So for example;composer require phpunit/phpunit:"8.3.3 as ^8.3"My
composer.json:{ "require": { "phpunit/phpunit": "8.3.3 as ^8.3" } }Output of
composer diagnose: