release-please-action VS release-please-demo

For automating releases based on conventional commits, I used the google-github-actions/release-please-action@v3 action.

If you are using GitHub Action, you can try this https://github.com/google-github-actions/release-please-action

Release Please Action is a GitHub action created by Google to automate releases with Conventional Commit Messages. As you merge PR's into your main branch, the action will create/update a new release branch that automatically adds your commits to a changelog and bumps the version according to your commits. When you're ready to release your changes, merging the PR will cause a new GitHub release to be created and released. We can even automate publishing to package registries like RubyGems!

# frozen_string_literal: true require_relative "lib/release/please/demo/version" Gem::Specification.new do |spec| spec.name = "release-please-demo" spec.version = Release::Please::Demo::VERSION spec.authors = ["Andrew Mason"] spec.email = ["[email protected]"] spec.summary = "Demo of release-please." spec.description = "A demo gem showing how to use release-please to automatically version gems." spec.homepage = "https://github.com/andrewmcodes/release-please-demo" spec.license = "MIT" spec.required_ruby_version = Gem::Requirement.new(">= 2.4.0") spec.metadata = { "bug_tracker_uri" => "#{spec.homepage}/issues", "changelog_uri" => "#{spec.homepage}/blob/main/CHANGELOG.md", "documentation_uri" => spec.homepage.to_s, "homepage_uri" => spec.homepage.to_s, "source_code_uri" => spec.homepage.to_s } spec.files = Dir.chdir(File.expand_path(__dir__)) do `git ls-files -z`.split("\x0").reject { |f| f.match(%r{\A(?:test|spec|features)/}) } end spec.bindir = "exe" spec.executables = spec.files.grep(%r{\Aexe/}) { |f| File.basename(f) } spec.require_paths = ["lib"] end