-
Notifications
You must be signed in to change notification settings - Fork 15
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
Conversation
WalkthroughThe pull request modifies the GitHub Actions workflow for the Appflow Release Branch. A new parameter, Changes
Possibly related PRs
Suggested labels
Suggested reviewers
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? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this 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
📒 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:
- Verify all your build dependencies work with this new stack
- Test the build process thoroughly
- 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!
build-stack: macOS - 2024.04 | ||
certificate: Fyle signing | ||
environment: staging | ||
native-config: prod |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
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 |
|
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
Bug Fixes
Chores