Bump terser from 4.8.0 to 4.8.1
Bumps terser from 4.8.0 to 4.8.1.
Changelog
Sourced from terser's changelog.
v4.8.1 (backport)
- Security fix for RegExps that should not be evaluated (regexp DDOS)
Commits
- See full diff in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebasewill rebase this PR -
@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it -
@dependabot mergewill merge this PR after your CI passes on it -
@dependabot squash and mergewill squash and merge this PR after your CI passes on it -
@dependabot cancel mergewill cancel a previously requested merge and block automerging -
@dependabot reopenwill reopen this PR if it is closed -
@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the Security Alerts page.
Please note that this will break code like this because calls to clone and to_owned will no longer be dereferenced:
#[derive(Debug, Model)]
struct A {
id: Uuid,
#[ormlite(join_column = "b")]
b: Join<B>
}
#[derive(Clone, Debug, Model)]
struct B {
id: Uuid,
}
fn hi(a: A) {
// no longer works
let x: B = a.b.to_owned();
// now works
let y: Join<B> = a.b.to_owned();
// still works
let z: B = (*a.b).to_owned();
}
Can you provide a rationale and example code for why you'd want to Clone a Join struct? My mental model is that it's owned by the queried object, and never lives elsewhere. Definitely happy to include it if it makes sense, just concerned it might also lead to mistakes where users think they're updating the values, but it was only the clone that was updated.