Skip to content
This repository has been archived by the owner on Jan 1, 2025. It is now read-only.

Roll back 2.0.0 changes #107

Open
mixmix opened this issue Jul 29, 2024 · 2 comments
Open

Roll back 2.0.0 changes #107

mixmix opened this issue Jul 29, 2024 · 2 comments

Comments

@mixmix
Copy link
Collaborator

mixmix commented Jul 29, 2024

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

@mixmix
Copy link
Collaborator Author

mixmix commented Jul 31, 2024

@elribonazo what do you think?

@elribonazo
Copy link
Collaborator

elribonazo commented Aug 4, 2024

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants