Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automation: main-next integrate #18762

Merged
merged 5 commits into from
Dec 12, 2023
Merged

Automation: main-next integrate #18762

merged 5 commits into from
Dec 12, 2023

Conversation

msfluid-bot
Copy link
Collaborator

main-next integrate PR

DO NOT MERGE THIS PR USING THE GITHUB UI.

The aim of this pull request is to sync main and next branch. If this PR is assigned to you, you need to do the following:

  1. Acknowledge the pull request by adding a comment -- "Actively working on it".
  2. If there are no CI failures, add the "msftbot: merge-next" label to the PR and one of the people with merge permissions will merge it in.
  3. If there are CI failures, check out the main-next-ee948b5 branch and make code changes to fix the failures.
  • You can ignore any failures in the Real service e2e test and Stress test pipelines. These pipelines are not required to pass to merge changes.
  1. Do NOT rebase or squash the main-next-ee948b5 branch: its history must be preserved. Always amend the HEAD commit using the following git commands:
  • git commit --amend -m "Automation: main-next integrate"
  • git push --force-with-lease

Once CI passes and the PR is ready to merge, add the "msftbot: merge-next" label to the PR and one of the people with merge permissions will merge it in.

CraigMacomber and others added 5 commits December 6, 2023 18:19
## Description

Deprecate SchemaBuilder, and related cleanup.
This package now has tests, but the CI pipeline was not specifying them.
This adds the script to the CI pipeline.
The labeling logic is broken, it seems, and we don't rely on the label
today, so removing.
…n minimal release level (#18663)

This PR adds the `minimalReleaseLevel` configuration option, which
allows consumers to specify a release tag to serve as the "minimal"
level of API items to be processed when generating the API docs suite.

E.g. A user could specify `public` to only generate docs for the public
API surface, or they could specify `beta` to include the API surface
containing beta and public members (but not alpha or internal).

The motivation here is to enable hiding `@alpha` API members from the
public (fluidframework.com) documentation, as those APIs are (currently)
designated for pre-approved Microsoft-internal use only. Our internal
API docs site can continue to show alpha docs.

This PR also updates a couple of the end-to-end test configurations to
leverage this new functionality - you can see the resulting changes in
the test snapshots.

AB#6469
@msfluid-bot
Copy link
Collaborator Author

Could not find a usable baseline build with search starting at CI 51f8520

Generated by 🚫 dangerJS against 4582ffc

@sonalideshpandemsft sonalideshpandemsft merged commit 4582ffc into next Dec 12, 2023
37 checks passed
@sonalideshpandemsft sonalideshpandemsft deleted the main-next-ee948b5 branch December 12, 2023 00:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants