Skip to content

bump build number to 67 - #459

Merged
abdulsaheel merged 1 commit into
mainfrom
release/v0.10.0-build67
Sep 25, 2026
Merged

abdulsaheel merged 1 commit into
mainfrom
release/v0.10.0-build67

Conversation

@abdulsaheel

@abdulsaheel abdulsaheel commented Sep 25, 2026 •

Copy link
Copy Markdown
Collaborator

User description

follow-up to v0.10.0 — TestFlight build 66 was cut before #451 (analytics repin, kAlgoVersion 96->97) merged. this bumps the build number so the fresh upload includes it. no version/feature change.

Summary by Sourcery

Build:

  • Increment the iOS build number from 66 to 67 while keeping the 0.10.0 version unchanged.

PR Type

Other


Description

  • Bumps iOS build number from 66 to 67 across all targets

  • CURRENT_PROJECT_VERSION updated in Runner, RunnerTests, widget, and watch targets

  • pubspec.yaml version updated from 0.10.0+66 to 0.10.0+67


Diagram Walkthrough

flowchart LR
  A["pubspec.yaml\nversion: 0.10.0+66"] -- "bump build" --> B["pubspec.yaml\nversion: 0.10.0+67"]
  C["project.pbxproj\nCURRENT_PROJECT_VERSION = 66\n(all targets)"] -- "bump build" --> D["project.pbxproj\nCURRENT_PROJECT_VERSION = 67\n(all targets)"]
Loading

File Walkthrough

Relevant files
Configuration changes
pubspec.yaml
Bump app version build number to 67                                           

pubspec.yaml

  • Version string updated from 0.10.0+66 to 0.10.0+67
+1/-1     
project.pbxproj
Increment CURRENT_PROJECT_VERSION to 67 for all targets   

ios/Runner.xcodeproj/project.pbxproj

  • CURRENT_PROJECT_VERSION incremented from 66 to 67 in all nine build
    configurations
  • Covers Runner (Debug/Release/Profile), RunnerTests
    (Debug/Release/Profile), widget extension (Debug/Release/Profile), and
    watch app (Debug/Release/Profile)
  • MARKETING_VERSION remains 0.10.0 unchanged
+9/-9     

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Sorry @abdulsaheel, you've used your own review budget of 250,000 diff characters for the last 7 days.

You can request another review in 1 hour and 10 minutes by commenting @sourcery-ai review. Upgrade to get a review now.

@sourcery-ai

sourcery-ai Bot commented Sep 25, 2026

Copy link
Copy Markdown
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Bumps the iOS/Flutter build from 66 to 67 for a fresh TestFlight upload that includes previously merged changes, with no feature or marketing-version change.

File-Level Changes

Change Details Files
Increment the Flutter build number for the next TestFlight upload while preserving the existing app version.
  • Change the package version from 0.10.0+66 to 0.10.0+67.
  • Update corresponding iOS project build-number settings for the Runner and related targets.
pubspec.yaml
ios/Runner.xcodeproj/project.pbxproj

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@coderabbitai

coderabbitai Bot commented Sep 25, 2026 •

Copy link
Copy Markdown
Contributor

Review in Change Stack →

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository: OpenStrap/edge/.coderabbit.yaml

Review profile: ASSERTIVE

Plan: Advanced

Run ID: 3a4d5a73-7b1b-4974-9611-21782bb902a3

📥 Commits

Reviewing files that changed from the base of the PR and between 71b7761 and 6facc93.

⛔ Files ignored due to path filters (1)
  • ios/Runner.xcodeproj/project.pbxproj is excluded by !ios/**
📒 Files selected for processing (1)
  • pubspec.yaml

Included review availability: Your plan provides up to 4 included reviews per hour; 3 remain after this review.


📝 Walkthrough

Walkthrough

The package version changed from 0.10.0+66 to 0.10.0+67.

Changes

Package version

Layer / File(s) Summary
Update package version
pubspec.yaml
The package version changes from 0.10.0+66 to 0.10.0+67.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~2 minutes

Change: Other

Suggested reviewers: droptabl

Merge Risk: ⚪ Minimal · up to 6facc

The build-number bump appears ready to merge after normal release checks. The supplied evidence does not establish a problem with the analytics pin.

Architecture Summary

Architecture risk: 🔵 Low · up to 6facc

The change affects 1 system.

Changed systems: pubspec.yaml

Architecture concerns
No architecture-level concerns identified.

Review details

Systems and components

  • observed — pubspec.yaml (service) was modified; 1 changed file maps to changed impact.

Before / after behavior

  • observed — Modified behavior in pubspec.yaml: The package version changed from 0.10.0+66 to 0.10.0+67.
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely describes the main change: increasing the package build number from 66 to 67.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@github-actions

Copy link
Copy Markdown
Contributor

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪
🧪 No relevant tests
🔒 No security concerns identified
⚡ No major issues detected

@github-actions

Copy link
Copy Markdown
Contributor

PR Code Suggestions ✨

No code suggestions found for the PR.

@abdulsaheel
abdulsaheel merged commit 74ed359 into main Sep 25, 2026
4 checks passed
@abdulsaheel
abdulsaheel deleted the release/v0.10.0-build67 branch September 25, 2026 12:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant