chore: release dev

[Koenkk]

🤖 I have created a release beep boop

1.37.1

1.37.1 (2024-05-09)

Bug Fixes

• Add Helm chart (#21852) (b2e8b3e)
• Add settings for finer control over debug log level (#22426) (eb49f52)
• Fix logger crashing on restart (#22565) (d26ccae)
• Fix MQTT ECONNREFUSED error ECONNREFUSED error after 1.37.0-1 zigbee2mqtt/hassio-zigbee2mqtt#605 (a0c9a17)
• ignore: update dependencies (#22456) (b754b9d)
• ignore: update zigbee-herdsman to 0.46.0 (#22380) (55b5f91)
• ignore: update zigbee-herdsman to 0.46.1 (#22439) (329d832)
• ignore: update zigbee-herdsman to 0.46.2 (#22470) (e4c9bac)
• ignore: update zigbee-herdsman to 0.46.3 (#22471) (316654b)
• ignore: update zigbee-herdsman to 0.46.4 (#22501) (e44608a)
• ignore: update zigbee-herdsman to 0.46.5 (#22552) (6bcb4b6)
• ignore: update zigbee-herdsman to 0.46.6 (#22558) (989f667)
• ignore: update zigbee-herdsman-converters to 19.33.0 (#22381) (907591c)
• ignore: update zigbee-herdsman-converters to 19.35.0 (#22442) (beedfae)
• ignore: update zigbee-herdsman-converters to 19.36.0 (#22472) (358e2ee)
• ignore: update zigbee-herdsman-converters to 19.36.1 (#22503) (3544d51)
• ignore: update zigbee-herdsman-converters to 19.37.0 (#22531) (6b886f6)
• ignore: update zigbee-herdsman-converters to 19.37.1 (#22549) (cc9a95c)
• ignore: update zigbee2mqtt-frontend to 0.6.166 (#22410) (5899436)
• ignore: update zigbee2mqtt-frontend to 0.6.167 (#22419) (23e97d0)

1.37.1

1.37.1 (2024-05-09)

Bug Fixes

• Add Helm chart (#21852) (b2e8b3e)

---

This PR was generated with Release Please. See documentation.

[Koenkk]

@jlpedrosa looks good now, many thanks!

[jlpedrosa]

@jlpedrosa looks good now, many thanks!

At your service, feel free to ping me if this is causing issues. I will test this as soon as the release is created.

[Koenkk]

@jlpedrosa yes, will ping you with the next release, since we are planning a hotfix release it should come soon.

[jlpedrosa]

I am not sure if it was the force push the reason why the CI is stuck, in actions all seems correct....

[jlpedrosa]

Since the CI generates another commit, not sure if the force push is confusion to the CI system? maybe instead of force pushing, maybe an empty commit?

git commit --allow-empty -m "Empty-Commit"

[jlpedrosa]

@Koenkk I see one step is failing from the previous steps of the CI.

Let me have a look

[jlpedrosa]

Humm, the output is empty, there's not a single log line.
It seems

node scripts/generateChangelog.js $MASTER_Z2M_VERSION $MASTER_ZHC_VERSION $MASTER_ZH_VERSION $MASTER_FRONTEND_VERSION >> ../changelog.md

is having issues, I don't have a clue of Javascript, but I don't think it's using any file that has been modified by the helm chart.
I have tried to reproduce it locally with the two branches checked out, but it works on my pc. Not sure what I can do to help.

[Koenkk]

@jlpedrosa the branch name changed due to jlpedrosa@04e0e3f, fixed it in 834626d

[jlpedrosa]

Yeah, that makes sense, but I don't see the CI trigger for the next commit... it's strange:

I am not sure if it's the force push...

[jlpedrosa]

I see the CI is configured for push, not sure why the other commit is not triggering it. I don't know if it's the loop protection from GH.

zigbee2mqtt/.github/workflows/ci.yml

Line 3 in ee5cf5a

on: [pull_request, push]

[Koenkk]

GH doesn't run pipelines for commits done via Github actions, adding the token should fix it (aecdfe6)

[jlpedrosa]

GH doesn't run pipelines for commits done via Github actions, adding the token should fix it (aecdfe6)

Yeah, that decision was apparently intentional to prevent loops. that is what I meant.

When you use the repository's GITHUB_TOKEN to perform tasks, events triggered by the GITHUB_TOKEN, with the exception of workflow_dispatch and repository_dispatch, will not create a new workflow run. This prevents you from accidentally creating recursive workflow runs.

https://docs.github.com/en/actions/security-guides/automatic-token-authentication#using-the-github_token-in-a-workflow

[Koenkk]

Works now! 🥳

[jlpedrosa]

🥳 !!!

Thanks man!