feat: remove site_capabilities from the deploy object #526
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
This was used just for large media and we're deprecating it. We'll be removing this slowly and this is a good first step and allows us to return a smaller object for deploys. Updated the porcelain handler to not rely on this field but only on the option passed on DoDeploy. This way we allow for builds to still use it if needed until fully retired.
✅ Deploy Preview for open-api ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
paulo
approved these changes
Jan 22, 2024
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 was used just for large media and we're deprecating it. We'll be removing this slowly and this is a good first step and allows us to return a smaller object for deploys.
Updated the porcelain handler to not rely on this field but only on the option passed on DoDeploy. This way we allow for builds to still use it if needed until fully retired (see buildbot PR linked below)