Docs: semver page not working
See original GitHub issueDescribe the bug
The page dedicated to the semver module https://deno.land/std@0.167.0/semver/mod.ts isn’t working on the official STD documentation website.
It shows this error:

It seems like it broke in v0.167.0 (the previous version works fine)
Steps to Reproduce
or
- go to https://deno.land/std@0.167.0?doc
- click on
semver
Expected behavior
The documentation page should be accessible like in version 0.166.0 https://deno.land/std@0.166.0/semver/mod.ts
Issue Analytics
- State:
- Created 9 months ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Applying Semantic Versioning to documentation #609 - GitHub
The problem I see with SemVer in regards to documentation updates is that the specification requires a fully-documented API, but doesn't specify how ......
Read more >Semantic Versioning 2.0.0 | Semantic Versioning
Semantic Versioning 2.0.0. Summary. Given a version number MAJOR.MINOR.PATCH, increment the: MAJOR version when you make incompatible API changes ...
Read more >How to semver versioning documentation update?
It depends on the documentation changes. It's likely that you have a patch level change, provided you didn't suddenly say something like ...
Read more >Using semver — python-semver 2.13.0 documentation
The semver.org page is the authoritative specification of how semantic versioning is defined. ... It's not a special version object like the semver....
Read more >Is it okay to use a patch version in semver when updating ...
Adding or changing public API documentation to a package changes the package content, so you have to make a new version - see...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Thank you @lino-levan for the prompt response and sorry if I opened the issue in the wrong place. To be honest, it wasn’t very clear to me which project controls the API docs since it seems to be mostly auto-generated and the older version worked, so this led me here…
No worries, I think it’s not super well obvious unless you’ve been in the community for a little bit. Thanks for reporting the bug!