starred/markdig
1
0
Fork 0
mirror of https://github.com/xoofx/markdig.git synced 2026-02-03 21:36:36 +00:00
Code Issues 690 Packages Projects Releases 20 Wiki Activity

Package ID Prefix Issue #492

New Issue
Closed
opened 2026-01-29 14:38:03 +00:00 by claunia · 2 comments
claunia commented 2026-01-29 14:38:03 +00:00
Owner
Copy Link

Originally created by @wbaldoumas on GitHub (Jan 12, 2022).

I am currently working on a small Markdig extension that adds markdown syntax highlighting by leveraging ColorCode-Universal, which is an updated version of ColorCode.

Unfortunately, I am running into an issue when trying to publish the library as a NuGet package:

error: Response status code does not indicate success: 409 (This package ID has been reserved. Please request access to upload to this reserved namespace from the owner of the reserved prefix, or re-upload the package with a different ID. Go to https://docs.microsoft.com/en-us/nuget/reference/id-prefix-reservation learn more about Package ID prefix reservation.).

I believe the issue is that "Markdig" is a reserved package ID prefix. Removing "Markdig" from the extension name will obscure its purpose from potential users of the library. Is there a path forward to being unblocked and publishing this extension as Markdig.ColorCode?

Originally created by @wbaldoumas on GitHub (Jan 12, 2022). I am currently working on [a small Markdig extension](https://github.com/wbaldoumas/markdig-colorcode) that adds markdown syntax highlighting by leveraging [ColorCode-Universal](https://github.com/CommunityToolkit/ColorCode-Universal), which is an updated version of [ColorCode](https://ripcode.net/p/colorcode). Unfortunately, I am running into an issue when trying to publish the library as a NuGet package: ``` error: Response status code does not indicate success: 409 (This package ID has been reserved. Please request access to upload to this reserved namespace from the owner of the reserved prefix, or re-upload the package with a different ID. Go to https://docs.microsoft.com/en-us/nuget/reference/id-prefix-reservation learn more about Package ID prefix reservation.). ``` I believe the issue is that "Markdig" is a reserved package ID prefix. Removing "Markdig" from the extension name will obscure its purpose from potential users of the library. Is there a path forward to being unblocked and publishing this extension as `Markdig.ColorCode`?
claunia added the question label 2026-01-29 14:38:03 +00:00
claunia commented 2026-01-29 14:38:03 +00:00
Author
Owner
Copy Link

@xoofx commented on GitHub (Jan 13, 2022):

Is there a path forward to being unblocked and publishing this extension as Markdig.ColorCode?

No there is no path apart prefixing your package with your own name as everybody else is doing. There is one exception for Markdig.Wpf, but this package existed before the Markdig prefix was locked. Having a package like Markdig.ColorCode or any other packages would be very confusing as folks might think that it comes from this repo or it is supported in similar way.

@xoofx commented on GitHub (Jan 13, 2022): > Is there a path forward to being unblocked and publishing this extension as Markdig.ColorCode? No there is no path apart prefixing your package with your own name as [everybody else](https://www.nuget.org/packages?q=markdig) is doing. There is one exception for `Markdig.Wpf`, but this package existed before the Markdig prefix was locked. Having a package like `Markdig.ColorCode` or any other packages would be very confusing as folks might think that it comes from this repo or it is supported in similar way.
claunia commented 2026-01-29 14:38:04 +00:00
Author
Owner
Copy Link

@wbaldoumas commented on GitHub (Jan 13, 2022):

Hey, thanks for your response and clarification. I'll find another package name that works and is still clear about what it does. I'll also be sure to adjust my repository name to match. 😄

@wbaldoumas commented on GitHub (Jan 13, 2022): Hey, thanks for your response and clarification. I'll find another package name that works and is still clear about what it does. I'll also be sure to adjust my repository name to match. 😄
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
enhancement
extension
Hacktoberfest
invalid
PR Welcome!
pull-request
Mirrored from GitHub Pull Request
 question
wontfix
No Label question
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/markdig#492
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?