Skip to content

Commit a34bf0f

Browse files
committed
Removing old in preview messages
1 parent 6c94ac6 commit a34bf0f

File tree

2 files changed

+1
-4
lines changed

2 files changed

+1
-4
lines changed

docs/features/hub-site/REST-unregisterhubsite-method.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,9 +7,6 @@ ms.localizationpriority: medium
77

88
# UnRegisterHubSite
99

10-
> [!IMPORTANT]
11-
> The hub sites feature is currently in preview and is subject to change. It is not currently supported for use in production environments.
12-
1310
Unregisters a hub site so that it is no longer a hub site. It will become a regular site. Any sites associated with the hub site will no longer be associated. This can take up to an hour to propagate. If you want to speed up the process, first remove any associated sites before unregistering the hub site.
1411

1512
## HTTP request

docs/spfx/toolchain/implement-ci-cd-with-azure-devops.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ This article explains the steps involved in setting up your Azure DevOps environ
1616

1717
There are currently two approaches available to implement continuous integration, and deployment in Azure DevOps.
1818
Azure builds and releases is the historic one, featuring a graphical edition experience and storing the definitions in a JSON document hidden from the user.
19-
Azure multi-stage Pipelines is a newer feature still in preview, is relies on pipeline definitions stored as YAML files on the repository providing transparency, version history and repeatability.
19+
2020
Both approaches are described for the SharePoint Framework:
2121

2222
- Azure Build and Release (this article)

0 commit comments

Comments
 (0)