fix: refresh generated app dependency baseline - #288
Merged
Conversation
artiphishle
force-pushed
the
fix/generated-package-baseline
branch
from
August 16, 2026 18:31
d8e0684 to
c86c21f
Compare
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.
Summary
Refresh the dependency baseline written into generated app
package.jsonfiles.Changes
@ankhorage/contracts->^7.9.0@ankhorage/expo-runtime->^2.5.1@ankhorage/runtime->^1.1.0@ankhorage/studio->^1.12.5@ankhorage/supabase-auth->^1.2.1@ankhorage/supabase-storage->^0.2.0@ankhorage/zora->^2.13.2@ankhorage/devtools->^1.4.1latestdependencies with explicit compatible ranges~54.0.36~29.0.19~5.9.3^5.0.2latestdependenciesWhy
Project sync already rewrites generated app package manifests from this central Studio template. Keeping stale or floating dependency ranges here means existing apps stay outdated even after their Studio host is upgraded, and new apps can resolve inconsistent package versions.
After merge/release, project sync can update generated app manifests to this baseline; dependency installation remains a separate step.