fix: adding live update version for sentry release in build script

[Aniruddha-Shriwant]

Clickup

app.clickup.com

Summary by CodeRabbit

• Chores
  • Updated the versioning method for uploading source maps to Sentry, now utilizing the $LIVE_UPDATE_APP_VERSION variable.

[coderabbitai]

Walkthrough

The build_appflow.sh script has been modified to change how the version for uploading source maps to Sentry is determined. The previous method of using sentry-cli releases propose-version has been removed, and now the version is directly taken from the $LIVE_UPDATE_APP_VERSION variable. This adjustment impacts the source of version information during the build process.

Changes

File	Change Summary
build_appflow.sh	Removed sentry-cli releases propose-version assignment; now uses $LIVE_UPDATE_APP_VERSION.

Possibly related PRs

• feat: add mobile app release version in Sentry issues #3249: Updates Sentry configuration to use the mobile app version for tracking issues, related to version sourcing changes.
• fix: LIVE_UPDATE_APP_VERSION for Sentry release instead of FYLE_MOBILE_RELEASE_VERSION #3264: Modifies Sentry release version to use LIVE_UPDATE_APP_VERSION, aligning with the main PR's changes.

Suggested labels

size/XS

Suggested reviewers

• arjunaj5
• Chethan-Fyle

In the script of life, a change we see,
Versioning now flows, like a river so free.
From propose-version to a variable bright,
$LIVE_UPDATE_APP_VERSION shines with delight!
Build it up, let it fly,
Sentry's ready, oh my, oh my! 🌟

---

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

[coderabbitai]

Actionable comments posted: 2

📜 Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

📥 Commits

Reviewing files that changed from the base of the PR and between dc81265 and df5fbfe.

📒 Files selected for processing (1)

• build_appflow.sh (1 hunks)

🔇 Additional comments (1)

build_appflow.sh (1)

3-3: ⚠️ Potential issue

Mind it! Verify the LIVE_UPDATE_APP_VERSION variable, machan!

The script is now fully dependent on $LIVE_UPDATE_APP_VERSION being set correctly. This is a critical change that could affect source map uploads to Sentry if the variable is not properly set.

Let me run a quick check with this script, thalaiva:

I suggest adding this validation at the start of the script:

+if [ -z "$LIVE_UPDATE_APP_VERSION" ]; then
+    echo "Error: LIVE_UPDATE_APP_VERSION is not set!"
+    exit 1
+fi
+
 ionic capacitor sync --prod --source-map

[github-actions]

Unit Test Coverage	%	values
Statements	95.95%	( 19187 / 19996 )
Branches	91.11%	( 10567 / 11597 )
Functions	94.35%	( 5729 / 6072 )
Lines	95.98%	( 18316 / 19082 )