Release workflowのTriggerを変更

[Shion1305]

• dependabotによる依存性の更新が入ったため、更新後のバージョンを反映しようとした。
• Tokiwa23ではreleaseのworkflowとして、 release ブランチにpushされるタイミングに設定されていた
• tokiwa24 と同じく release されたタイミングで反映されるようにしたい

Summary by CodeRabbit

• New Features
  • Deployment process now triggers on official GitHub release events, enhancing reliability and predictability.
• Improvements
  • Streamlined deployment strategy focusing on versioned releases instead of branch-based deployments.

[coderabbitai]

Walkthrough

The pull request modifies the deployment workflow for Cloud Run by changing the trigger mechanism from a push event on the release branch to a release event that specifically listens for released types. This adjustment ensures that deployments are initiated only when a release is officially published, promoting a more versioned and controlled deployment process.

Changes

File	Change Summary
.github/workflows/deploy-cloudrun-release.yaml	Trigger event changed from push on branch release to release of type released.

Poem

In the meadow, we hop with glee,
A new release, oh what a spree!
No more pushes, just a grand cheer,
For every release, we hold dear.
With Docker and Cloud Run in sight,
Our deployments now feel just right! 🐇✨

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 5607f87 and 3373182.

Files selected for processing (1)

• .github/workflows/deploy-cloudrun-release.yaml (1 hunks)

Additional comments not posted (1)

.github/workflows/deploy-cloudrun-release.yaml (1)

3-5: LGTM! The new deployment strategy aligns better with versioned releases.

The changes to the trigger event streamline the deployment process by focusing on release events. This enhances the reliability and predictability of deployments to Cloud Run.

The new deployment process is more controlled, ensuring that deployments occur only when a release is officially published. This is a better approach compared to branch-based deployments.

---

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>, 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 generate interesting stats about this repository and render them as a table.
  -- @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 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.

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.

[github-actions]

Deployed on https://tokiwa23-stg-pr-125-54hsiiq5ra-an.a.run.app

[Shion1305]

@hayato19 Please Review

[hayato19]

LGTM!