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

Is your feature request related to a problem? Please describe.
The default release text with Changelog and Docker images is nice. Also the option to custom release headers and footers. But it is too static. In my case I not only want to provide links on how to docker pull a certain image, but also provide instructions to install a Helm chart with a specific just-released image version. e.g.

javadocRelease/javadocDebug tasks failing for android-gradle-plugin > 3.6.0

Execution failed for task ':library:javadocRelease'.

Javadoc generation failed. Generated Javadoc options file (useful for troubleshooting):

it was not able to find any android related class

error: package android.view does not exist
import android.view.View;

after 100 errors task fails

similar to

Exposing category name as a "Change Template" variable would be useful for generating change logs in this format:

- ADDED: X (#100)
- ADDED: Y (#101)
- FIXED: Z (#99)

Relevant documentation:

Variable	Description
$CATEGORY	The category title of the pull request, e.g. Features.

As far as I know you can't do that with Replacers, as you only have one cat

Since PyScaffold's putup command might be used from any virtual environment or even when no virtual environment is activated, it makes sense to mention pipx in PyScaffold's documentation. This tool allows you to install putup systemwide in a non-invasive way. We should also add this to our unit tests.

Hi!

release {
    versionPropertyFile = "version.properties"
    afterEvaluate {
        buildTasks = listOf(":aem:assembly:full:build")
    }
}

afterEvaluate {
    throw GradleException("${project.version}")
}

ends with

* What went wrong:
A problem occurred configuring root project 'example'.
> unspecified

however if I put version to `gradle.pr

We have a workflow where we want do generate the release notes only from pull requests and mention the pull request author. I have found no way to do this yet...

It took a few attempts to find a solution to get a version # to tag the releases with. In my case I have a VERSION file containing the version number, such as 0.1.0. This solution should be applicable even if the desired version is stored elsewhere so long as it can be accessed from a bash shell.

The first step gets the version via a run command and sets the output. See the [documentation for

@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! I can't find any clear documentation about the asset_content_type field -- what the options are, what this does etc.

If there is some documentation in another place, maybe it'd be worth linking to it in the readme?

Sorry if there's been an existing issue for this -- I couldn't find any.

I've just stumbled upon conventional-github-releaser, having used standard-version for awhile and searching for a way to customize how the CHANGELOG.md is generated. It appears that the templating system may be provided by the underlying conventional-changelog tool, but I can't seem to find any documentation at any level of these tools which actually walks you through how to create a custom templ

Currently https://escape.ankyra.io/docs/ site is missing that information.
It's impossible for new uses to discover such features are existing at all.
Docs need updates to reflect changes introduced in #22 and #24 #21

twine check can detect problems such as bad README formatting or classifiers. I think it's worth running before the upload step?

When "org.shipkit.javadoc" plugin is applied, then release notes should contain a link (as a badge) to the published Javadoc.

By default, the link should point to the specified directory ("javadoc.repositoryDirectory") and branch "javadoc.repositoryBranch" (see ShipkitConfiguration.java for more configuration options).

There should be also a possibility to point to some class, e.g. for Mock

We should cryptographically sign the distributed release-tool.phar so people can validate it. Also, we should check the signature in the self-update command (#44).