There's a section about Uninstall existing npm, but the recommendations for upgrading are scattered in the issues.

The relationship between node, npm and nvm is not clear and it's not obvious if upgrading npm should be done through nvm or at least in a way that doesn't break nvm.

Is it okay to include "rich" content like images, links to other projects, blockquotes, etc. in the changelog? While these things might make it more "enjoyable" to read, I can also see where they might make it harder for users to copy/paste and more complex for machines to parse. Whatever is considered the best practice with regards to rich content, I feel like that should be included in the FAQ.

Issue

In v7.1.0:

When you declare a custom file in bumpFiles standard-version will no longer update normal package.json, composer.json, lockfiles, etc. declared in the defaults.

This is fine (I don't think this is a bug because maybe you don't want it to bother with the defaults), but I think it should be mentioned in the documentation that when you do declare bumpFiles in your c

Description & context

Users can specify names for their nodes to identify them more easily. When a name is not explicitly specified, Kedro auto-generates a default name. You can see this in the name property on Node.
The current auto-generated name for a node looks something like this: func_name(inputs) -> outputs. (see implementation of __str__ method on the Node class)

This is

As per SO the following needs to be added to setup() for PyPI to correctly render.
long_description_content_type='text/markdown'

Update:
This solved my PyPI README markdown rendering issue.
At some point I'll look at putting together a pull request.

In this quickstart, Info() has been replaced by OpenApiInfo():
https://github.com/microsoft/aspnet-api-versioning/wiki/API-Documentation#aspnet-core

Thanks for all you do to maintain this site.

Having a sample starting point may save other people a lot of time. There are probably many other ways to accomplish the goal, but this is a generic way that is easily reusable for any Visual Studio language.

Here is what I did:

1. From the Package Manage Console, run

Install-Package GitVersion.CommandLine

2. Put the following text into a powershell script such as 'gitversionwc

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?

I'm not sure how it's meant to be used, but it seems the only way to find the path I want would be to scroll through the 173 pages of entries. I think there should be some form of searching in there (for paths, not resources).

Like

• npm-check
• https://github.com/peerigon/updtr#readme

The long-term plan for v1.0 is to focus on :refreshVersions instead of :buildSrcVersions

refreshVersions

Starting from release 0.8.0 the plugin is now called and contain only the task refreshVersions

plugins {
  id("de.fayard.refreshVersions").version("0.8.x") // or newer
}

buildSrcVersions

We are not quite ready yet to extract the useful parts of `buildS

This would give us a better starting point for getting a Kubernetes cluster up and running in the future.
Maybe also using the GraalVM with native binaries. As we didn't use reflection and other stuff which would prohibit the use of native binaries the only thing now is that we moved to Java 13 and the GraalVM just started to support Java 11.

fetchPypi just calls fetchurl underneath but has a slightly different calling syntax in order to construct the URL. It would be great to track these external dependencies using niv. :-)

@adamdubiel In the document, users should get the same output as the currentVersion task, but actually it is not. there is another issue #207 talks about this issue, but it has been closed.

In my scenario, I need the currentVersion output to update my grad

Hi, The documentation mentions that paper_trail can "revert back to anytime in history", but I can't figure out exactly how to revert or reconstitute an older version of a model. Is there documentation somewhere that describes this?

Also, it's mentioned that you "don't delete your paper_trail versions, instead you can merge them", but I can't figure out exactly how to merge them. Is there docum

'draft' function is defined in the lib/composure.bash

Unfortunately the name of this function is clashing with the draft binary Draft actively developed for the K8S domain.
Simply renaming 'draft' function here to say 'draft_fun' would do.

ref: originally raised as #1453 for Bash-It

sbt-dynver uses git describe --abbrev=8 and the pattern matches on exactly 8 characters for the abbreviated SHA-1.

git describe --abbrev=<n> produces a shortened representation of