New feature motivation

I've added semantic-release to some of my projects. Unfortunately, due to trial and error some of my pushes didn't get published. I can push a fix and thus publish a new release, but then the previous would-have-been release and its changelog seems to be lost. How would I recover or include the changelog of a failed release?

I had a look at the FAQ, but it only contai

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

Is there a list of all the possible labels/annotations that keel uses? I went through all the documentation but didn’t any any place that list them all. Could you please have a section in the Guide that list all the labels/annotations?

Also, why are labels and annotations used interchangeably? It doesn’t matter if either is used? Examples in the Guide sometimes using labels and sometimes using

Like

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

Got this message:

? Are you using GitHub Enterprise? No
ERR! semantic-release Error: GitHub repository URL is invalid: https:undefined.git

This was caused by the repo being SSH based, not HTTP(s). Took a while to figure this out, a clearer error message would make sense and make this easily fixable.

Code here:
https://github.com/semantic-release/cli/blob/d2b48b0ef70e327ae591a3

Relevant API guidelines

The Version type currently uses public fields, which is convenient for construction and destructuring, but not ideal for future-proofing. It means new fields can't be added to Version without a breaking change, and the types of those fields are fixed (the `pre: Vec

Situation

At the moment, this project uses and supports Python 2.7. As we all know, Python 2.7 is going out of maintenance soon ("retire") and it's not clear what the project is going to do.

After disussing #160, we found out that the project doesn't have a clear statement or information regarding the retirement of Python 2.7 (neither in issues, README, nor documentation). Maybe I have mi

Feature request

Use update-notifier to notify users if they're using an older version.

cz check --rev-range master..HEAD currently only shows the latest commits that do not follow the pattern. It would be more convenient if these ill-formatted are showed at once

Below is a snippet for the gitlab ci that uses the all-in-one executable checked into the repo to create a version file. If the binary stored in the repo is not desired, a container with the binary installed can be made.

The script just does the following:

1. getting the branch from gitlab environment
2. [setting the bran

I had to use versioning-bundle on ApliPlatform so I had to create simple normalizer for that.

use ApiPlatform\Core\Documentation\Documentation;
use ApiPlatform\Core\Swagger\Serializer\DocumentationNormalizer;
use Shivas\VersioningBundle\Service\VersionManager;
use Symfony\Component\Serializer\Normalizer\NormalizerAwareInterface;
use Symfony\Component\Serializer\Normalizer\NormalizerAwa