Fix bundle not found on 1.0.2#8
Merged
michaelversus merged 1 commit intomichaelversus:masterfrom Jan 29, 2026
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #8 +/- ##
==========================================
+ Coverage 93.59% 93.78% +0.18%
==========================================
Files 33 33
Lines 2060 2589 +529
==========================================
+ Hits 1928 2428 +500
- Misses 132 161 +29 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Currently downloaded version 1.0.2 from brew is crashing due to bundle not found.
This PR solves this issue by introducing a new Version.swift that is considered in the Release pipeline and goes in sync with VERSION file.
Apologies for the disruption , maybe in future we can add some e2e snapshot tests for cases like that.