Do you want to request a feature or report a bug?
feature request

What is the current behavior?
Currently yarn why won't indicate any package info in the resolutions field

If the current behavior is a bug, please provide the steps to reproduce.

1. install a package with any version, e.g "pkg": "^1.0.0"
2. add resolutions field in package.json, pkg: "1.0.0"
3. upd

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
        

In https://github.com/Homebrew/brew/pull/7371/files I have added lots of # TODO: check could be in RuboCop comments to Library/Homebrew/dev-cmd/audit.rb. These indicate that the audit check/problem below does not rely on Formula state so could be moved to a RuboCop (https://github.com/Homebrew/brew/tree/master/Library/Homebrew/rubocops) to be faster, more reliable and provided in-editor to u

Now building for iOS is not covered fully in README.md, starting with Xcode 11 there is no Linked Frameworks and Libraries anymore and this section become one with Embedded Binaries. Documentation needs to be updated in this place:

https://github.com/Carthage/Carthage#if-youre-building-for-ios-tvos-or-watchos

Following documentation step-by-step now will cause build error with Xcode 11 d

I often forget the exact syntax and semantics of the version constraints.
It would be great to have that readily accessible from the command line
with (for example) dep help constraints.

pod --version
1.9.1

• [x ] I've read and understood the CONTRIBUTING guidelines and have done my best effort to follow.

Report

Most legitimate bots I see on a server report who they are. When I saw user agent of "Ruby" it made me feel something suspicious is going on. Then I did a test and cocoapods jus

The documentation does not provide a simple things we can follow from start to finish.

The introduction section is really "installation", and go quiet deep in the different option to install the tools.

Quick Start

# install poetry
curl -sSL https://raw.githubusercontent.com/python-poetry/poetry/master/get-poetry.py | python
# Creating a new project
poetry new poetry-demo
# Add a de

Library name:
https://github.com/pboettch/json-schema-validator

Library description:
JSON schema validator for JSON for Modern C++

Source repository URL:
https://github.com/pboettch/json-schema-validator

Project homepage (if different from the source repository):

Anything else that is useful to know when adding (such as optional features the library may have that should be included)

I have a project that is in a monorepo and uses yarn right now.

I'm considering migrating to pnpm for the monorepo, as well as all other projects I contribute to, as I have a small SSD as local storage (and with Windows...). However, it would be ideal if there was compatibility between yarn's workspaces and pnpm, so that we don't have to jump "all in" to it.

To this end, yarn allows packages

Hi,
On this page:
https://chocolatey.org/docs/helpers-install-chocolatey-package

Look the example 3:

$url = 'https://somewhere.com/file.msi'
$url64 = 'https://somewhere.com/file-x64.msi'

It's never calling these variables.

Maybe:
A: a step is missing in the example
B: there's a copy paste error in the example

Can you please have a look and fix it?

Cheers,

Create an schedule for stable releases and document steps on how stable releases should be considered and accepted (release candidates, minor test period required, etc).

Out of the top of my head I can think of the following requirements for a release to be considered as stable:

• At least a week of being released
• No bugs reported caused by that release

Also to consider:

• Release

I wrote a recipe using a requires.
The required dependancy was misconfigured and the self.deps_cpp_info['required'].include_paths was set to [].

An alert indicating that the dependancy was misconfigured and its include_path was incorrect would be time saving.

More precisely, in build_info.py , in _filter_path we call os.isdir.path(p) and a warning here could be more than apprec

Describe the bug

The release docs have a few issues.

First, they don't have information on how to do patch releases. There should be some things added:

• Code freeze is not required for patch releases
• You should branch from the previous release branch and cherry pick (e.g. git cherry-pick $COMMIT) commits from master into the new branch
• Before you tag the branch / do the GH

What would you like Renovate to be able to do?
Has configuration options to be able to create as draft PR.

Describe the solution you'd like
if configuration like draftPR as boolean is true then renovate-bot just create PR as draft in github. (default value should be false)

Misc
Github API for create pull request as draft is already provided https://developer.github.com/v

Do you have a reproduction script?
Using any project:
bundle install --standalone

What were you expecting to happen?
The generated setup.rb does not contain relative path operators.
E.g.

$:.unshift "#{path}/#{ruby_engine}/#{ruby_version}/gems/rake-13.0.1/lib"

What actually happened?
The generated paths contain /../ relative path operators.

path = File.

hab sup run is used to start a Supervisor, and hab svc load is used to instruct a running Supervisor to load a new service.

However, as a way to have allow Habitat containers to start-and-load a service in a single ENTRYPOINT, hab sup run takes options and arguments of hab svc load to effectively perform both operations at once.

However, this has led to confusion, in that it is cur