Repository navigation
docs(readme): drop the notes about Claude Motion availability - #40
Merged
Merged
Conversation
…t motion-render does not need it
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.
Summary
From 1.0.0 motion-render does not need Claude Motion, but the READMEs still carried notes written when it did. This removes them, in English and Japanese.
Kept on purpose: "Two ways to make the animation" and the Troubleshooting row about Motion pages using OS fonts. Both describe what happens when Motion is used, which is still the case on Team and Enterprise.
The
v1.0.0tag and its draft release were deleted. They are recreated on the merge commit of this PR.Test plan
npx prettier --check README.md README.ja.md