Generate Storybook versions from npmjs#401
Merged
Merged
Conversation
|
Tip All tests passed and all changes approved!🟢 UI Tests: web/frontpage: 37 tests unchanged |
|
Tip All tests passed and all changes approved!🟢 UI Tests: web/ui: 11 tests unchanged |
✅ Deploy Preview for storybook-frontpage ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for storybook-addon-catalog ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
github-project-automation
Bot
moved this from In Progress
to Done
in Core Team Projects
8 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fetch Storybook version metadata from npm dist-tags and store it in a generated file. Update the build process to include version generation and add a new script for generating versions. Remove the old way of getting Storybook versions through
/docs/versions/latest|next.jsonin the monorepo.This shouldn't change the output at all, all routes stay the same, only how it is generated changes.
To test:
Compare: