fix: derive Voltra version from package metadata - #238
Draft
V3RON wants to merge 2 commits into
Draft
Conversation
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
1 participant
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.
What is this?
Dynamic Widget build environments now report the installed Voltra client package version instead of the stale hardcoded
1.4.1value.How does it work?
Node-based generation resolves the platform client package manifest from the app project. Android continues to expose that value through
BuildConfig; iOS writes it to the widget extension'sInfo.plist, where Swift reads it at runtime. Placeholder prerendering and CLI-generated artifacts use the same resolved value.Why is this useful?
Version metadata in widget environments now stays aligned with the Voltra package that actually ships, improving diagnostics and preventing release-time manual synchronization across TypeScript, Swift, and Kotlin.