React Release Upgrade Strategy
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 140
- Forks
- 100
- Avg merge
- 1h 3m
- Merged PRs (30d)
- 30
Description
Hello
Just a question here.
We've begun using paragon in our apps and we noticed a long lag in supporting React 18, which was released in March 2022, but supported by paragon only quite recently as of Jan 2025, an almost 2 year gap for a sustaining engineering release.
We'd like to standardize using paragon across our apps.
Can you provide guidelines used to assess how paragon decides to upgrade to new React releases?
Thanks!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are identified. The requested outcome is guidance explaining how Paragon evaluates and schedules support for new React releases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react
- Domain
- documentation, release
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100