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
        

The current scenario when virtualenvs.in-project = true is specified, is that we default to creating .venv as the virtual environment. This needs to be improved to support multiple versions of python.

Ideally we will end up having a structure similar to the one below.

.
└── .venv
    ├── 3.7
    ├── 3.8
    └── 3.9

Concensus Required

• Directory structure and na

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?

1. 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

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.