chore(packages): 530 — prepare retirement publish for jarl-react-redux and jarl-react-native - #89
Open
randomdevpete wants to merge 1 commit into
Open
Conversation
randomdevpeteforce-pushed
the
task-530-retire-jarl-react-redux-and-native-packages
branch
2 times, most recently
from
August 19, 2026 13:38
79927e6 to
7e20fe1Comparerandomdevpete
commented
Aug 20, 2026
OwnerAuthor
Change deprecation message to: "Retired: Not in scope for JARL v2." Followed by a package-specific reasoning. Followed by the "see" link. Reasoning: for jarl-react-redux - "JARL v2 is built on Jotai state and fundamentally incompatible with Redux (though you are welcome to build a bridge)." For jarl-react-native - "Was never finished even in v1. Could be reconsidered at a later date." |
…jarl-react-native Both packages' source was already dropped from the monorepo in 72c0ba0; npm still serves their code-bearing 1.0.0-beta.4. Recreate each as a minimal package (package.json + README + LICENSE, no code) explaining the retirement and pointing at jarl-atoms/jarl-react, ready for OWNER to publish and deprecate by hand. Add both to the root workspaces array and regenerate package-lock.json. Neither is added to .releaserc.json's npm plugin list, so semantic-release continues to publish only jarl-atoms and jarl-react. Ticket: 530
randomdevpeteforce-pushed
the
task-530-retire-jarl-react-redux-and-native-packages
branch
from
August 21, 2026 13:12
7e20fe1 to
388d17dComparerandomdevpete
commented
Aug 21, 2026
OwnerAuthor
Done in 388d17d |
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
Prepare minimal packages for official retirement of
jarl-react-reduxandjarl-react-nativeon npm. Both packages had their source removed from the monorepo in 72c0ba0 but continue to exist on npm at1.0.0-beta.4(last modified 2022-05-06) with no deprecation notice.This PR recreates each as a code-free package containing only
package.json,README.mdandLICENSE.md, explains the retirement and links users to the v2 alternatives (jarl-atomsandjarl-react). Both packages are added to the root workspaces andpackage-lock.jsonis regenerated.Version choice: 1.0.1
Both packages publish as
1.0.1rather than continuing the prerelease line at1.0.0-beta.5. Reasoning:1.0.0-beta.5continues the existing prerelease sequence but creates naming confusion:jarl-reactalso published1.0.0-beta.5, so matching that across packages reads as simultaneous releases when they're not.1.0.1marks a clear semantic move: even a code-free publish is a genuine release (a deprecation marker), not a continuation of the experimental prerelease cycle. It sorts after the beta line and before any future v2 prerelease on these packages (unlikely but clearer if it happens).Deprecation fields
Each
package.jsoncarries adeprecatedfield:When published to npm, this surfaces an installation-time warning to any user still installing these packages. The README explains the retirement; the deprecated field makes it visible.
Outstanding for the owner
Merging this PR does not publish anything to npm — that requires explicit manual action. Once the PR merges, run these commands to complete the retirement:
(Optional: if earlier prerelease versions should also be deprecated, run
npm deprecate <package>@<version> <message>for each.)Auto-publish safety verification
Merging this PR will NOT trigger an automatic npm publish. Evidence:
.releaserc.jsonnpm plugin allowlist: The semantic-release config has explicitpkgRootentries for onlypackages/jarl-atomsandpackages/jarl-react. The new deprecated packages are not listed, so they are never touched by semantic-release.CI workflow release job guard: The
releasejob in.github/workflows/ci.ymlruns ONLY when:workflow_dispatch(manual trigger)releaseinput is explicitly tickedIt never runs automatically on a push to master.
Style guide compliance
No exceptions. The READMEs follow area 4 (human-facing docs) rules: clear, concise prose; no padding or marketing fluff; descriptions of current state; links to actual resources. The
package.jsonfiles are minimal with no cruft. British English throughout.LICENSE.mdfiles match the original MIT text frompackages/jarl-react/LICENSE.md.