Change Android and iOS Publish action triggers

[daniellfalcao]

Summary by CodeRabbit

• New Features

  • Enhanced control over the Android and iOS release workflows by triggering publishing actions only when releases are finalized and made public.
  • Streamlined release process by automating the generation of release notes from commit messages.

• Bug Fixes

  • Improved reliability and timing of deployment processes for both Android and iOS releases.

• Chores

  • Updated version number in the project configuration to reflect minor improvements.

[coderabbitai]

Walkthrough

The changes involve updates to the GitHub Actions workflow configuration for both Android and iOS publishing. The event type that triggers these workflows has been modified from created to published under the release event. Additionally, the Cargo.toml file has been updated to reflect a minor version increment from 0.1.0 to 0.1.1. A step for capturing release notes has also been removed in favor of automatic generation.

Changes

Files	Change Summary
.github/workflows/publish-android.yaml, .github/workflows/publish-ios.yaml	Changed event type from created to published under the release event.
Cargo.toml	Incremented version number from 0.1.0 to 0.1.1.
.github/workflows/pull-master-release.yaml	Removed step for capturing release notes; now uses --generate-notes option.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant GitHub
    participant Workflow

    User->>GitHub: Create Release
    GitHub-->>User: Release Created
    User->>GitHub: Publish Release
    GitHub-->>Workflow: Trigger Workflow
    Workflow-->>User: Execute Publishing Actions

Loading

Poem

🐰 In the meadow, a change so bright,
Releases now dance in the soft moonlight.
From "created" to "published," they leap and play,
A joyful hop in the workflow's ballet!
With each new release, the bunnies cheer,
For smoother journeys, the time is near! 🌼✨

---

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 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.

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 3d20cd9 and b84b2f8.

Files selected for processing (2)

• .github/workflows/publish-android.yaml (1 hunks)
• .github/workflows/publish-ios.yaml (1 hunks)

Additional comments not posted (2)

.github/workflows/publish-android.yaml (1)

4-4: LGTM!

The change from created to published ensures that the workflow will only execute when a release is officially published, which aligns with the objective of improving the control flow and reliability of the deployment process.

.github/workflows/publish-ios.yaml (1)

4-4: LGTM!

The change from created to published ensures that the workflow will only execute when a release is officially published, which aligns with the objective of improving the control flow and reliability of the deployment process.

[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 b84b2f8 and b19357d.

Files ignored due to path filters (1)

• Cargo.lock is excluded by !**/*.lock

Files selected for processing (1)

• Cargo.toml (1 hunks)

Files skipped from review due to trivial changes (1)

• Cargo.toml

[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 b19357d and 04db600.

Files selected for processing (1)

• .github/workflows/pull-master-release.yaml (1 hunks)

Additional comments not posted (1)

.github/workflows/pull-master-release.yaml (1)

81-81: LGTM!

The changes simplify the release process by automatically generating release notes and ensure the correct context by explicitly setting the target branch to master.