Skip to content

`gsub!': can't modify frozen String (FrozenError) causing changelog generator exiting with error code 1 #977

Closed
@kian2attari

Description

@kian2attari

Describe the bug

Recent runs of the action have suddenly started failing with the following error:

Screen Shot 2021-08-10 at 8 28 35 PM

Screen Shot 2021-08-10 at 8 28 02 PM

For reference, here is the error text:

/Users/runner/hostedtoolcache/Ruby/2.6.8/x64/lib/ruby/gems/2.6.0/gems/github_changelog_generator-1.16.4/lib/github_changelog_generator/generator/generator.rb:160:in `gsub!': can't modify frozen String (FrozenError)
Associating PRs with tags: 9/188
	from /Users/runner/hostedtoolcache/Ruby/2.6.8/x64/lib/ruby/gems/2.6.0/gems/github_changelog_generator-1.16.4/lib/github_changelog_generator/generator/generator.rb:160:in `remove_old_fixed_string'
Associating PRs with tags: 10/188
	from /Users/runner/hostedtoolcache/Ruby/2.6.8/x64/lib/ruby/gems/2.6.0/gems/github_changelog_generator-1.16.4/lib/github_changelog_generator/generator/generator.rb:63:in `block in compound_changelog'
Associating PRs with tags: 11/188
	from /Users/runner/hostedtoolcache/Ruby/2.6.8/x64/lib/ruby/gems/2.6.0/gems/async-1.30.1/lib/async/task.rb:260:in `block in make_fiber'

This is my partial config file, it was working perfectly

          unreleased-label=New features since previous release **${{ env.LATEST_RELEASE_TAG }}**
          output=CHANGELOG.md
          configure-sections={"enhancements":{"prefix":"###  🚀  Enhancements:","labels":["enhancement"]},"bugs":{"prefix":"###  🐛  Bug fixes:","labels":["bug"]},"security":{"prefix":"###  🔒  Security:","labels":["security"]},"documentation":{"prefix":"###  📜  Documentation:","labels":["documentation"]},"tests":{"prefix":"###  🧪  Tests:","labels":["tests"]}}
          compare-link=true
          unreleased-only=true
          date-format=%m/%d/%Y
          header-label=<!-- Changelog -->
          pr-label=### ➕  Other merged pull requests 
          issues=false
          issues-wo-labels=false

To Reproduce
Steps to reproduce the behavior:
This is currently happening on a private repo but I'll update this once I have a test repo running with the issue

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions