-
Notifications
You must be signed in to change notification settings - Fork 519
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update RELEASE.toml for next release #687
Merged
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
tjkirch
force-pushed
the
region-migration
branch
from
January 28, 2020 23:18
6679e53
to
d14f6a0
Compare
tjkirch
force-pushed
the
release.toml-migrations
branch
from
January 28, 2020 23:18
6adfb6a
to
b3ca093
Compare
This push just rebases on a typo fix from #636. |
tjkirch
force-pushed
the
region-migration
branch
from
January 29, 2020 18:18
d14f6a0
to
6b61f65
Compare
tjkirch
force-pushed
the
release.toml-migrations
branch
from
January 29, 2020 18:18
b3ca093
to
2da145a
Compare
This push is just a rebase onto changes from #637. |
zmrow
approved these changes
Jan 29, 2020
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤙
tjkirch
force-pushed
the
region-migration
branch
from
January 31, 2020 23:07
6b61f65
to
ae03e5d
Compare
tjkirch
force-pushed
the
release.toml-migrations
branch
from
January 31, 2020 23:07
2da145a
to
51df5ae
Compare
This push was just a rebase onto changes from #644. |
tjkirch
force-pushed
the
region-migration
branch
from
February 1, 2020 00:09
ae03e5d
to
bd015f4
Compare
tjkirch
force-pushed
the
release.toml-migrations
branch
from
February 1, 2020 00:09
51df5ae
to
1f3e45a
Compare
This push was just a rebase onto changes from #644. |
tjkirch
force-pushed
the
region-migration
branch
from
February 1, 2020 00:28
bd015f4
to
6851fa7
Compare
This adds the remove-region migration needed to downgrade after adding platform-specific settings. This updates the migration syntax to match manifest.json from the TUF repo, both for simplicity of updating the manifest and because we have a lot of information and the increased density makes it easier for humans to see the various migration paths.
tjkirch
force-pushed
the
release.toml-migrations
branch
from
February 1, 2020 00:32
1f3e45a
to
230f784
Compare
Just a rebase on develop, no changes. |
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 adds the remove-region migration needed to downgrade after adding
platform-specific settings.
This updates the migration syntax to match manifest.json from the TUF repo,
both for simplicity of updating the manifest and because we have a lot of
information and the increased density makes it easier for humans to see the
various migration paths.
We don't use this migration list yet, but it took me a bit to figure out the correct paths, so I wanted it represented here - either a tool will start to use it, or a human can copy/paste it into our next manifest.json.
I think our future process could be to add migrations to this file in the same PR that creates the migration.