I am using semantic tags such as 1.2.0, 1.2.1, 1.2.2, or v1.2.0, v1.2.1, v1.2.2 and still getting empty body.

Hello, and thank you for this github action.
I am not sure, but this line

In one of our projects we have always the same changlelog generated.

I don't have a large set of debugging available, so I am sorry by advance if this is an error.
Thank you

Hi,

I am using this workflow and it is working fine. I would like to get the ${{ steps.changelog.outputs.changes }} and send it via email. But I am not getting anything. I am using this code to get the changes:

• name: Send mail
  uses: dawidd6/action-send-mail@v3
  with:
  # Required mail server address:
  server_address:
  # Required mail server port:
  server_port:
  # Optional (recommended): mail server username:
  username:
  # Optional (recommended) mail server password:
  password:
  # Required mail subject:
  subject:
  # Required recipients' addresses:
  to:
  # Required sender full name (address can be skipped):
  from:
  # Optional whether this connection use TLS (default is true if server_port is 465)
  secure:
  # Optional plain body:
  body: ${{ steps.changelog.outputs.changes }}
  # Optional unsigned/invalid certificates allowance:
  ignore_cert:
  # Optional converting Markdown to HTML (set content_type to text/html too):
  convert_markdown:
  # Optional priority: 'high', 'normal' (default) or 'low'

I hope you can assist me with this one.
Thank you so much.

• Lisley

Hi,

Would it be possible to update to node 20 as node 16 is deprecated.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: loopwerk/tag-changelog@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/

This commit has a title and a body text, but the release notes only show the title. What happened to the body? Why is it not rendered?

See https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

I just copy the sample workflow code,but when I push a tag to the github,although the workflow work success,the release page only has a record.

I want this option:

It can generate all of commit messages between the latest tag version and the previous tag version when i push a tag version.

Detail sample:

Now my github repositiy has a tag named 0.2.And I publish a tag named 0.3.And there are 7 commit in two tag version.And the release body message also generate 7 commit message .

You may see my reposity,link is https://github.com/stars-one/kxorm

Hope your help,Thanks!

Workflow code:

name: Create Release

on:
  push:
    tags:
      - '*'

jobs:
  create-release:
    runs-on: ubuntu-latest

    steps:
      - name: Checkout
        uses: actions/checkout@v2

      - name: Create changelog text
        id: changelog
        uses: loopwerk/tag-changelog@v1
        with:
          token: ${{ secrets.GITHUB_TOKEN }}
          exclude_types: other,doc,chore

      - name: Create release
        uses: actions/create-release@latest
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        with:
          tag_name: ${{ github.ref }}
          release_name: Release ${{ github.ref }}
          body: ${{ steps.changelog.outputs.changes }} 

I am running into a bit of a snag when setting up the changelog action on one of my repositories. I had previously created two releases before adding this Action, and it looks like I am hitting the following error:

Error: Validation Failed: {"resource":"Release","code":"already_exists","field":"tag_name"}

I am sure that this is user error. How should I setup the action to handle this? Here is a link to my workflow.

Hi,

I am using your Action, but recently I receive this warning:

Node.js 12 actions are deprecated. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/. Please update the following actions to use Node.js 16: loopwerk/tag-changelog

So I request if it is possible to go for Node 16 as described here

https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/

Regards,

DK

Is it possible to be compatible with the first two submissions?

your code

  // Find the two most recent tags
  const { data: tags } = await octokit.repos.listTags({
    owner,
    repo,
    per_page: 10,
  });

  const validSortedTags = tags
    .filter((t) => compareVersions.validate(t.name))
    .sort((a, b) => {
      return compareVersions(a.name, b.name);
    })
    .reverse();

  if (validSortedTags.length < 2) {
    setFailed("Couldn't find previous tag");
    return;
  }

I like to make a new branch when I start working on a fix or a feature.
And I have the habit of creating Merge Commits when merging a pull request into the active branch when I am done.

But it doesn't seem like it picks up all the commit history of the branch when doing it like this?
I seem to recall that it worked previously.

All my commits follow conventional commit format (except for the merge commit).

And then this is what the changelog ends up as: