Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

JS Client beta release process #242

Open
CedarMist opened this issue Dec 11, 2023 · 0 comments
Open

JS Client beta release process #242

CedarMist opened this issue Dec 11, 2023 · 0 comments
Assignees
@CedarMist
Labels
client js Pull requests that update JS code p:1 Priority: high s:planned Status: work on this issue is scheduled

Comments

@CedarMist
Copy link
Member

Making new releases of the JS client can be nerve wracking as it is most used at the moment.

I'm proposing the following:

  • create -beta releases, or a sapphire-paratime-beta NPMJS package
    • Whichever one will be unlikely to auto-upgrade when people 1.x in the package.json
  • Release checklist
    • Upgrade demo & dapp repos to the -beta release and test them
      • Also upgrade other packages to their most recent versions
    • Test the dapps with the most common browser based web3 wallets
      • Rabby
      • MetaMask
      • MetaMask mobile
      • Brave

This will serve as a canary release, and provide good UX feedback .
@CedarMist CedarMist added p:1 Priority: high s:planned Status: work on this issue is scheduled js Pull requests that update JS code client labels Dec 11, 2023
@CedarMist CedarMist self-assigned this Dec 11, 2023
@aefhm aefhm mentioned this issue Dec 19, 2023
Merged
10 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@CedarMist CedarMist

Labels
client js Pull requests that update JS code p:1 Priority: high s:planned Status: work on this issue is scheduled
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@CedarMist