Rename package artifacts from vast to tenzir #3203
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
tobim
force-pushed
the
topic/tenzir-package
branch
from
a48e2f8 to
f56900b
Compare
|
This now includes the adjustments for the config file paths, but not the The open points from the description are still TODO, but the existing commits can already be reviewed. |
tobim
force-pushed
the
topic/tenzir-package
branch
3 times, most recently
from
a20ea77 to
1fe75f6
Compare
dominiklohmann
approved these changes
Jun 14, 2023
changelog/next/breaking-changes/3203--vast-to-tenzir-migration.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Dominik Lohmann <mail@dominiklohmann.de>
tobim
force-pushed
the
topic/tenzir-package
branch
from
8905b5c to
ccdfbaa
Compare
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.
This change renames user-facing assets from "vast" or a variation thereof to "tenzir".
Automatic migrations of persisted state is implemented on a best-effort basis, meaning that manually created or heavily outdated setups are not supported and require manual intervention.
TODO: