Repository navigation
docs: point the readme links at main and name the 1.0 packages in the migration skill - #362
Merged
Merged
Conversation
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
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.
After 1.0,
mainis the only branch, andnextwill be deleted. npm keeps the README of each version, so the 1.0.0 READMEs must not link tonext.demo.gifURLs in the READMEs now point atmain.migrating-from-v4skill names@awesome-reveal/react1.0 andreact-awesome-reveal5, not "v5 of@awesome-reveal/react". The two copies stay the same.Merge this PR before release PR #360. Until
mainis reset tonext,mainhas nodemo.gif, so the image does not show for some minutes after the publish.Test plan
pnpm test:packagepasses: 8 test files, 50 tests, publint and attw.pnpm format:checkpasses.next.