This repository has been archived by the owner on Mar 24, 2023. It is now read-only.
Stop pinning ship-init to specific version #691
Merged
Conversation
This file contains 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 I Did
Reverted web/app Makefile, package.json, yarn.lock changes, which were modified in attempting to fix standalone/Homebrew build issues by pinning a specific ship-init version.
How I Did it
How to verify it
Check that appropriate UI resources are included in local & circleci builds.
Description for the Changelog
Restore embedded ship-init component to use latest code, rather than pinning to explicit version
Picture of a Boat (not required but encouraged)