Please describe the feature/suggestion

The url schema for a package.json schema is amazing, I love that I can take this and share it with coworkers. The sorting of Size high -> low does not currently get encoded though, so when a coworker opens up my link, they can't see the same ordering I expected them to

Describe the solution you'd like

Encode the alphabetical selection and t

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

While inspecting the installer, I noticed the fallbacks for Linux / OSX when appdirs isn't available (in data_dir()).

Wouldn't it make sense to add an if for Windows based on %APPDATA% or %LOCALAPPDATA%, before resorting to globally installing appdirs?

Description

Running the following command:
./scancode -clpieu --json-pp facet_summary.json samples --summary --facet dev=*.java --summary-by-facet

Generates the following Error

ERROR: failed to run post-scan plugin: summary-by-facet:
Traceback (most recent call last):
  File "/home/ayansm/Desktop/GSoD/scancode-toolkit-versions/scancode-toolkit-3.1.1/src/scancode/cli.py", lin

See scala/scala-xml#359 (comment).

Add support for SPM (Swift Package Manager) when installed through Apple Xcode.

The code at

https://github.com/oss-review-toolkit/ort/blob/fd1b62a799523b55871cd04001ddfe1e6262da0f/analyzer/src/main/kotlin/managers/Stack.kt#L113-L140

can be simplified now that Stack 2.3.1 supports ls dependencies json.

Optional dependencies should not be treated as a "dependency" kind, of which there are only three -- regular, build, and dev. "Optional deps" should instead be handled as a boolean flag, which is what cargo does. A dependency can be both a build dependency and optional simultaneously, but currently cargo-deps will erase one of these.

Optional dependencies can be displayed with a dashed line.