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.

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

fix: remove deprecated noTame options #328

Merged
merged 1 commit into from
May 28, 2020

Conversation

erights
Copy link
Contributor

@erights erights commented May 27, 2020

Fixes #326

Removes support for old noTame options, which we can't merge until after Agoric/agoric-sdk#1128 is merged.

As described in #326, subsequent calls to lockdown don't need to agree exactly. Only the options provided need to agree exactly. Absence implies agreement with the status quo, whatever that is.

@erights erights requested review from kriskowal and warner May 27, 2020 04:35
@warner
Copy link
Contributor

warner commented May 27, 2020

I don't think this needs to wait for anything from agoric-sdk.. we've got semver, as long as it's marked as a breaking change, whatever version agoric-sdk is using will continue to work the same way as before, and when agoric-sdk upgrades to the new version, the same PR must also make the matching invocation changes.

(incidentally, agoric-sdk trunk is still using the old 0.6.5 SES, so the only branch that uses lockdown() is my swingset-on-new-SES branch, and I'm still working on that. So I'm not worried about compatibility issues)

Copy link
Contributor

@warner warner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good to me

@erights erights merged commit 5d7b781 into master May 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

lockdown noTame options reform
3 participants