Update Releases documentation with Scheduling #2025
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 ↗︎
|
pwizla
added
source: User Guide
yanniskadiri
requested changes
Feb 22, 2024
pwizla
commented
Feb 22, 2024
pwizla
added
the
temp: port to v5
yanniskadiri
approved these changes
Feb 22, 2024
pwizla
removed
the
temp: port to v5
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 PR updates the User Guide for Releases Scheduling (Releases section + Content Manager) + the Dev Docs since we now again have a usable future flag and a new webhook.
Direct preview links for all impacted pages:
👉 Releases introduction
👉 Creating a release
👉 New "Scheduling a release" section in "Managing a release" page
👉 Small mention in the "Adding content to a release" page (Content Manager section)
👉 Future flags page in the Dev Docs
👉 New section in the Webhooks page (Dev Docs)