Skip to content

chore(deps): update dependency github_changelog_generator to v1.18.0#112

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/github_changelog_generator-1.x
Open

chore(deps): update dependency github_changelog_generator to v1.18.0#112
renovate[bot] wants to merge 1 commit intomainfrom
renovate/github_changelog_generator-1.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Mar 13, 2026

This PR contains the following updates:

Package Change Age Confidence
github_changelog_generator "1.16.4""1.18.0" age confidence

Release Notes

github-changelog-generator/github-changelog-generator (github_changelog_generator)

v1.18.0

Compare Source

Changes since v1.17.0

Fixed bugs:

  • Fix critical bugs: race condition, wrong tag lookup, branch memoization, nil sections (#​1067) by @​skywinder
  • Pull requests missing #​971

Closed issues:

  • Undefined method map for nil:NilClass in client.branches(user_project).map #​1020
  • commits_in_branch': undefined method `map' for nil:NilClass (NoMethodError) #​1016
  • github-changelog-generator 1.15 Error #​758
  • The link to Full Changelog is wrong #​918
  • Different results when generating a CHANGELOG.md #​891

Other:

Full Changelog

This Changelog was automatically generated by github_changelog_generator

v1.17.0

Compare Source

Full Changelog

Implemented enhancements:

Fixed bugs:

  • Verbose output says token is not in use #​1047
  • No common ancestor between XXXXX and v1.30.0. #​994
  • `gsub!': can't modify frozen String (FrozenError) causing changelog generator exiting with error code 1 #​977
  • Error: log writing failed. Attempt to unlock a mutex which is locked by another thread/fiber #​974
  • Generated log path incorrect #​892
  • --no-issues-wo-labels should not exclude Pull Requests #​821
  • Mixed line endings in output file when using 'release summaries' #​715
  • Error when run against module with a second module merged into it. #​665
  • Specifying since-tag on a PR merge commit can cause that PR to be included #​615
  • Cannot use --exclude-tags option after upgrade to Ruby 2.4.0 #​469
  • Can't exclude issues without labels #​302
  • Cannot exclude PRs without labels. #​292
  • PR appears as part of "unreleased #​282
  • old merged PR listed for a wrong release #​256
  • Fix SSL certificate errors and update RuboCop config #​1064 (skywinder)
  • Avoid processing a single commit multiple times #​1058 (smortex)
  • Fix missing release branch when looking for commits #​1055 (sdb9696)
  • fix: remove an unneeded shebang and fix another one #​987 (MatteoPierro)
  • Fix for echoing the complete output path #​986 (anakinj)
  • Use mutable empty strings when needed #​981 (adangel)
  • Get commits from release branch #​979 (pokey)
  • section: Make sure to normalize line endings in body #​808 (lazyfrosch)

Closed issues:

  • Allow passing location of configuration file to ParseFile #​925
  • Use GitHub's GraphQL v4 API #​524
  • [wishlist] --include-tags-regex #​376
  • Add support for custom sections #​316

Merged pull requests:


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/github_changelog_generator-1.x branch from 3c70d82 to 2282eff Compare March 18, 2026 05:38
@renovate renovate bot changed the title chore(deps): update dependency github_changelog_generator to v1.17.0 chore(deps): update dependency github_changelog_generator to v1.18.0 Mar 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants