chore(deps): update it-at-m/lhm_actions action to v1.0.1

[renovate]

This PR contains the following updates:

Package	Type	Update	Change	OpenSSF
it-at-m/lhm_actions	action	patch	v1.0.0 -> v1.0.1

---

Release Notes

it-at-m/lhm_actions (it-at-m/lhm_actions)

v1.0.1

Compare Source

Bug Fixes

• add pr checklist actions (6b2f0fe)

---

Configuration

📅 Schedule: Branch creation - "* 0-3 * * 1" in timezone Europe/Berlin, 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.

[coderabbitai]

Walkthrough

This pull request updates the versions of multiple GitHub Actions in various workflow files. The changes update actions from version v1.0.0 to v1.0.1 by referencing new commit hashes. The workflows affected include those for documentation deployment, Maven and NPM builds, releases, and image creation. No modifications have been made to workflow logic or error handling.

Changes

File(s)	Change Summary
.github/.../deploy-docs.yml	Updated action-build-docs and action-deploy-docs from v1.0.0 (commit 07f8f5fe…) to v1.0.1 (commit 14080db5…).
.github/.../maven-node-build.yml	Updated action-checkout, action-npm-build, action-maven-build, and action-build-image from v1.0.0 to v1.0.1 with new commit hashes.
.github/.../maven-release.yml	Updated action-maven-release, action-build-image, and action-create-github-release from v1.0.0 to v1.0.1 with new commit identifiers.
.github/.../npm-release.yml	Updated action-npm-release, action-build-image, and action-create-github-release from v1.0.0 to v1.0.1 by referencing newer commit IDs.

Possibly related PRs

• Changing reference of actions from .github to lhm_actions repo #776: Updates the source paths of the same actions, directly relating to the version update changes.
• chore(deps): pin it-at-m/lhm_actions action to 07f8f5f #793: Modifies the same actions in .github/workflows/deploy-docs.yml while pinning them to a specific commit hash.

Suggested reviewers

• devtobi
• hupling

Poem

I’m a rabbit hopping in the code,
Skipping old commits on a bright new road.
With each action updated, I cheerfully bound,
New versions and hashes all around.
🐇✨ Happy hops in every line of code!

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5725d71 and bf0424e.

📒 Files selected for processing (4)

• .github/workflows/deploy-docs.yml (1 hunks)
• .github/workflows/maven-node-build.yml (1 hunks)
• .github/workflows/maven-release.yml (3 hunks)
• .github/workflows/npm-release.yml (3 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: build (refarch-backend)

🔇 Additional comments (12)

.github/workflows/deploy-docs.yml (2)

27-27: Action Update for Build Docs
The commit hash for action-build-docs has been updated to the v1.0.1 release. This change is consistent with the overall version bump and should integrate seamlessly with the deployment workflow.

---

31-31: Action Update for Deploy Docs
The update for action-deploy-docs to v1.0.1, via the new commit hash, aligns with the intended patch upgrade. Make sure that any documentation regarding deployment procedures reflects this updated version.

.github/workflows/npm-release.yml (3)

35-35: Action Update for NPM Release
The action-npm-release reference has been updated to v1.0.1 using the new commit hash. This update is straightforward and maintains consistency with the patch release objectives.

---

44-44: Action Update for Build Image in NPM Release
The update to the action-build-image reference ensures that the container image build step benefits from the latest fixes in v1.0.1.

---

60-60: Action Update for Create GitHub Release
The action-create-github-release has been successfully updated to v1.0.1. This will incorporate the bug fixes related to the pull request checklist improvements.

.github/workflows/maven-node-build.yml (4)

24-24: Action Update for Checkout
The action-checkout step has been updated to use the v1.0.1 commit hash. This ensures that the checkout process benefits from the latest improvements.

---

27-27: Action Update for NPM Build
The new commit hash for action-npm-build reflects the update to v1.0.1. This change preserves consistency in the build process for node-based projects.

---

32-32: Action Update for Maven Build
The update for action-maven-build ensures that the Maven build step is consistent with the patch release version v1.0.1.

---

36-36: Action Update for Build Image
The new commit hash in action-build-image confirms the update to v1.0.1. This consistency helps to mitigate version mismatches across different workflows.

.github/workflows/maven-release.yml (3)

32-32: Action Update for Maven Release
The action-maven-release has been updated to v1.0.1. This ensures that the release process for Maven-based projects reflects the latest bug fixes and improvements.

---

46-46: Action Update for Build Image in Maven Release
The updated action-build-image reference ensures consistency across workflows and benefits from the v1.0.1 patch release improvements.

---

61-61: Action Update for Create GitHub Release in Maven Release
The update for action-create-github-release to v1.0.1 aligns with the overall patch upgrade strategy, ensuring released assets are processed with the latest enhancements.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[hupling]

@devtobi bitte einen Auto merge einbauen.

[devtobi]

@devtobi bitte einen Auto merge einbauen.

Wie soll das gehen, wenn ihr als CODEOWNER mit drin steht? GitHub kann hier nicht unterscheiden ob der PR durch einen Bot oder durch einen Mensch eingestellt wurde.

[hupling]

doch es geht. wir haben das ja auch im .github Projekt gemacht.