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

poetry add git+https://github.com/AGeekInside/fastapi-jinja.git result in exception since it is tires to checkout master branch.

poetry add git+https://github.com/AGeekInside/fastapi-jinja.git

Updating dependencies
Resolving dependencies...

  CalledProcessError

  Command '['git', '--git-dir', 'C:/Users/n2/AppData/Local/Temp/pypoetry-git-fastapi-jinjau3blv69e/.git', '--work-tr

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

Feature: Print out what git/svn status returns, if uploading of a package fails because of uncommited changes.

It happend on our CI (Jenkins) few times now that upload failed because of uncommited changes.
We clear the whole repository folder after a build process to save storage. So we couldn't check it by ourself after the failed build.
To get the uncommited changes and fix them, we

We have a lot of long lines, let's shorten them.

Be smart about making the choices to split lines, no fake internet points for cutting strings and making them unreadable!

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'

I'm referring to the Rubygems security guide.

How about calculating the checksum as part of the rake build task?

I currently add the following rake build:checksum task to all my gems, but in order to promote checksums, it might be better to implement this on Bundler:

namespace :build

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