Jacob Bolda

Some of these were added/fixed in #211 and will be published with #212. You may be able to try using the release branch for the moment until it is published....

Looking at specific version numbers for prereleases, we could use `git rev-list --count` to retrieve the number of commits on a branch and use that as the incremental number when...

# Preleases and Preview Packages ## Terminology A typical release includes running the `version` and `publish` commands. This will increment version numbers, update the changelogs, and then publish the packages...

@FredZhao-at I was on extended vacation, not actively involved with Gatsby anymore, and do not receive any compensation for this so I have personally attempted to maintain it at the...

I have elected to [move this plugin into the GUC](https://github.com/gatsby-uc/plugins/issues/368), and these issues may be best addressed there.

Thinking about the time element more, it seems like an arbitrary number would still fall down (say for cases where a package is published once a quarter, what time range...

Building off of discussion in https://github.com/jbolda/covector/issues/189, it feels like this gets abstracted over long term for the 90% use case. I suspect in the exact manner you are imagining that...

Also touched on this in https://github.com/jbolda/covector/issues/133.

We have added the `use` option in #280. It sets some presets one of which does a `fetch` and handles the various cases more directly, including this one.

Currently there is only one format of changelog, but it is setup as a template which shouldn't be difficult to accept user config. Publishes are not specifically tied to a...