-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Broken link causes 404 error #32194
Comments
This is probably because the readme is from a version of package that was published long time ago. Now we linked to https://github.com/nodejs/release#release-schedule Is it possible to fix the doc site after it is published? |
@jeremymeng I'm not the content owner, but I created this issue because the broken link was included in a report. It's published content that customers use, so my opinion is the content owner should fix the broken link. |
@davidsmatlak Yeah definitely! Thanks for reporting! My question was for docs owner. |
this broken link should be fixed in f280f87 2 years ago, but we have never released this rp with a stable version. |
I have sent an email to the service team to have further discussion on this. I also cced you @jeremymeng @davidsmatlak |
We have released a stable version for this rp here: https://www.npmjs.com/package/@azure/arm-policyinsights/v/6.0.0 |
Type of issue
Typo
Description
Broken link in section Currently supported environments for LTS versions of Node.js causes a 404 error that Page could not be found.
Link on the Node.js website for Node.js Releases is
https://nodejs.org/en/about/previous-releases
and noticed without theen
this link will 404.Page URL
https://learn.microsoft.com/en-us/javascript/api/overview/azure/arm-policyinsights-readme?view=azure-node-latest
Content source URL
https://github.com/MicrosoftDocs/azure-docs-sdk-node/blob/main/docs-ref-services/latest/arm-policyinsights-readme.md
Document Version Independent Id
72d4a6fe-0e26-3f2d-bdc3-6d0fa204be4d
Article author
@azure-sdk
Metadata
The text was updated successfully, but these errors were encountered: