Skip to content

[docs] Add a step to API docs publishing about flipping monikers from 'prelease' to 'live'. #24465

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.

Sign up for GitHub

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

Merged
rolfbjarne merged 2 commits into from
Dec 19, 2025
+7 −3
Merged

[docs] Add a step to API docs publishing about flipping monikers from 'prelease' to 'live'. #24465

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4013555
[docs] Add a step to API docs publishing about flipping monikers from…
rolfbjarne Dec 17, 2025
b50154f
Update docs/update-api-docs.md
rolfbjarne Dec 18, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions docs/update-api-docs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,9 @@ The steps are:

Once this pull request has been merged, an automated publishing job will get any changes in the `main` branch into the `live` branch, which will then show up on https://learn.microsoft.com.

7. The last step is to create a pull request in the [binaries](https://apidrop.visualstudio.com/_git/binaries) repository for the `netX.Y-xcodeZ.W` we created with the new assemblies (into the `master` branch).
7. Create a pull request in the [binaries](https://apidrop.visualstudio.com/_git/binaries) repository for the `netX.Y-xcodeZ.W` we created with the new assemblies (into the `master` branch).

8. The final step is to flip the monikers from prerelease to live monikers (another ticket has to be created for this).

## How to create new monikers

Expand All @@ -67,13 +69,15 @@ So for the initial .NET 10 release, when we shipped APIs for iOS 26.0, tvOS 26.0
We can't create monikers ourselves, we have to request their creation:

1. Go here: [Learn Request Central](https://microsoft.sharepoint.com/teams/Partnerships/SitePages/Learn%20Request%20Central.aspx) (you might have to request access the first time you go here)
a. Under "GitHub Publishing Services" click [Submit your request](https://forms.office.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbRxxUz-ZV53lLrgTaBjGRmtBUNlkzT01CSzNBSE1SRU8yRzU5UTZFNjQyOC4u)
b. Fill in the form with:
1. Under "GitHub Publishing Services" click [Submit your request](https://forms.office.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbRxxUz-ZV53lLrgTaBjGRmtBUNlkzT01CSzNBSE1SRU8yRzU5UTZFNjQyOC4u)
2. Fill in the form with:
1. I am working on publishing a new content set.
2. I need help with updating information architecture (IA) or navigation.
3. Request monikers.
This will lead you to a template to fill an issue. Here's a sample of how I filled it out once: [#480959](https://dev.azure.com/msft-skilling/Content/_workitems/edit/480959).

Note: monikers are typically created as prerelease monikers. Another request has to be created to flip them to live monikers once everything else is in place.

It can be helpful to view info about all monikers here: [All monikers](https://ops.microsoft.com#/monikers)

## References
Expand Down
Loading