chore(main): release 0.4.1

[kitchen-porter]

🤖 I have created a release beep boop

0.4.1 (2024-05-19)

Bug Fixes

• Fix release-config (#66) (53c59f1)
• More (#68) (3c82993)
• release-please-config (#69) (e6ea516)

---

This PR was generated with Release Please. See documentation.

[damacus]

@ecottom looks like it still isn't bumping the version file? 🤔

[ecottom]

This is odd because release-please release-pr --token=$env:myaccesstoken --repo-url=sous-chefs/chef-ruby-lvm-attrib --dry-run --target-branch=main indicates it can find the lib/lvm/version.rb and it would be bumped. It looks like the Action that generated this PR used the past config

Run googleapis/release-please-action@v4
  with:
    release-type: ruby
    token: ***
    repo-url: sous-chefs/chef-ruby-lvm-attrib
    github-api-url: https://api.github.com/
    github-graphql-url: https://api.github.com/graphql
    fork: false
    include-component-in-tag: false
    skip-github-release: false
    skip-github-pull-request: false
    changelog-host: https://github.com/

https://github.com/sous-chefs/chef-ruby-lvm-attrib/actions/runs/9146091307/job/25145814587#step:4:2

> Fetching release-please-config.json from branch main
> Fetching .release-please-manifest.json from branch main
√ Building pull requests
√ Building strategies by path
> .: ruby
√ Collecting release commit SHAs
> release search depth: 400
> Fetching releases with cursor undefined
‼ Expected 1 releases, only found 0
‼ Missing 1 paths: .
> looking for tagName: v0.4.0
> found: v0.4.0 675d6f38f4b76705b5bcfee6e3882c9e4e74673e
> release for path: ., version: 0.4.0, sha: 675d6f38f4b76705b5bcfee6e3882c9e4e74673e
√ Collecting commits since all latest releases
> commit search depth: 500
> Set(1) { '675d6f38f4b76705b5bcfee6e3882c9e4e74673e' }
> Fetching merge commits on branch main with cursor: undefined
> Backfilling file list for commit: ee03179eeab690e4a7550b0169dce312c6ac18c1
> Found 2 files
> Backfilling file list for commit: 72b696c564047d884267332243fd4e89b39f486f
> Found 14 files
> Backfilling file list for commit: 5c209093189664f86ec05afed12d41b9d32b71f9
> Found 2 files
> Backfilling file list for commit: ac02d11374f2aea3ddd0f5feeaa821df072eb480
> Found 2 files
> Backfilling file list for commit: 6b690f03c3a6312af7eb3fd727501ea4c2203b47
> Found 3 files
√ Splitting 3 commits by path
√ Building candidate release pull request for path: .
> type: ruby
> targetBranch: main
> commits: 5
√ Considering: 5 commits
> component:
> pull request title pattern: undefined
Would open 1 pull requests
fork: false
title: chore(main): release 0.4.1
branch: release-please--branches--main
draft: false
body: :robot: I have created a release *beep* *boop*
---


## [0.4.1](https://github.com/sous-chefs/chef-ruby-lvm-attrib/compare/v0.4.0...v0.4.1) (2024-05-20)


### Bug Fixes

* Fix release-config ([#66](https://github.com/sous-chefs/chef-ruby-lvm-attrib/issues/66)) ([53c59f1](https://github.com/sous-chefs/chef-ruby-lvm-attrib/commit/53c59f1180d03c74dd5513e2f3a6704597d9581c))
* More ([#68](https://github.com/sous-chefs/chef-ruby-lvm-attrib/issues/68)) ([3c82993](https://github.com/sous-chefs/chef-ruby-lvm-attrib/commit/3c829930cdf73900a6b13eb77a452a0a4cee1d26))
* release-please-config ([#69](https://github.com/sous-chefs/chef-ruby-lvm-attrib/issues/69)) ([e6ea516](https://github.com/sous-chefs/chef-ruby-lvm-attrib/commit/e6ea516797839857aeea1e77186ce27b21b02dd5))

---
This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
updates: 4
> Fetching CHANGELOG.md from branch main
> Fetching lib/lvm/version.rb from branch main
> Fetching Gemfile.lock from branch main
‼ file Gemfile.lock did not exist
> Fetching .release-please-manifest.json from branch main
  CHANGELOG.md:  [class Changelog extends DefaultUpdater]
  lib/lvm/version.rb:  [class VersionRB extends DefaultUpdater]
  Gemfile.lock:  [class GemfileLock extends DefaultUpdater]
  .release-please-manifest.json:  [class ReleasePleaseManifest extends DefaultUpdater]

[ecottom]

Something else might also be going on. I synced my fork with sous-chefs/chef-ruby-lvm-attrib/main and ran release-please release-pr --token=$env:myaccesstoken --repo-url=ecottom/chef-ruby-lvm-attrib --target-branch=main and it did open a PR with a bumped version.

[Stromweld]

I'd suggest testing out the config here https://github.com/test-kitchen/workflow-testing-gem
This we can PR and publish without erroneous versions of real gems getting published or version incremented.

[awrel34]

Hello,
would it be possible to release manually to rubygems while debugging the github actions ?

[awrel34]

@damacus @ecottom
Hello ! Any news on this please ?

[Excalibure86]

Still no news about this?

[Stromweld]

closing this PR in favor of #75