v3.7.2

• Fix getting a tag from $GITHUB_EVENT_PATH environment variable in action (#23, thanks @linde12)
• Fix only github.com is allowed as host name for GHE environment
• Do not download files on Git LFS when updating changelog file in action (#24)
• Update Go module dependencies including go-github v58

v3.7.1

• Ensure a trailing / in the API base URL set in GITHUB_API_BASE_URL environment variable
• Show a diff of updated changelog in action output instead of printing an entire changelog
• Update google/go-github from v40 to v45
• Improve help description of -r option

v3.7.0

• Add -r option to specify a remote URL of repository.

  # Generate changelog for rhysd/changelog-from-release
  changelog-from-release -r 'https://github.com/rhysd/changelog-from-release'

• Fix repeating Git tag name in a release heading when a release title already includes it (#20). For example, when a release title is v1.2.3 with some features and its Git tag is v1.2.3, the generated heading is:
  • until v3.7.0: v1.2.3 with some features (v1.2.3)
  • from v3.7.0: v1.2.3 with some features
• Ensure spaces are trimmed from release title and release name.

v3.6.1

• Fix 404 response is not handled when trying to resolve private renamed repositories. (#19)
  • For private repositories, repository rename is not resolved because GitHub always returns 404 even if an authentication token is set. Please ensure the Git remote URL in your local repository is up-to-date when running changelog-from-release command in this case.

v3.6.0

• If you enable protected-branch, rhysd/changelog-from-release/action action cannot push a commit directly to the branch. Instead, use pull_request input to create a pull request to update the changelog. (#17)

  - uses: rhysd/changelog-from-release/action@v3
    with:
      file: CHANGELOG.md
      github_token: ${{ secrets.GITHUB_TOKEN }}
      pull_request: true

v3.5.2

• Check and follow redirects for Git remote URLs. This check is necessary to resolve renamed old repositories correctly. (#16)
• Avoid unnecessary memory allocation when no reference link is included in changelog.
• Update dependencies to include golang.org/x/* packages which were newly managed as Go modules.

v3.5.1

• Add -d option to include/exclude drafts in generated changelog. (thanks @paescuj, #15)

  # Exclude drafts from the output
  changelog-from-release -d=false > CHANGELOG.md

• Include version of changelog-from-release in the footer of generated output
• Remove a single space which were prepended to a footer line
• Do not fail when no release is found since an empty changelog is a good start point of development

v3.4.0

• Add -i option to ignore release tags by regular expression pattern. For example, if your project has nightly tag release for nightly builds, it can be excluded as follows:

  changelog-from-release -i '^nightly$' > CHANGELOG.md

• Add -e option to extract release tags by regular expression pattern. For example, if your project uses v{major}.{minor}.{patch} format for release tags, they can be extracted as follows:

  changelog-from-release -e '^v\d+\.\d+\.\d+$' > CHANGELOG.md

• Allow multiple drafts in releases. For including draft releases, see the FAQ for more details.

v3.3.0

• Add args input to the action to define command line arguments passed to changelog-from-release command.

  - uses: rhysd/changelog-from-release/action@v3
    with:
      file: CHANGELOG.md
      github_token: ${{ secrets.GITHUB_TOKEN }}
      # Pass `-l 2` to use `##` instead of `#` for each release section
      args: -l 2

• Add header and footer inputs to the action to insert templates before/after the generated changelog. The following step inserts the header and the footer.

  - uses: rhysd/changelog-from-release/action@v3
    with:
      file: CHANGELOG.md
      github_token: ${{ secrets.GITHUB_TOKEN }}
      args: -l 2
      header: |
        Changelog
        =========
  
        This is header.
      footer: |-
  
        This is footer.

• Report an error when the release is not associated with any Git tags. This can happen when the release is a draft.
• Fix release date is broken when the release is a draft. Instead of published date, created date is used in the case.
• Add FAQ section to readme document. Currently two topics are described.
  • How to update changelog before adding the release tag?
  • How to insert some templates at top/bottom of generated changelog?

v3.2.0

• Add -l option to set heading level of each release sections. For example, -l 2 uses ## instead of # for each release sections.
• Use Go 1.19 to build release binaries.
• Go module path was changed from github.com/rhysd/changelog-from-release to github.com/rhysd/changelog-from-release/v3 since go install without version specifier does not work in recent Go toolchain. (#14)