Skip to content

docs(ses): update news for evalTaming #2764

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

Merged
merged 1 commit into from
Apr 10, 2025
Merged

docs(ses): update news for evalTaming #2764

merged 1 commit into from
Apr 10, 2025

Conversation

leotm
Copy link
Contributor

@leotm leotm commented Apr 9, 2025

Follow-up to: #2723

Add news for evalTaming

@leotm leotm assigned kriskowal and erights and unassigned kriskowal and erights Apr 9, 2025
@leotm leotm requested review from kriskowal and erights April 9, 2025 12:43
@leotm leotm marked this pull request as ready for review April 9, 2025 15:00
Comment on lines +11 to +12
The module name `ses/hermes` can now be required to call `lockdown` and
`repairIntrinsics` only, `Compartment` is not yet available.
Copy link
Contributor Author

@leotm leotm Apr 9, 2025

Choose a reason for hiding this comment

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

Copy link
Contributor

@erights erights left a comment

Choose a reason for hiding this comment

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

LGTM modulo missing single quotes. Thanks!

@@ -2,9 +2,23 @@ User-visible changes in `ses`

# Next release

- The `evalTaming:` option `safe-eval` now can only throw error `SES_DIRECT_EVAL`.
- The [evalTaming](https://github.com/endojs/endo/blob/master/packages/ses/docs/lockdown.md#evaltaming-options)
option `safe-eval` now can only throw error `SES_DIRECT_EVAL`.
This allows SES to initialize with `'unsafe-eval'` or `no-eval` on hosts with no
Copy link
Contributor

Choose a reason for hiding this comment

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

Still missing single quotes around no-eval.

Suggested change
This allows SES to initialize with `'unsafe-eval'` or `no-eval` on hosts with no
This allows SES to initialize with `'unsafe-eval'` or `'no-eval'` on hosts with no

Copy link
Contributor Author

Choose a reason for hiding this comment

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

😅 updated and potentially autofixable with a markdownlint custom rule, noted in

@leotm leotm force-pushed the doc-evalTaming-news branch from 1f36581 to eb3ee92 Compare April 10, 2025 15:27
@leotm leotm enabled auto-merge (rebase) April 10, 2025 15:40
@leotm leotm force-pushed the doc-evalTaming-news branch from eb3ee92 to ba2aa46 Compare April 10, 2025 15:44
@leotm leotm merged commit b9de7e9 into master Apr 10, 2025
15 of 16 checks passed
@leotm leotm deleted the doc-evalTaming-news branch April 10, 2025 15:56
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.

3 participants