Repository navigation
Remove former branding from docs and installer messages - #29
Merged
Merged
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.
Remove the former product name from README, changelog, migration instructions, source comments, and installer messages. Rename the native migration entry point to
deploy/native/migrate-legacy.shand update its documented invocation.Preserve the exact identifiers that pre-4.1 installs require: legacy data paths, environment variables, service registrations, discovery values, update headers, and compatibility release assets. Removing those would break upgrades or communication with existing installations. Runtime Rust logic and release packaging commands are unchanged.
Validation:
cargo test --workspace(246 passed, 13 ignored),cargo clippy --workspace --all-targets -- -D warnings,cargo fmt --all -- --check, Bash syntax checks for the affected scripts, and a documentation/link scan. The existing launch-rollback timing test failed once, passed in isolation, and passed on the full rerun. Windows/Linux execution remains covered by CI.