chore(deps): update github-actions - autoclosed

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
Songmu/tagpr	action	minor	v1.3.0 -> v1.4.0
actions/upload-artifact	action	patch	v4.3.5 -> v4.3.6

---

Release Notes

Songmu/tagpr (Songmu/tagpr)

v1.4.0

Compare Source

• fix typo by @​mocyuto in https://github.com/Songmu/tagpr/pull/175
• fix: Unstable search issue behavior by @​snaka in https://github.com/Songmu/tagpr/pull/178

actions/upload-artifact (actions/upload-artifact)

v4.3.6

Compare Source

---

Configuration

📅 Schedule: Branch creation - "before 8am on monday" in timezone Asia/Tokyo, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• 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 update enhances the GitHub Actions workflows by upgrading the dependency versions for tag generation and artifact upload processes. The Songmu/tagpr action has been updated from version v1.3.0 to v1.4.0, while the upload-artifact action has been upgraded from v4.3.5 to v4.3.6. These changes may introduce new features and improvements, streamlining release tagging and artifact management without altering the existing workflow structures.

Changes

Files	Change Summary
.github/workflows/generate_release_tag.yaml, .github/workflows/test.yaml	Updated action versions: Songmu/tagpr from v1.3.0 to v1.4.0 and actions/upload-artifact from v4.3.5 to v4.3.6.

Poem

In the garden of code, where rabbits play,
Versions hop high, shining bright as the day.
Tagging and artifacts dance hand in hand,
With each little update, a new feature planned.
Hoppy and happy, we cheer with delight,
For changes in workflows make everything right! 🐰✨

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 1212f09 and 3c06e7a.

Files selected for processing (2)

• .github/workflows/generate_release_tag.yaml (1 hunks)
• .github/workflows/test.yaml (1 hunks)

Files skipped from review due to trivial changes (2)

• .github/workflows/generate_release_tag.yaml
• .github/workflows/test.yaml