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

Homebrew/livecheck provides various automated ways of detecting formulae updates.

Repology provides an API that provides details on whether a Homebrew package is outdated e.g. https://repology.org/metapackage/boost/versions

A separate Ruby application that can be trivially deployed on e

• I am on the latest Poetry version.
• I have searched the issues of this repo and believe that this is not a duplicate. (There are similar tickets, notably #3291 but they aren't specifically targeting a repo hosted on S3/Cloudfront)
• If an exception occurs when executing a c

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

Conan can't work on OpenBSD.

ERROR: Invalid setting 'OpenBSD' is not a valid 'settings.os' value.
Possible values are ['AIX', 'Android', 'Arduino', 'Emscripten', 'FreeBSD', 'Linux', 'Macos', 'Neutrino', 'SunOS', 'Windows', 'WindowsCE', 'WindowsStore', 'iOS', 'tvOS', 'watchOS']

Problem:

It is opaque which service will receive credentials for "npm login". This can lead to leaked credentials.

Logging into a non-standard registry is a 2-command process. Not only that, but one can be logged into multiple registries for various scopes. Give a multitude of registries, when I perform "npm login", depending on the flags, my credentials can be sent to a number of services. I

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

• I'd be willing to implement this feature
• This feature can already be implemented through a plugin

Describe the user story

I was looking into patch and how it works, but the docs didnt give much info. The CLI also didnt. I had to look around to get an idea of it. I thought it worked similar like patch-package. However, it works differently.

**Describe the solution you'

This feature adds a CHANGELOG.md file when running bundle gem mygem in addition to all other gem skeleton files.

I keep adding it myself and it is best practice to keep a changelog. Let me know if there is any reason this was not there yet or if there is anything I can improve. Thanks!

The design for volta list specified that we would output both the default version from the user's toolchain and the version set in a local package:

$ volta list all --format=plain
runtime [email protected]
runtime [email protected]
runtime [email protected] (default)
runtime [email protected] (current @ ~/node-only/package.json)

We currently only print the (current @ ...) when in a package