Feat/clean up type names non breaking #68
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
krhoda
changed the title
Juliano1612
approved these changes
Jun 2, 2023
krhoda
changed the title
…out breaking backwards compatibility
anukritidata
approved these changes
Jun 2, 2023
krhoda
force-pushed
the
feat/clean-up-type-names-non-breaking
branch
from
98ea55a
to
cd44e93
Compare
Deploying with
|
| Latest commit: |
cd44e93
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://bde58b66.rebase.pages.dev |
| Branch Preview URL: | https://feat-clean-up-type-names-non.rebase.pages.dev |
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 handles all the non-breaking changes clean up captured in the pre-publication task lists. All current functionality continues to work across demos, and this PR can be tested by using the CF links below.
rebase-client version
0.12.0includes these changes.Soon, there will be a breaking change that will require all UIs to update at the same time we publish a new worker -- but this is not that update.