feat(cli): publish field types on deploys #322
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
eunjae-lee
approved these changes
Dec 1, 2023
…create-and-update-per-default
demetriusfeijoo
deleted the
EXT-2074-cli-deploy-publish-field-plugin-on-create-and-update-per-default
branch
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.
What?
This PR enhances our CLI deployment process to always publish the field type whenever a new or existing field type is deployed.
Why?
JIRA: EXT-2074
Currently, all the field types deployed using our CLI are being saved but not published.
As we don't see a use case for this scenario, we're changing this behavior to always publish field-types for new deploys or updates.
I did some tests locally after the adjustments and checked how the data was stored and everything worked as expected.