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

chore(core): auto-update vendored lockdown.umd.js #1078

Closed
wants to merge 1 commit into from
Closed

chore(core): auto-update vendored lockdown.umd.js #1078

wants to merge 1 commit into from

Commits on Mar 6, 2024

  1. chore(core): auto-update vendored lockdown.umd.js 

    This changes the `lint-staged` configuration so that when `package-lock.json` is updated, the vendored `packages/core/lib/lockdown.umd.js` is copied from the currently-installed `ses` and added to the commit.

I'm not sure if this is something we want to be doing or not, but needing to run the `lib:ses` script in `lavamoat-core` after a `ses` upgrade is non-obvious for maintainers (me).
    @boneskull
    boneskull committed Mar 6, 2024
    Copy the full SHA
    b3a5397 View commit details
    Browse the repository at this point in the history