You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 1, 2025. It is now read-only.
Problem: we're wanting to make clear documentation etc for pluto-encrypted. Currently we have all these 2.0.0 modules published which are a distraction for new users because:
they are the first thing you see when you go to this repo
they don't work with the current SDK
from what I understand you aren't that keen on the "upgrade RXDB" path anyway
Proposal
wind the HEAD back to before these releases
move the 2.0.0 work into a branch called "rxdb_upgrade"
remove the 2.0.0 tags
unpublish 2.0.0 packages from npm
The goal of all this is to make it real hard for people to accidentally install broken software setup / be reading the wrong docs
The text was updated successfully, but these errors were encountered:
Uff, we cannot unpublish the npm packages if they are already used in other published packages and some automatiions fuck this up, let me see.
There's literally no way. I would propose to jump to 3x + try to bring something in at least some improvement. Its not ideal but we won't have this problem.
We can also improve docs and make a statement around that. If we release newer packages to 1.X which we ofc can continue doing i'm not fully sure if npm will continue showing the last version is 2x.
But yeah, either jump to 3X or stay but clarify this in the NPM package readme + git readme
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Problem: we're wanting to make clear documentation etc for pluto-encrypted. Currently we have all these 2.0.0 modules published which are a distraction for new users because:
Proposal
HEAD
back to before these releasesThe goal of all this is to make it real hard for people to accidentally install broken software setup / be reading the wrong docs
The text was updated successfully, but these errors were encountered: