So if you happen to insert invalid version string when requiring package, it will still write it into composer.json and 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:

$ composer diagnose
        

• I have searched the issues of this repo and believe that this is not a duplicate.
• I have searched the documentation and believe that my question is not covered.

Feature Request

Path-dependencies in Poetry can be [optionally marked as `'dev

• /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/

What Renovate type, platform and version are you using?

Doesn't matter.

Describe the bug

The table that's used in https://github.com/

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

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.

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.