Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Switch to macOS 2024.04 for prod internal release #3273

Merged
merged 1 commit into from
Nov 20, 2024

Conversation

arjunaj5
Copy link
Contributor

@arjunaj5 arjunaj5 commented Nov 20, 2024

Clickup

https://app.clickup.com

Code Coverage

Please add code coverage here

UI Preview

Please add screenshots for UI changes

Summary by CodeRabbit

  • New Features

    • Updated iOS build environment to macOS - 2024.04 for improved compatibility.
    • Set iOS build type to development for enhanced testing capabilities.
  • Bug Fixes

    • Adjusted native configuration to production for more stable releases.
  • Chores

    • Maintained existing workflow structure for building and deploying Android and iOS applications.

Copy link

coderabbitai bot commented Nov 20, 2024

Walkthrough

The pull request modifies the GitHub Actions workflow for the Appflow Release Branch. A new parameter, build-stack: macOS - 2024.04, is added to the iOS build step, specifying the build environment. The iOS build type is set to development, and the native configuration is updated to prod. The overall structure of the workflow remains intact, including steps for building Android and iOS applications, managing artifacts, and sending Slack notifications.

Changes

File Change Summary
.github/workflows/appflow-release-branch.yml Added build-stack: macOS - 2024.04 to iOS build step; set iOS build type to development and native configuration to prod.

Possibly related PRs

Suggested labels

size/XS

Suggested reviewers

  • Chethan-Fyle
  • suyashpatil78

🎉 In the workflow of code, changes flow like a stream,
With build-stack added, we chase the dream.
iOS builds now shine, with development in sight,
Native config in prod, ready to take flight!
Notifications on Slack, we celebrate the day,
With Rajinikanth's style, let's code away! 🌟


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
🪧 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 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 github-actions bot added the size/XS Extra Small PR label Nov 20, 2024
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

📥 Commits

Reviewing files that changed from the base of the PR and between 1bc2061 and 65f0fc6.

📒 Files selected for processing (1)
  • .github/workflows/appflow-release-branch.yml (1 hunks)
🔇 Additional comments (2)
.github/workflows/appflow-release-branch.yml (2)

Line range hint 14-17: Verify the build type configuration, maccha!

Listen here, partner! I notice you're using different build types:

  • Android: debug
  • iOS: development

Make sure this difference is intentional and won't cause any problems in production. Sometimes, what looks like a small difference can turn into a big headache later!

Also applies to: 44-46


46-46: Kabali da! Verify the new macOS stack compatibility!

The new macOS 2024.04 stack is like a fresh superstar entering the industry! Before we roll this out to production:

  1. Verify all your build dependencies work with this new stack
  2. Test the build process thoroughly
  3. Check if there are any known issues with this stack version

Remember what I always say: "When I do something, I do it style!" Let's make sure this upgrade is stylish and smooth!

Comment on lines +46 to 49
build-stack: macOS - 2024.04
certificate: Fyle signing
environment: staging
native-config: prod
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Mind it! Environment configuration mismatch detected!

Hey boss! Your iOS build is mixing staging environment with prod native-config, while Android keeps it all staging. This kind of mismatch situation is like wearing formal shoes with beach shorts - it just doesn't match!

  environment: staging
- native-config: prod
+ native-config: staging

Let's maintain consistency across platforms, what do you say?

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
build-stack: macOS - 2024.04
certificate: Fyle signing
environment: staging
native-config: prod
build-stack: macOS - 2024.04
certificate: Fyle signing
environment: staging
native-config: staging

Copy link

Unit Test Coverage % values
Statements 95.95% ( 19188 / 19996 )
Branches 91.11% ( 10567 / 11597 )
Functions 94.36% ( 5730 / 6072 )
Lines 95.99% ( 18317 / 19082 )

@arjunaj5 arjunaj5 merged commit faa306b into master Nov 20, 2024
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
size/XS Extra Small PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants