Feat!: Keep track of the previous finalized snapshots in the environment#2130
Merged
izeigerman merged 1 commit intomainfrom Feb 16, 2024
Merged
Feat!: Keep track of the previous finalized snapshots in the environment#2130izeigerman merged 1 commit intomainfrom
izeigerman merged 1 commit intomainfrom
Conversation
izeigerman
force-pushed
the
feat-previous-promoted-snapshots
branch
from
783f623 to
0902af3
Compare
izeigerman
changed the title
izeigerman
force-pushed
the
feat-previous-promoted-snapshots
branch
from
0902af3 to
739c18f
Compare
tobymao
approved these changes
Feb 16, 2024
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
2 participants
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.
Sometimes, when the main branch is ahead of production and changes are being deployed to production, other users iterating in their development environments might end up comparing their local state against a partial / unfinilized production state.
This may result in unnecessary evaluations, leading to a worse developer experience, even if comparing against the most recent state of production is technically more correct.
This update introduces an option to compare against the latest finalized state of the target environment and ignore the partial state.