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

drop jsvm (aka enclave) #183

Merged
merged 3 commits into from
Aug 22, 2022
Merged

drop jsvm (aka enclave) #183

merged 3 commits into from
Aug 22, 2022

Conversation

ailisp
Copy link
Member

@ailisp ailisp commented Aug 19, 2022

@thisisjoshford @BenKurrek From what we discussed in retro, please help make an announcement in blog / doc and maybe mention:

  • Enclave, if there's a lot community interest, will be continue as a separate project
  • There's an archived enclave, at jsvm branch, but note that it's feature behind standalone and not actively maintained

@ailisp ailisp requested a review from volovyks August 19, 2022 02:08
@volovyks
Copy link
Collaborator

volovyks commented Aug 22, 2022 •
edited
Loading

@ailisp I have:

  • deleted all JSVM-related APIs and logic.
  • deleted all mentions of "standalone name". I think we should not use it from now on. It is just NEAR JS SDK.

@volovyks volovyks merged commit bb02965 into develop Aug 22, 2022
@ailisp ailisp deleted the drop-jsvm branch August 23, 2022 01:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@volovyks volovyks volovyks approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@ailisp @volovyks