Bump eslint-import-resolver-typescript from 2.7.1 to 3.6.3 in /frontends/admin-panel#95
Open
dependabot[bot] wants to merge 10000 commits intomainfrom
Conversation
dependabot
bot
added
the
dependencies
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/frontends/admin-panel/eslint-import-resolver-typescript-3.6.3
branch
from
32ccf1e to
611d21d
Compare
…alues (Recidiviz/recidiviz-data#33243) ## Description of the change Lydia ran into a bug in our external_id clustering algorithm when trying to cluster a group of ids whose edges are represented as a long chain. It turns out the clustering algorithm only worked when the edges were presented in a particular order. This PR fixes the bug and adds a few tests that failed before the change. ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Unblocks Recidiviz/recidiviz-data#33186 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [x] This pull request has a descriptive title and information useful to a reviewer - [x] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 4a216a529edce3f14d0934e6271cd655725c0fce
…-data#33219) ## Description of the change Updates feature gates so the US_OR ingest pipeline will run normalization and output to `us_or_normalized_state_new`. Downstream processes will still read from `us_or_normalized_state` / `us_or_state`. There is a `--pre_normalization_only` flag you can run if you want to run sandbox pipelines without running normalization (e.g. because it's faster). Successful (non-crashing) pipeline run [here](https://console.cloud.google.com/dataflow/jobs/us-west1/2024-09-06_12_11_19-13736956035355378549;graphView=0?project=recidiviz-staging&authuser=0&organizationId=448885369991) ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Part of Recidiviz/recidiviz-data#29517 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [x] This pull request has a descriptive title and information useful to a reviewer - [x] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 6e5c9fa3b2f5d4d068b9bdf93c83f77abb93b054
…z-data#33207) ## Description of the change Added `google_sheet_backed_tables` and `manually_updated_source_tables` to bigquery-scheduled-queries.tf. ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [x] This pull request has a descriptive title and information useful to a reviewer - [x] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 3f1fc9cbd19fbc00556c0cf258d5dabf92152882
…ecidiviz/recidiviz-data#33249) Bumps [google-protobuf](https://github.com/protocolbuffers/protobuf-javascript) from 3.21.2 to 3.21.4. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/protocolbuffers/protobuf-javascript/releases">google-protobuf's releases</a>.</em></p> <blockquote> <h2>v3.21.4</h2> <p>Release to fix bazel build layering issue in 3.21.3.</p> <h2>v3.21.3</h2> <p>This release consists of mostly minor changes:</p> <ul> <li>Documentation link fixes</li> <li>Updated code generator to work with upstream API changes</li> <li>Groundwork for moving to Bazel modules</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/protocolbuffers/protobuf-javascript/blob/main/protobuf_javascript_release.bzl">google-protobuf's changelog</a>.</em></p> <blockquote> <p>"""Generates package naming variables for use with rules_pkg."""</p> <p>load("<a href="https://github.com/bazel"><code>@bazel</code></a>_tools//tools/cpp:toolchain_utils.bzl", "find_cpp_toolchain") load("<a href="https://github.com/rules"><code>@rules</code></a>_pkg//:providers.bzl", "PackageVariablesInfo")</p> <p>_PROTOBUF_JAVASCRIPT_VERSION = "3.21.4"</p> <p>def _package_naming_impl(ctx): values = {} values["version"] = _PROTOBUF_JAVASCRIPT_VERSION</p> <pre><code>if ctx.attr.platform != "": values["platform"] = ctx.attr.platform return PackageVariablesInfo(values = values) <h1>infer from the current cpp toolchain.</h1> <p>toolchain = find_cpp_toolchain(ctx) cpu = toolchain.cpu system_name = toolchain.target_gnu_system_name</p> <h1>rename cpus to match what we want artifacts to be</h1> <p>if cpu == "systemz": cpu = "s390_64" elif cpu == "aarch64": cpu = "aarch_64" elif cpu == "ppc64": cpu = "ppcle_64"</p> <h1>use the system name to determine the os and then create platform names</h1> <p>if "apple" in system_name: values["platform"] = "osx-" + cpu elif "linux" in system_name: values["platform"] = "linux-" + cpu elif "mingw" in system_name: if cpu == "x86_64": values["platform"] = "win64" else: values["platform"] = "win32" else: values["platform"] = "unknown"</p> <p>return PackageVariablesInfo(values = values) </code></pre></p> <p>package_naming = rule( implementation = _package_naming_impl, attrs = { # Necessary data dependency for find_cpp_toolchain. "_cc_toolchain": attr.label( default = Label("<a href="https://github.com/bazel"><code>@bazel</code></a>_tools//tools/cpp:current_cc_toolchain"), ),</p> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/protocolbuffers/protobuf-javascript/commit/5aee743b83ddf64aa40b0bdd44769111a0761118"><code>5aee743</code></a> Update version to 3.21.4</li> <li><a href="https://github.com/protocolbuffers/protobuf-javascript/commit/4cd555a799daf2e00303ebe089807ea46e5d58b4"><code>4cd555a</code></a> Update various workflow action versions for node 20 compatibility</li> <li><a href="https://github.com/protocolbuffers/protobuf-javascript/commit/dae06f259d646b70d70b8dd27311af7e727caebf"><code>dae06f2</code></a> fix generator build layering by correcting deps</li> <li><a href="https://github.com/protocolbuffers/protobuf-javascript/commit/fd8f7f7f90e10d58a8753049c868c5f94819035c"><code>fd8f7f7</code></a> belatedly update package.json version to 3.21.3</li> <li><a href="https://github.com/protocolbuffers/protobuf-javascript/commit/c4fbfe3b58631a80c73a2bb10c6a67c783a6080d"><code>c4fbfe3</code></a> Adopt protobuf's .bazelrc to simplify cross-compilation</li> <li><a href="https://github.com/protocolbuffers/protobuf-javascript/commit/8afb6ebd19ce19fc6adb1feef3949702e6efa469"><code>8afb6eb</code></a> Bump MODULE.bazel version to match protobuf_javascript_release.bzl</li> <li><a href="https://github.com/protocolbuffers/protobuf-javascript/commit/eb860eb9d6af8bca07ffdffbc420b023ac384236"><code>eb860eb</code></a> Pin rules_python to 0.24.0 to fix release build error</li> <li><a href="https://github.com/protocolbuffers/protobuf-javascript/commit/5d939dbc8fd5245c4316d52c203a1bff24bac5c4"><code>5d939db</code></a> Bump version to 3.21.3</li> <li><a href="https://github.com/protocolbuffers/protobuf-javascript/commit/bd0540e2dcfa1b44369f83527b504cc8d16abd00"><code>bd0540e</code></a> Switch to bazel-contrib/setup-bazel</li> <li><a href="https://github.com/protocolbuffers/protobuf-javascript/commit/05560593d93e7207e84829b3ab6a80c08078e389"><code>0556059</code></a> Fix sha256 digest for protobuf http_archive (<a href="https://redirect.github.com/protocolbuffers/protobuf-javascript/issues/210">Recidiviz/recidiviz-data#210</a>)</li> <li>Additional commits viewable in <a href="https://github.com/protocolbuffers/protobuf-javascript/compare/v3.21.2...v3.21.4">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will 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 version` will 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 dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> GitOrigin-RevId: 3736f26071073f2af0f00a21415119c72983c607
…-data#33223) ## Description of the change Updates feature gates so the US_MI ingest pipeline will run normalization and output to `us_mi_normalized_state_new`. Downstream processes will still read from `us_mi_normalized_state` / `us_mi_state`. There is a `--pre_normalization_only` flag you can run if you want to run sandbox pipelines without running normalization (e.g. because it's faster). Successful (non-crashing) pipeline run [here](https://console.cloud.google.com/dataflow/jobs/us-west1/2024-09-06_10_45_17-14825413111503778068;graphView=0?project=recidiviz-staging&authuser=0&organizationId=448885369991) ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Part of Recidiviz/recidiviz-data#29517 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [x] This pull request has a descriptive title and information useful to a reviewer - [x] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 56c7f1c1bea522041d809ff7c49aea19bc687a33
…prototype-app (Recidiviz/recidiviz-data#33254) Bumps [react-router-dom](https://github.com/remix-run/react-router/tree/HEAD/packages/react-router-dom) from 6.26.1 to 6.26.2. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/remix-run/react-router/releases">react-router-dom's releases</a>.</em></p> <blockquote> <h2>react-router-dom-v5-compat@6.4.0-pre.15</h2> <h3>Patch Changes</h3> <ul> <li>Updated dependencies <ul> <li>react-router@6.4.0-pre.15</li> <li>react-router-dom@6.4.0-pre.15</li> </ul> </li> </ul> <h2>react-router-dom-v5-compat@6.4.0-pre.11</h2> <h3>Patch Changes</h3> <ul> <li>Updated dependencies <ul> <li>react-router@6.4.0-pre.11</li> <li>react-router-dom@6.4.0-pre.11</li> </ul> </li> </ul> <h2>react-router-dom-v5-compat@6.4.0-pre.10</h2> <h3>Patch Changes</h3> <ul> <li>Updated dependencies <ul> <li>react-router@6.4.0-pre.10</li> <li>react-router-dom@6.4.0-pre.10</li> </ul> </li> </ul> <h2>react-router-dom-v5-compat@6.4.0-pre.9</h2> <h3>Patch Changes</h3> <ul> <li>Updated dependencies <ul> <li>react-router@6.4.0-pre.9</li> <li>react-router-dom@6.4.0-pre.9</li> </ul> </li> </ul> <h2>react-router-dom-v5-compat@6.4.0-pre.8</h2> <h3>Patch Changes</h3> <ul> <li>Updated dependencies <ul> <li>react-router@6.4.0-pre.8</li> <li>react-router-dom@6.4.0-pre.8</li> </ul> </li> </ul> <h2>react-router-dom-v5-compat@6.4.0-pre.7</h2> <h3>Patch Changes</h3> <ul> <li>Updated dependencies <ul> <li><code>react-router@6.4.0-pre.7</code></li> <li><code>react-router-dom@6.4.0-pre.7</code></li> </ul> </li> </ul> <h2>react-router-dom-v5-compat@6.4.0-pre.6</h2> <h3>Patch Changes</h3> <ul> <li>44bce3c6: Fix <code>react-router-dom</code> peer dependency version <ul> <li>react-router@6.4.0-pre.6</li> <li>react-router-dom@6.4.0-pre.6</li> </ul> </li> </ul> <h2>react-router-dom-v5-compat@6.4.0-pre.5</h2> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/remix-run/react-router/blob/main/packages/react-router-dom/CHANGELOG.md">react-router-dom's changelog</a>.</em></p> <blockquote> <h2>6.26.2</h2> <h3>Patch Changes</h3> <ul> <li>Updated dependencies: <ul> <li><code>@remix-run/router@1.19.2</code></li> <li><code>react-router@6.26.2</code></li> </ul> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/remix-run/react-router/commit/eeb86ab07f11d8cbd28e886ee31103a4bfc25cb7"><code>eeb86ab</code></a> chore: Update version for release (<a href="https://github.com/remix-run/react-router/tree/HEAD/packages/react-router-dom/issues/11968">Recidiviz/recidiviz-data#11968</a>)</li> <li><a href="https://github.com/remix-run/react-router/commit/7cbe349fac324fdf908ef39c5528c633610fbc78"><code>7cbe349</code></a> chore: Update version for release (pre) (<a href="https://github.com/remix-run/react-router/tree/HEAD/packages/react-router-dom/issues/11955">Recidiviz/recidiviz-data#11955</a>)</li> <li><a href="https://github.com/remix-run/react-router/commit/64835156f7dd779abe7ac42e6b688012ba603bbf"><code>6483515</code></a> Merge branch 'release-next' into v6</li> <li><a href="https://github.com/remix-run/react-router/commit/05612a3011290dd6134009298628c98a5da96bbd"><code>05612a3</code></a> unstable_dataStrategy refactor for better single fetch support (<a href="https://github.com/remix-run/react-router/tree/HEAD/packages/react-router-dom/issues/11943">Recidiviz/recidiviz-data#11943</a>)</li> <li><a href="https://github.com/remix-run/react-router/commit/5651176d86f3bf71b80301810e6bfaa2cf187ee6"><code>5651176</code></a> fix: Wait for restore url navigation to complete before proceeding (<a href="https://github.com/remix-run/react-router/tree/HEAD/packages/react-router-dom/issues/11930">Recidiviz/recidiviz-data#11930</a>)</li> <li>See full diff in <a href="https://github.com/remix-run/react-router/commits/react-router-dom@6.26.2/packages/react-router-dom">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will 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 version` will 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 dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> GitOrigin-RevId: c83b551358315410884df6b4b5c16d5e89067ec9
…neration (Recidiviz/recidiviz-data#33255) Bumps @recidiviz/design-system from 5.0.0 to 5.7.0. [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will 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 version` will 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 dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> GitOrigin-RevId: f366f309723ab26711e570dd652e03dc87bd6a75
…/recidiviz-data#33256) Bumps [zod](https://github.com/colinhacks/zod) from 3.22.3 to 3.23.8. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/colinhacks/zod/releases">zod's releases</a>.</em></p> <blockquote> <h2>v3.23.8</h2> <h2>Commits:</h2> <ul> <li>0f4d403558ae0490c711e4c2bfcf6c200bd14e11 Add Bronze logos (<a href="https://redirect.github.com/colinhacks/zod/issues/3470">Recidiviz/recidiviz-data#3470</a>)</li> <li>19687315b5b24bbd1ff6c346bfc2975700221748 Tweak tiers (<a href="https://redirect.github.com/colinhacks/zod/issues/3471">Recidiviz/recidiviz-data#3471</a>)</li> <li>eda7df314399929f7ed737423868a5a0780cd944 Change RefinementCtx to interface</li> <li>ca42965df46b2f7e2747db29c40a26bcb32a51d5 v3.23.8</li> </ul> <h2>v3.23.7</h2> <h2>Commits:</h2> <ul> <li>29d2ea2a15f0b1ac4b89138041f786a3dafc490b Add copper</li> <li>d969423266fccee56ef769da6744cc8bacb04550 Fix <a href="https://redirect.github.com/colinhacks/zod/issues/3437">Recidiviz/recidiviz-data#3437</a>: extendShape erases JSDoc property documentation (<a href="https://redirect.github.com/colinhacks/zod/issues/3463">Recidiviz/recidiviz-data#3463</a>)</li> <li>2239ff3ccc9af4d28bee27bd6fb2a5632844480b Add social crow</li> <li>f985b5b922cb357dbf4b25bb43814d19f838e046 3.23.7</li> </ul> <h2>v3.23.6</h2> <h2>Commits:</h2> <ul> <li>bc0095aab9e7254deb18701adc63de128ca2c742 Test on latest node</li> <li>6e5699a30373cc22879f2bcb6902fc138518c980 Lint on latest node</li> <li>1f466d9d00f446d7bed1962990e7a1ce813ab0d4 describe how one can protect from cyclical objects starting an infini… (<a href="https://redirect.github.com/colinhacks/zod/issues/3447">Recidiviz/recidiviz-data#3447</a>)</li> <li>3fed6f21e0ea7adc91aa0cc44f75bcf4e526d98e Add zod playground link (<a href="https://redirect.github.com/colinhacks/zod/issues/3454">Recidiviz/recidiviz-data#3454</a>)</li> <li>04e1f379f6989d23dd45660fcabc78f76d7834f8 Fixed freezing async ZodReadonly results (<a href="https://redirect.github.com/colinhacks/zod/issues/3457">Recidiviz/recidiviz-data#3457</a>)</li> <li>b87e59d0e4bbb4403bf27243afdcda9fcdeec258 Update sponsor tiers (<a href="https://redirect.github.com/colinhacks/zod/issues/3453">Recidiviz/recidiviz-data#3453</a>)</li> <li>143886151bba3930bdcc10d34a1cff4bf9103ba8 Add copper tier (<a href="https://redirect.github.com/colinhacks/zod/issues/3460">Recidiviz/recidiviz-data#3460</a>)</li> <li>ce3711e1384952d255769b9495f9bfadfb327291 add VSCode dev container support and documenation</li> <li>93b480b12ec3466cbd3b4182f7ce292e5c61528c v3.23.6</li> </ul> <h2>v3.23.5</h2> <h2>Commits:</h2> <ul> <li>110b8211f991b3e060ab2da4fec7b63d600439ad Update README_ZH.md (<a href="https://redirect.github.com/colinhacks/zod/issues/3433">Recidiviz/recidiviz-data#3433</a>)</li> <li>c1910bdfc98709b8f14231e2cefc5a3be401e3ee Made ZodEnum take readonly string array (<a href="https://redirect.github.com/colinhacks/zod/issues/3444">Recidiviz/recidiviz-data#3444</a>)</li> <li>541a862e978f96eb391849a6bf16be84231aa1b3 3.23.5</li> </ul> <h2>v3.23.4</h2> <h2>Commits:</h2> <ul> <li>157b18d742c86d85b26a8421af46ad6d6d6b6ea7 Add 3.23 announcement</li> <li>aedf93f1435a29463d915c3be45b4dcbeefa8cc1 Revert change to default Input</li> <li>45107f7a7230fe48ee24dc37e621422c9dc64ec4 v3.23.4</li> </ul> <h2>v3.23.3</h2> <h2>Commits:</h2> <ul> <li>103d2436f85872ca0e0e6247652989cc93d46a39 3.23.3</li> </ul> <h2>v3.23.2</h2> <h2>Commits:</h2> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/colinhacks/zod/commit/ca42965df46b2f7e2747db29c40a26bcb32a51d5"><code>ca42965</code></a> v3.23.8</li> <li><a href="https://github.com/colinhacks/zod/commit/eda7df314399929f7ed737423868a5a0780cd944"><code>eda7df3</code></a> Change RefinementCtx to interface</li> <li><a href="https://github.com/colinhacks/zod/commit/19687315b5b24bbd1ff6c346bfc2975700221748"><code>1968731</code></a> Tweak tiers (<a href="https://redirect.github.com/colinhacks/zod/issues/3471">Recidiviz/recidiviz-data#3471</a>)</li> <li><a href="https://github.com/colinhacks/zod/commit/0f4d403558ae0490c711e4c2bfcf6c200bd14e11"><code>0f4d403</code></a> Add Bronze logos (<a href="https://redirect.github.com/colinhacks/zod/issues/3470">Recidiviz/recidiviz-data#3470</a>)</li> <li><a href="https://github.com/colinhacks/zod/commit/f985b5b922cb357dbf4b25bb43814d19f838e046"><code>f985b5b</code></a> 3.23.7</li> <li><a href="https://github.com/colinhacks/zod/commit/2239ff3ccc9af4d28bee27bd6fb2a5632844480b"><code>2239ff3</code></a> Add social crow</li> <li><a href="https://github.com/colinhacks/zod/commit/d969423266fccee56ef769da6744cc8bacb04550"><code>d969423</code></a> Fix <a href="https://redirect.github.com/colinhacks/zod/issues/3437">Recidiviz/recidiviz-data#3437</a>: extendShape erases JSDoc property documentation (<a href="https://redirect.github.com/colinhacks/zod/issues/3463">Recidiviz/recidiviz-data#3463</a>)</li> <li><a href="https://github.com/colinhacks/zod/commit/29d2ea2a15f0b1ac4b89138041f786a3dafc490b"><code>29d2ea2</code></a> Add copper</li> <li><a href="https://github.com/colinhacks/zod/commit/93b480b12ec3466cbd3b4182f7ce292e5c61528c"><code>93b480b</code></a> v3.23.6</li> <li><a href="https://github.com/colinhacks/zod/commit/ce3711e1384952d255769b9495f9bfadfb327291"><code>ce3711e</code></a> add VSCode dev container support and documenation</li> <li>Additional commits viewable in <a href="https://github.com/colinhacks/zod/compare/v3.22.3...v3.23.8">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will 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 version` will 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 dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> GitOrigin-RevId: 73f61a6616d4a42d39e26a13c9a31459c1bfdcff
## Description of the change IA HATH BESTOWED DATA UPON US. ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Closes #XXXX ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 5988055695c800f666b1dfcd92e28e5bc760d97d
…ecidiviz/recidiviz-data#33240) ## Description of the change We previously had extra logic in a cleaning CTE in the TN IP ingest view in order to address what we thought might be incorrectly logged movement in OffenderMovement. However, in doing that, we ended up eliminating some periods that we actually do want to keep. What we have also noted over time is that OffenderMovement is not the cleanest data source possible, so overly cleaning up periods in the view ends up being overly restricting and creating more errors than it helps. This PR removes the gating criteria in this cleaning CTE and instead only keeps out periods we know to be fully erroneous (starting with a termination). This change adds 14000 out of now 7894912 periods, an increase of 1%. Validation for this will happen in gheidkamp_scratch to compare previous scores and eligibility numbers. Pipeline runs for this change are found under the prefix gheidkamp11. ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Closes #XXXX ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [x] This pull request has a descriptive title and information useful to a reviewer - [x] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 06aa19c7550c98a62172a6c83c6bbeee8e813e53
…Recidiviz/recidiviz-data#33258) Bumps [express](https://github.com/expressjs/express) from 4.19.2 to 4.20.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/expressjs/express/releases">express's releases</a>.</em></p> <blockquote> <h2>4.20.0</h2> <h2>What's Changed</h2> <h3>Important</h3> <ul> <li>IMPORTANT: The default <code>depth</code> level for parsing URL-encoded data is now <code>32</code> (previously was <code>Infinity</code>)</li> <li>Remove link renderization in html while using <code>res.redirect</code></li> </ul> <h3>Other Changes</h3> <ul> <li>4.19.2 Staging by <a href="https://github.com/wesleytodd"><code>@wesleytodd</code></a> in <a href="https://redirect.github.com/expressjs/express/pull/5561">expressjs/expressRecidiviz/recidiviz-data#5561</a></li> <li>remove duplicate location test for data uri by <a href="https://github.com/wesleytodd"><code>@wesleytodd</code></a> in <a href="https://redirect.github.com/expressjs/express/pull/5562">expressjs/expressRecidiviz/recidiviz-data#5562</a></li> <li>feat: document beta releases expectations by <a href="https://github.com/marco-ippolito"><code>@marco-ippolito</code></a> in <a href="https://redirect.github.com/expressjs/express/pull/5565">expressjs/expressRecidiviz/recidiviz-data#5565</a></li> <li>Cut down on duplicated CI runs by <a href="https://github.com/jonchurch"><code>@jonchurch</code></a> in <a href="https://redirect.github.com/expressjs/express/pull/5564">expressjs/expressRecidiviz/recidiviz-data#5564</a></li> <li>Add a Threat Model by <a href="https://github.com/UlisesGascon"><code>@UlisesGascon</code></a> in <a href="https://redirect.github.com/expressjs/express/pull/5526">expressjs/expressRecidiviz/recidiviz-data#5526</a></li> <li>Assign captain of encodeurl by <a href="https://github.com/blakeembrey"><code>@blakeembrey</code></a> in <a href="https://redirect.github.com/expressjs/express/pull/5579">expressjs/expressRecidiviz/recidiviz-data#5579</a></li> <li>Nominate jonchurch as repo captain for <code>http-errors</code>, <code>expressjs.com</code>, <code>morgan</code>, <code>cors</code>, <code>body-parser</code> by <a href="https://github.com/jonchurch"><code>@jonchurch</code></a> in <a href="https://redirect.github.com/expressjs/express/pull/5587">expressjs/expressRecidiviz/recidiviz-data#5587</a></li> <li>docs: update Security.md by <a href="https://github.com/inigomarquinez"><code>@inigomarquinez</code></a> in <a href="https://redirect.github.com/expressjs/express/pull/5590">expressjs/expressRecidiviz/recidiviz-data#5590</a></li> <li>docs: update triage nomination policy by <a href="https://github.com/UlisesGascon"><code>@UlisesGascon</code></a> in <a href="https://redirect.github.com/expressjs/express/pull/5600">expressjs/expressRecidiviz/recidiviz-data#5600</a></li> <li>Add CodeQL (SAST) by <a href="https://github.com/UlisesGascon"><code>@UlisesGascon</code></a> in <a href="https://redirect.github.com/expressjs/express/pull/5433">expressjs/expressRecidiviz/recidiviz-data#5433</a></li> <li>docs: add UlisesGascon as triage initiative captain by <a href="https://github.com/UlisesGascon"><code>@UlisesGascon</code></a> in <a href="https://redirect.github.com/expressjs/express/pull/5605">expressjs/expressRecidiviz/recidiviz-data#5605</a></li> <li>deps: encodeurl@~2.0.0 by <a href="https://github.com/blakeembrey"><code>@blakeembrey</code></a> in <a href="https://redirect.github.com/expressjs/express/pull/5569">expressjs/expressRecidiviz/recidiviz-data#5569</a></li> <li>skip QUERY method test by <a href="https://github.com/jonchurch"><code>@jonchurch</code></a> in <a href="https://redirect.github.com/expressjs/express/pull/5628">expressjs/expressRecidiviz/recidiviz-data#5628</a></li> <li>ignore ETAG query test on 21 and 22, reuse skip util by <a href="https://github.com/jonchurch"><code>@jonchurch</code></a> in <a href="https://redirect.github.com/expressjs/express/pull/5639">expressjs/expressRecidiviz/recidiviz-data#5639</a></li> <li>add support Node.js@22 in the CI by <a href="https://github.com/mertcanaltin"><code>@mertcanaltin</code></a> in <a href="https://redirect.github.com/expressjs/express/pull/5627">expressjs/expressRecidiviz/recidiviz-data#5627</a></li> <li>doc: add table of contents, tc/triager lists to readme by <a href="https://github.com/mertcanaltin"><code>@mertcanaltin</code></a> in <a href="https://redirect.github.com/expressjs/express/pull/5619">expressjs/expressRecidiviz/recidiviz-data#5619</a></li> <li>List and sort all projects, add captains by <a href="https://github.com/blakeembrey"><code>@blakeembrey</code></a> in <a href="https://redirect.github.com/expressjs/express/pull/5653">expressjs/expressRecidiviz/recidiviz-data#5653</a></li> <li>docs: add <a href="https://github.com/UlisesGascon"><code>@UlisesGascon</code></a> as captain for cookie-parser by <a href="https://github.com/UlisesGascon"><code>@UlisesGascon</code></a> in <a href="https://redirect.github.com/expressjs/express/pull/5666">expressjs/expressRecidiviz/recidiviz-data#5666</a></li> <li>✨ bring back query tests for node 21 by <a href="https://github.com/ctcpip"><code>@ctcpip</code></a> in <a href="https://redirect.github.com/expressjs/express/pull/5690">expressjs/expressRecidiviz/recidiviz-data#5690</a></li> <li>[v4] Deprecate <code>res.clearCookie</code> accepting <code>options.maxAge</code> and <code>options.expires</code> by <a href="https://github.com/jonchurch"><code>@jonchurch</code></a> in <a href="https://redirect.github.com/expressjs/express/pull/5672">expressjs/expressRecidiviz/recidiviz-data#5672</a></li> <li>skip QUERY tests for Node 21 only, still not supported by <a href="https://github.com/jonchurch"><code>@jonchurch</code></a> in <a href="https://redirect.github.com/expressjs/express/pull/5695">expressjs/expressRecidiviz/recidiviz-data#5695</a></li> <li>📝 update people, add ctcpip to TC by <a href="https://github.com/ctcpip"><code>@ctcpip</code></a> in <a href="https://redirect.github.com/expressjs/express/pull/5683">expressjs/expressRecidiviz/recidiviz-data#5683</a></li> <li>remove minor version pinning from ci by <a href="https://github.com/jonchurch"><code>@jonchurch</code></a> in <a href="https://redirect.github.com/expressjs/express/pull/5722">expressjs/expressRecidiviz/recidiviz-data#5722</a></li> <li>Fix link variable use in attribution section of CODE OF CONDUCT by <a href="https://github.com/IamLizu"><code>@IamLizu</code></a> in <a href="https://redirect.github.com/expressjs/express/pull/5762">expressjs/expressRecidiviz/recidiviz-data#5762</a></li> <li>Replace Appveyor windows testing with GHA by <a href="https://github.com/jonchurch"><code>@jonchurch</code></a> in <a href="https://redirect.github.com/expressjs/express/pull/5599">expressjs/expressRecidiviz/recidiviz-data#5599</a></li> <li>Add OSSF Scorecard badge by <a href="https://github.com/UlisesGascon"><code>@UlisesGascon</code></a> in <a href="https://redirect.github.com/expressjs/express/pull/5436">expressjs/expressRecidiviz/recidiviz-data#5436</a></li> <li>update scorecard link by <a href="https://github.com/bjohansebas"><code>@bjohansebas</code></a> in <a href="https://redirect.github.com/expressjs/express/pull/5814">expressjs/expressRecidiviz/recidiviz-data#5814</a></li> <li>Nominate <a href="https://github.com/IamLizu"><code>@IamLizu</code></a> to the triage team by <a href="https://github.com/UlisesGascon"><code>@UlisesGascon</code></a> in <a href="https://redirect.github.com/expressjs/express/pull/5836">expressjs/expressRecidiviz/recidiviz-data#5836</a></li> <li>deps: path-to-regexp@0.1.8 by <a href="https://github.com/blakeembrey"><code>@blakeembrey</code></a> in <a href="https://redirect.github.com/expressjs/express/pull/5603">expressjs/expressRecidiviz/recidiviz-data#5603</a></li> <li>docs: specify new instructions for <code>question</code> and <code>discuss</code> by <a href="https://github.com/IamLizu"><code>@IamLizu</code></a> in <a href="https://redirect.github.com/expressjs/express/pull/5835">expressjs/expressRecidiviz/recidiviz-data#5835</a></li> <li>4.x: Upgrade <code>merge-descriptors</code> dependency by <a href="https://github.com/RobinTail"><code>@RobinTail</code></a> in <a href="https://redirect.github.com/expressjs/express/pull/5781">expressjs/expressRecidiviz/recidiviz-data#5781</a></li> <li>path-to-regexp@0.1.10 by <a href="https://github.com/blakeembrey"><code>@blakeembrey</code></a> in <a href="https://redirect.github.com/expressjs/express/pull/5902">expressjs/expressRecidiviz/recidiviz-data#5902</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/marco-ippolito"><code>@marco-ippolito</code></a> made their first contribution in <a href="https://redirect.github.com/expressjs/express/pull/5565">expressjs/expressRecidiviz/recidiviz-data#5565</a></li> <li><a href="https://github.com/inigomarquinez"><code>@inigomarquinez</code></a> made their first contribution in <a href="https://redirect.github.com/expressjs/express/pull/5590">expressjs/expressRecidiviz/recidiviz-data#5590</a></li> <li><a href="https://github.com/mertcanaltin"><code>@mertcanaltin</code></a> made their first contribution in <a href="https://redirect.github.com/expressjs/express/pull/5627">expressjs/expressRecidiviz/recidiviz-data#5627</a></li> <li><a href="https://github.com/ctcpip"><code>@ctcpip</code></a> made their first contribution in <a href="https://redirect.github.com/expressjs/express/pull/5690">expressjs/expressRecidiviz/recidiviz-data#5690</a></li> <li><a href="https://github.com/bjohansebas"><code>@bjohansebas</code></a> made their first contribution in <a href="https://redirect.github.com/expressjs/express/pull/5814">expressjs/expressRecidiviz/recidiviz-data#5814</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/expressjs/express/compare/4.19.1...4.20.0">https://github.com/expressjs/express/compare/4.19.1...4.20.0</a></p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/expressjs/express/blob/master/History.md">express's changelog</a>.</em></p> <blockquote> <h1>4.20.0 / 2024-09-10</h1> <ul> <li>deps: serve-static@0.16.0 <ul> <li>Remove link renderization in html while redirecting</li> </ul> </li> <li>deps: send@0.19.0 <ul> <li>Remove link renderization in html while redirecting</li> </ul> </li> <li>deps: body-parser@0.6.0 <ul> <li>add <code>depth</code> option to customize the depth level in the parser</li> <li>IMPORTANT: The default <code>depth</code> level for parsing URL-encoded data is now <code>32</code> (previously was <code>Infinity</code>)</li> </ul> </li> <li>Remove link renderization in html while using <code>res.redirect</code></li> <li>deps: path-to-regexp@0.1.10 <ul> <li>Adds support for named matching groups in the routes using a regex</li> <li>Adds backtracking protection to parameters without regexes defined</li> </ul> </li> <li>deps: encodeurl@~2.0.0 <ul> <li>Removes encoding of <code>\</code>, <code>|</code>, and <code>^</code> to align better with URL spec</li> </ul> </li> <li>Deprecate passing <code>options.maxAge</code> and <code>options.expires</code> to <code>res.clearCookie</code> <ul> <li>Will be ignored in v5, clearCookie will set a cookie with an expires in the past to instruct clients to delete the cookie</li> </ul> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/expressjs/express/commit/21df421ebc7a5249bb31101da666bbf22adc3f18"><code>21df421</code></a> 4.20.0</li> <li><a href="https://github.com/expressjs/express/commit/4c9ddc1c47bf579e55c2fe837d76a952e9fd8959"><code>4c9ddc1</code></a> feat: upgrade to serve-static@0.16.0</li> <li><a href="https://github.com/expressjs/express/commit/9ebe5d500d22cbb2b8aaa73446866b084c747971"><code>9ebe5d5</code></a> feat: upgrade to send@0.19.0 (<a href="https://redirect.github.com/expressjs/express/issues/5928">Recidiviz/recidiviz-data#5928</a>)</li> <li><a href="https://github.com/expressjs/express/commit/ec4a01b6b8814d7b007f36a3023f4dbafdbc3d09"><code>ec4a01b</code></a> feat: upgrade to body-parser@1.20.3 (<a href="https://redirect.github.com/expressjs/express/issues/5926">Recidiviz/recidiviz-data#5926</a>)</li> <li><a href="https://github.com/expressjs/express/commit/54271f69b511fea198471e6ff3400ab805d6b553"><code>54271f6</code></a> fix: don't render redirect values in anchor href</li> <li><a href="https://github.com/expressjs/express/commit/125bb742a38cd97938a3932b47cc301e41c31f5d"><code>125bb74</code></a> path-to-regexp@0.1.10 (<a href="https://redirect.github.com/expressjs/express/issues/5902">Recidiviz/recidiviz-data#5902</a>)</li> <li><a href="https://github.com/expressjs/express/commit/2a980ad16052e53b398c9953fea50e3daa0b495c"><code>2a980ad</code></a> merge-descriptors@1.0.3 (<a href="https://redirect.github.com/expressjs/express/issues/5781">Recidiviz/recidiviz-data#5781</a>)</li> <li><a href="https://github.com/expressjs/express/commit/a3e7e05e0a435b7b4be25bd38d8d0ca19a773ca9"><code>a3e7e05</code></a> docs: specify new instructions for <code>question</code> and <code>discuss</code></li> <li><a href="https://github.com/expressjs/express/commit/c5addb9a17c5b4c9fccdd2c04153a30595e03385"><code>c5addb9</code></a> deps: path-to-regexp@0.1.8 (<a href="https://redirect.github.com/expressjs/express/issues/5603">Recidiviz/recidiviz-data#5603</a>)</li> <li><a href="https://github.com/expressjs/express/commit/e35380a39d94937e3d0f7119e0efbc7cd69d003f"><code>e35380a</code></a> docs: add <a href="https://github.com/IamLizu"><code>@IamLizu</code></a> to the triage team (<a href="https://redirect.github.com/expressjs/express/issues/5836">Recidiviz/recidiviz-data#5836</a>)</li> <li>Additional commits viewable in <a href="https://github.com/expressjs/express/compare/4.19.2...4.20.0">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will 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 version` will 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 dependency` will 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](https://github.com/Recidiviz/recidiviz-data/network/alerts). </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> GitOrigin-RevId: 6ebd7e83dee2a854a49d7159268b1e0f6b8e92b1
…om 3 to 6 months (Recidiviz/recidiviz-data#33216) ## Description of the change Change the almost eligible period for PA administrative supervision from 3 to 6 months, as per [this discussion](https://github.com/Recidiviz/recidiviz-data/issues/31793) ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Closes #XXXX ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [ ] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: c852bb45f3e8b55936db67123c91bd62e2273cbe
…ogic (Recidiviz/recidiviz-data#33210) ## Description of the change Adds eligibility logic for the ACTION_STRATEGY_OUTLIER_NEW_OFFICER action strategy. This is the final strategy! Also adds a comprehensive test in outliers_routes_test to test the priority/overall logic. Note: do not merge until after the prod deploy today when the new column will hit production. ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Closes Recidiviz/recidiviz-data#31579 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: b705be181dcf92dd7f8d5955c9849a76cdb48a67
…-data#33227) ## Description of the change Updates feature gates so the US_PA ingest pipeline will run normalization and output to `us_pa_normalized_state_new`. Downstream processes will still read from `us_pa_normalized_state` / `us_pa_state`. There is a `--pre_normalization_only` flag you can run if you want to run sandbox pipelines without running normalization (e.g. because it's faster). Successful (non-crashing) pipeline run [here](https://console.cloud.google.com/dataflow/jobs/us-west1/2024-09-06_12_12_09-13999410380172440098;graphView=0?project=recidiviz-staging&authuser=0&organizationId=448885369991) ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Part of Recidiviz/recidiviz-data#29517 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [x] This pull request has a descriptive title and information useful to a reviewer - [x] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 80bf00de491f4ac882434f04e0d7d12cca26d0e7
…#33172) ## Description of the change I made an implementation change to the code previously in Recidiviz/recidiviz-data#32804 in order to support both MI restrictive housing and OR supervision early discharge. I also broke out this infra change into a separate PR in order to delink the MI and OR PRs and make things more digestible (hopefully): Add a new `CriteriaCondition` subclass `EligibleCriteriaCondition` to support logic like "almost eligible X time before full eligibility". This implementation replaces the need for the `_DateComparatorCriteriaCondition .include_meets_criteria_spans` parameter, and provides two benefits beyond the `include_meets_criteria_spans` version: - `EligibleCriteriaCondition` also includes cases where the relevant reason field/critical date is NULL and the criteria `meets_default` is True, whereas the previous implementation would not count those spans since they did not meet the date condition. This occurs in OR early discharge where spans that have NULL `latest_supervision_sanction_date` AND `sentence_eligibility_date` past the threshold should be considered almost eligible. - `EligibleCriteriaCondition` can be applied in conjunction with other `CriteriaCondition` objects like `LessThanCriteriaCondition` to support almost eligible composite criteria like "almost eligible if less than $1,000 owed in fees", whereas the previous implementation only applied to the date comparator condition types. I did add an input validation though to ensure someone cannot have `EligibleCriteriaCondition` and `NotEligibleCriteriaCondition` objects applied to the same criteria within the same composite group. ## Related issues Closes Recidiviz/recidiviz-data#33080 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [ ] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [ ] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 5947917629ce03d1172740ae519ddd440e01fc40
…-data#33225) ## Description of the change Updates feature gates so the US_ME ingest pipeline will run normalization and output to `us_me_normalized_state_new`. Downstream processes will still read from `us_me_normalized_state` / `us_me_state`. There is a `--pre_normalization_only` flag you can run if you want to run sandbox pipelines without running normalization (e.g. because it's faster). Successful (non-crashing) pipeline run [here](https://console.cloud.google.com/dataflow/jobs/us-west1/2024-09-06_10_44_39-4126036516187747315;graphView=0?project=recidiviz-staging&authuser=0&organizationId=448885369991&pageState=(%22dfTime%22:(%22l%22:%22dfJobMaxTime%22))) ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Part of Recidiviz/recidiviz-data#29517 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [x] This pull request has a descriptive title and information useful to a reviewer - [x] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 7c9460407266ac00ab85a8863ae9b1f13a93ffec
…(Recidiviz/recidiviz-data#33260) ## Description of the change Change years required to serve reason in PA special circumstances opportunity from string to int ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Closes #XXXX ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [ ] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 54099c7b53afa9e3208c78870ae19d68fb4a53b3
…-data#33198) ## Description of the change In the new import DAG, we are unintentionally writing column headers as values to the raw data table every time we import a file. We should read and verify the file headers for both files requiring normalization and import ready files, and return the headers in the order they are found in the raw file (or in the raw file config if the file does not have a header row) in order to use as the table schema when we load the raw data to a temporary bq table later in the import process. Also refactored `DirectIngestRawFileHeaderReader` for easier mocking ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Recidiviz/recidiviz-data#33195 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [x] This pull request has a descriptive title and information useful to a reviewer - [x] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 346c5eb0b464a1dd44d12fff1dfe8eb6e0ef5d1c
…ecidiviz-data#33259) ## Description of the change This PR filters out routes and feature variants with a "false" value from displaying in the State User Permissions and State Role Default Permissions tables of the admin panel. In other words, now only routes and feature variants that a particular user or role has access to are displayed. Also, the display format was adjusted slightly: - Routes: display only the route name (e.g., `myRoute`) - Feature variants: if the variant has no active date (i.e., "always on") or its active date is in the past, display only the feature variant name (e.g., `myVariant`). If the active date is in the future, display the feature variant name along with the active date (e.g., `myVariant: Oct 11, 2024 1:45 PM`) ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Closes Recidiviz/recidiviz-data#33177 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [X] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [ ] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 874ad542f40cddd07b7ee3af0f0d634c3b15a3e3
…ata#33264) ## Description of the change Add `RawFileBigQueryTableSchema` to be used by `ImportReadyFile` types here Recidiviz/recidiviz-data#33263 Remove `PreImportNormalizedFileResult` type since it's not used anywhere ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Recidiviz/recidiviz-data#33195 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [x] This pull request has a descriptive title and information useful to a reviewer - [x] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: b280cb486467bbe29148c51ac4b788650f93f6ff
…iviz-data#33257) ## Description of the change OR receives files historically and therefore should be added to the pruning script but some files need to be exempt because of their usage in ingest views with @ALL. Added those file exemptions in here. ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Part of Recidiviz/recidiviz-data#32605 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [x] This pull request has a descriptive title and information useful to a reviewer - [x] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 3bba9dced96496eb75c82029f95485a23200098f
…st eligible feature (Recidiviz/recidiviz-data#32803) ## Description - Create not enrolled in relevant program criteria and add almost eligible. - Removed FREE THROUGH RECOVERY from the list of programs to surface in case notes - Only surface Health notes when they are currently in progress - Removed mental health notes and general assignments from transfer to min. These are no longer needed. As expected, we get 10 less people eligible (101 to 91): ``` recidiviz-data % python -m recidiviz.tools.load_views_to_sandbox \ --project_id recidiviz-staging\ --sandbox_dataset_prefix hsalas manual \ --dataset_ids_to_load task_eligibility_spans_us_nd,task_eligibility_criteria_us_nd,task_eligibility\ --update_descendants False ``` ## Related issues Closes Recidiviz/recidiviz-data#32555 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [ ] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [ ] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: eab913051933ce5534dba1bae6d8710881979f3b
## Description of the change NE sends us two ID columns - internalID and ID_NBR/inmateNumber - the first gets regenerated every day and the second one only remains as a person's ID through one cycle of incarceration, if they are later re-incarcerated they will receive a new ID_NBR. Because we only received one transfer it looks like internalID was static but that is not true so here I am changing the state person view and adding in and external id view to create one static internal id and connect all of the non-static ids based on a table they provide `prevInmateNumber`. successful pipeline run: https://console.cloud.google.com/dataflow/jobs/us-west1/2024-09-11_10_54_45-11009682693176858547?authuser=0&organizationId=448885369991&project=recidiviz-staging ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Closes #XXXX ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 96964237601fff19da65d950e55317436a97898d
…viz-data#33272) ## Description of the change Adds districts to US_ME users so MAU/WAU metrics that group by region can use these. This change is in the `current_staff` view, so it affects roster sync + the workflows supervision staff record. ME was recently updated to not filter workflows staff by district, so having districts in the staff record should be effectively a no-op for workflows. I also removed the explicit null for OR users because they similarly do not filter by district in workflows, so if we one day got district information all of a sudden for OR staff it could get filled out. ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Closes #XXXX ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [ ] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: ff55837607c9ec6e525dc22f592bf7452d59aa6f
…33273) ## Description of the change We received two files related to programming and job assignments for the first time this morning. This PR adds raw data configs so that they will import as raw data. A note on the utility of these files: the `DOC_ACI_ASSIGN` table was meant to be a decoder for all program assignments, but it actually only contains information about job assignments. Educational programs are presumably included in the `DOC_PR_ASSIGNMENT` table, but we cannot identify them yet. I requested another table from the ADCRR data team that will hopefully let us join in the name of the program to the rest of the information available in `DOC_PR_ASSIGNMENT`. Tests: - [x] PKs are sufficient - [x] files successfully import to sandbox ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Closes #XXXX ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [ ] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [ ] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 0a43bdaf8211d8e51bcc2f2ad03d6b47ca5dd7dc
## Description of the change Adding another exemption for pruning and adding OR to the pruning script ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Closes Recidiviz/recidiviz-data#32940 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 9c717fbad58754ae9f53163a1c68010498375284
…diviz/recidiviz-data#33278) ## Description of the change This view is only used as an input to `metric_benchmarks`, so it doesn't need to go all the way through to the DB. ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Closes Recidiviz/recidiviz-data#31711 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [ ] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 7781c685c733fc2e40da07e0719981c4c9b0babc
## Description of the change New tables from IA and their corresponding yamls ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Closes #XXXX ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: b0c087fab1757e0b6b4249b607f20b4cfa7f8b70
…recidiviz-data#33664) ## Description of the change Moves datasets related to `state` and `normalized_state` to a new dataset config, which should allow us a bit more flexibility in usage without worrying about source visibility. ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | **Type: Non-breaking refactor** | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [ ] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [ ] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: f2dd72f8ba4337c907573de66254f4ab2d4a3648
## Description of the change Autogenerated commit running `pipenv lock --dev` ## Type of change > Check the types that apply, and delete any that are not applicable to your changes - [X] Configuration change (adjusts configuration to achieve some end related to functionality, development, performance, or security) ## Related issues N/A ## Checklists ### Development These boxes should be checked by the submitter prior to merging: - ~~Tests have been written to cover the code changed/added as part of this pull request~~ ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant --------- Co-authored-by: Helper Bot <helperbot@recidiviz.org> Co-authored-by: Anna Geiduschek <anna@recidiviz.org> GitOrigin-RevId: 16ed65435ed72dcd340e066747321960786d4f75
…pper case region_code (Recidiviz/recidiviz-data#33665) ## Description of the change i was operating under the assumption that `region_code` meant `state_code.value.lower()`, but sometimes it does and sometimes it doesnt and in the operations db the `region_code` is upper case. in an ideal world we would get rid of this distinction (Recidiviz/recidiviz-data#31811) so as to not have this confusion but alas ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Recidiviz/recidiviz-data#29135 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [x] This pull request has a descriptive title and information useful to a reviewer - [x] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 9eef46d156e09fd82b44505936d149ab4fbe8fe2
…iod` (Recidiviz/recidiviz-data#33662) ## Description of the change Adding new raw data configs for period and sentences ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Closes #XXXX ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: a17183e82e78612a1b113de8d2437edd04776ecd
…abled (Recidiviz/recidiviz-data#33606) ## Description of the change we couldnt cancel secondary reimport when raw data import dag was enabled in just primary or secondary <img width="2056" alt="Screenshot 2024-09-23 at 4 56 30 PM" src="https://github.com/user-attachments/assets/fb5c6b1f-221f-4927-99e8-16a1e994bbcd"> ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Closes Recidiviz/recidiviz-data#33594 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [x] This pull request has a descriptive title and information useful to a reviewer - [x] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 1742bc6e966f2d35b7837cc13aabeee98a0f11ad
…it (Recidiviz/recidiviz-data#33508) ## Description of the change CA teams are organized by unit, but after checking with @not-a-doctor-stromberg - he let me know that the unit names are under `supervision_office_name` in the sessions attributes table. This updates the staff query to use the correct column when building supervisor rows. This has been run in the `jovergaag_units_` sandbox. We now have unit names for CA supervisors! @not-a-doctor-stromberg Do those units look correct? ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Closes Recidiviz/recidiviz-data#32176 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [ ] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: d1da97d37f723428396c9431ace6b045ea17313e
…tate-specific logic (Recidiviz/recidiviz-data#33683) ## Description of the change For the aggregated_metrics refactor, I want to be able to enforce that certain component views follow a certain structure. This PR introduces new helpers that I can use in unittests to validate new attributes about these views. 1) `check_query_selects_output_columns` - We want certain views to explicitly select the columns they need and no extra columns (will reduce materialization and query read cost!). This helper makes sure the top-level select in a query explicitly selects only the columns we need. Maybe someday we'll apply this check to all of our BQ views... 2) `check_view_has_no_state_specific_logic` - By the time we get to `aggregated_metrics` land, we should not be introducing state-specific logic. This check can be used to make sure a view does not reference state-specific views/tables and does not reference any specific state-code explicitly. ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Related to Recidiviz/recidiviz-data#32921 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [x] This pull request has a descriptive title and information useful to a reviewer - [x] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 9fd3924940e6a932a9fb66476a98c5720ad70d69
…Recidiviz/recidiviz-data#33037) ## Description of the change - Add criteria to exclude folks who have facility restrictions. - Add medical restrictions to side panel and to criteria - Added STATIC score into side panel We reduced the number of people eligible from 105 to 103, which is expected. This can be found in a sandbox under -`_hsalas`. ``` python -m recidiviz.tools.load_views_to_sandbox \ --project_id recidiviz-staging\ --sandbox_dataset_prefix hsalas manual \ --dataset_ids_to_load task_eligibility_criteria_us_nd,task_eligibility_spans_us_nd,task_eligibility,validation_views\ --update_descendants False ``` Closes Recidiviz/recidiviz-data#32161 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [ ] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [ ] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 59d4d924589cdcc57262c88ccbce320115f47310
… of eligible individuals (Recidiviz/recidiviz-data#33685) ## Description of the change Adjust the Marked Ineligible aggregated metrics to reflect only individuals that are also eligible for the opportunity. These aggregated metrics are used in the Automated Leadership reports. This change makes this metric more consistent with what is reflected in the [looker funnel metrics](https://github.com/Recidiviz/recidiviz-data/blob/main/recidiviz/tools/looker/aggregated_metrics/custom_workflows_metrics_configurations.py#L88-L103). ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Closes #XXXX ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [ ] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [ ] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant Co-authored-by: Michelle Orden <michelleorden@Michelles-MacBook-Pro.local> GitOrigin-RevId: 3a40f585daa5b15a421d6dc1735e82929d30805d
…idiviz/recidiviz-data#33680) ## Description of the change Changes SUPERVISION_SUPERVISION_TERMINATIONS to SUPERVISION_DISCHARGES in the Populations category under the Supervision sector. Changes SUPERVISION_SUPERVISION_VIOLATIONS to SUPERVISION_VIOLATIONS on the Operations and Dynamics category under the Supervision sector. Adds an underscore to PROSECUTION_CASES REFERRED in the Populations category under the Prosecution sector. This was a request for CSG for v2 agency dashboard as part of sprint 1 of the Agency Dashboard project. Tested locally! <img width="338" alt="Screenshot 2024-09-25 at 12 54 10 PM" src="https://github.com/user-attachments/assets/3b2a0f30-fca2-48cc-b187-9b16a884fe7b"> <img width="433" alt="Screenshot 2024-09-25 at 12 55 05 PM" src="https://github.com/user-attachments/asse <img width="346" alt="Screenshot 2024-09-25 at 12 53 30 PM" src="https://github.com/user-attachments/assets/341a1cbb-8748-4ac1-8ac6-7447d5314e98"> ts/183d2df3-4f3f-4da4-a933-49827d39104c"> ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [ ] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [ ] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 01fd1bc03145acfa9d10816ccc2eb4a511b8e080
…ecidiviz/recidiviz-data#33648) ## Description of the change I've added three new fields to the v2 published data response for dashboards: reporting_agency_id, reporting_agency_url, and reporting_agency_name. Currently, all three fields will return None since there is no frontend or mechanism yet to populate these values. I'm holding off on fully building out the backend for these fields until Brandon deprecates writing agency datapoints to the database later this week. This will avoid the need to manage writing metric config in two places. For now, the agreed-upon deliverable for CSG is to include these fields in the response as None, allowing the frontend team to familiarize themselves with them in the API response. ## Related issues Recidiviz/recidiviz-data#33024 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 09b7463b8fbcdf32b49be49c6f1df34a6cbefdd0
## Description of the change Last date parsing fix, following the example of Recidiviz/recidiviz-data#33666 and Recidiviz/recidiviz-data#33674. I ran `load_views_to_sandbox` with the `all` flag and it made it to `aggregated_metrics`, which gives me some confidence that this is the last one. ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Closes #XXXX ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [ ] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [x] This pull request has a descriptive title and information useful to a reviewer - [x] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 29f8155c36534aba45d7a86aa2330e13bbd02a9a
…iviz-data#33658) ## Description of the change updates `get_raw_data_branch_filter` and `get_raw_data_dag_enabled_state_and_instance_pairs` to actually call `is_raw_data_import_dag_enabled` and only build branches for enabled states ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Closes Recidiviz/recidiviz-data#33185 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [x] This pull request has a descriptive title and information useful to a reviewer - [x] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 0524fa7e1c3b5820808a5b3adfda3f137ed8ef80
…Recidiviz/recidiviz-data#33638) ## Description of the change makes pre-import normalization failures blocking by adding `filter_normalization_results_based_on_errors` function in the `regroup_and_verify_file_chunks` task ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Part of Recidiviz/recidiviz-data#33551 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: b0b11ebecb792d03497c6952f50a0a41c24dcb20
…Recidiviz/recidiviz-data#33692) ## Description of the change the following two things are true about `branching_by_key`: - when a branch operator skips a branch, airflow does not respect the trigger rules of the branch roots; rather, it just sets the branch roots as skipped and then lets the branch's trigger rules propagate that skipped status. the trigger rules of all all other tasks downstream of the branch root remain in use. - in pre-2.10 airflow (we currently use 2.7.3), you cannot have a task group be the root of a branch, so we have a small workaround us to do this by creating an empty task that serves as the branch root that will be upstream. the two of these things taken together means: if we a task that has an `ALL_DONE` trigger rule in a branch, it will always run, even if the branch is skipped. this is undesirable for a few reasons and has been a bit of a headache for raw data import dag, where we want certain behaviors to happen within an import branch irrespective of if upstream tasks succeeded (think releasing resource locks and cleaning up temporary resources). in this PR, i make three updates to `branching_by_key`: 1. i removed the `EmptyOperator` (task_id is like `{branch_key}_start` ) in favor of either using the provided `BaseOperator` directly, or using `TaskGroup.roots` for `branch_start`. i roughly followed the way that `TaskGroup._set_relatives` is implemented (i think what eventually gets called with `>>` operator) that uses `TaskGroup.roots` to set dependencies for upstream dependencies. this is also similar to how [airflow implemented branching for task groups in 2.10](apache/airflow#38883). 2. i used the provided `BaseOperator` or `TaskGroup.leaves` to relate to `branch_end`. i roughly followed the way that `TaskGroup._set_relatives` is implemented, which uses `TaskGroup.leaves` to set downstream dependencies. 3. i allowed each branch to take in either a task or a list of tasks this was one of a few approaches i tried to solve this problem; a few others that i liked less were: - use more `AirflowSkipExecptions` in tasks with `ALL_DONE`, see `recidiviz/airflow/dags/utils/task_utils.py` in https://github.com/Recidiviz/recidiviz-data/compare/ethanoro/if-skipped-show-skipped-1?expand=1 - replace branching with ``{branch_key}_start` being a `ShortCircuitOperator` since they can have task groups as downstream, see `recidiviz/airflow/dags/utils/branching_by_key.py` in https://github.com/Recidiviz/recidiviz-data/compare/ethanoro/if-skipped-show-skipped-2?expand=1 if this feels like a lot of work to solve a small problem, i agree! am very open to other ideas here! here's a screenshot of the new dataflow pipelines branching: <img width="1697" alt="Screenshot 2024-09-25 at 4 55 37 PM" src="https://github.com/user-attachments/assets/a4ec780c-fcea-401f-8ebc-f063dc4375e2"> screenshot of branching for raw data import dag: collapsed: <img width="583" alt="Screenshot 2024-09-25 at 5 57 25 PM" src="https://github.com/user-attachments/assets/743fa307-1051-4d30-a199-3a735fc4ecbb"> expanded: <img width="755" alt="Screenshot 2024-09-25 at 5 57 03 PM" src="https://github.com/user-attachments/assets/26d04cf7-5721-4921-9704-fbde4d7ab962"> and screenshot of visual groups: <img width="380" alt="Screenshot 2024-09-25 at 5 57 47 PM" src="https://github.com/user-attachments/assets/424c4d68-3af4-478d-ab3c-e0396ce37423"> ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Closes Recidiviz/recidiviz-data#33184 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [x] This pull request has a descriptive title and information useful to a reviewer - [x] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 81cb85d972bb48a52e1457c38725fa582f839410
…idiviz-data#33502) ## Description of the change I will rebase and add this to the new sentence sessions module info once Recidiviz/recidiviz-data#33406 is merged in! This PR contains the first of 4 views related to calculating projected dates for inferred sentence groups. This view aggregates sentence level projected dates by inferred sentence group. Recidiviz/recidiviz-data#33497 will aggregate group level projected dates by inferred sentence group. Recidiviz/recidiviz-data#33498 will create a validation between the sentence level and group level views. Recidiviz/recidiviz-data#33499 will aggregate all projected dates for inferred sentence groups. **The Plan** ```mermaid graph TD NormalizedStateSentenceLength --> aggregated_sentence_projected_dates NormalizedStateSentenceGroupLength --> aggregated_sentence_group_projected_dates aggregated_sentence_projected_dates --> validation aggregated_sentence_group_projected_dates --> validation aggregated_sentence_projected_dates --> sentence_inferred_group_projected_dates aggregated_sentence_group_projected_dates --> sentence_inferred_group_projected_dates ``` I think this will allow us to: - More easily understand projected dates when groups have suspended sentences - More easily check differences between state provided projected dates (if they exist) - More easily maintain all of these aggregations ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Closes Recidiviz/recidiviz-data#32945 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [ ] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [ ] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [x] This pull request has a descriptive title and information useful to a reviewer - [x] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: ed1f6098866abcc116d2246060adc1b144b05767
…gth (Recidiviz/recidiviz-data#33684) ## Description of the change For all impact report aggregated metrics, set the minimum date to two months ago. For all impact report aggregated metrics, change the `rolling_period_length` from 1 day to 7 days. This PR should address the issue that day-level metrics are causing a dramatic spike in view update runtime. In prod the run time spiked by an extra 2 hours due to these metrics. #### How I Tested I ran the following: `python -m recidiviz.tools.load_views_to_sandbox --sandbox_dataset_prefix michelle_sandbox manual --view_ids_to_load impact_reports.justice_involved_state_day_aggregated_metrics,analyst_data.person_spans --update_descendants False` and it produced ``` INFO:root:Prefixing all view datasets with [michelle_sandbox_]. INFO:root:Gathering all deployed view builders... INFO:root:Gathering views to load to sandbox... INFO:root:Building [4548] views... INFO:root:Will load the following views to the sandbox: - analyst_data.person_spans - impact_reports.justice_involved_state_day_aggregated_metrics INFO:root:Updating 2 views... INFO:root:Setting default table expiration for sandbox view load. New datasets created in this process will have a default table expiration of 24 hours. INFO:root:Building [2] views... /Users/michelleorden/.local/share/virtualenvs/recidiviz-data-LblS7iSE/lib/python3.11/site-packages/google/auth/_default.py:76: UserWarning: Your application has authenticated using end user credentials from Google Cloud SDK without a quota project. You might receive a "quota exceeded" or "API not enabled" error. See the following page for troubleshooting: https://cloud.google.com/docs/authentication/adc-troubleshooting/user-creds. warnings.warn(_CLOUD_SDK_CREDENTIALS_WARNING) INFO:root:Dataset [recidiviz-staging.michelle_sandbox_analyst_data] does not exist. Creating... INFO:root:Setting default table expiration to 86400000 milliseconds for dataset [recidiviz-staging.michelle_sandbox_analyst_data]. INFO:root:Dataset [recidiviz-staging.michelle_sandbox_impact_reports] does not exist. Creating... INFO:root:Setting default table expiration to 86400000 milliseconds for dataset [recidiviz-staging.michelle_sandbox_impact_reports]. INFO:root:Optimistically updating view [recidiviz-staging.michelle_sandbox_analyst_data.person_spans] INFO:root:Creating view [recidiviz-staging.michelle_sandbox_analyst_data.person_spans] as it was not found while attempting to update INFO:root:Materializing michelle_sandbox_analyst_data.person_spans into a table with address: michelle_sandbox_analyst_data.person_spans_materialized INFO:root:Creating table: michelle_sandbox_analyst_data.person_spans_materialized with query: SELECT * FROM `recidiviz-staging.michelle_sandbox_analyst_data.person_spans` INFO:root:Inserting into table [michelle_sandbox_analyst_data.person_spans_materialized] result of query: SELECT * FROM `recidiviz-staging.michelle_sandbox_analyst_data.person_spans` INFO:root:Optimistically updating view [recidiviz-staging.michelle_sandbox_impact_reports.justice_involved_state_day_aggregated_metrics] INFO:root:Creating view [recidiviz-staging.michelle_sandbox_impact_reports.justice_involved_state_day_aggregated_metrics] as it was not found while attempting to update INFO:root:Materializing michelle_sandbox_impact_reports.justice_involved_state_day_aggregated_metrics into a table with address: michelle_sandbox_impact_reports.justice_involved_state_day_aggregated_metrics_materialized INFO:root:Creating table: michelle_sandbox_impact_reports.justice_involved_state_day_aggregated_metrics_materialized with query: SELECT * FROM `recidiviz-staging.michelle_sandbox_impact_reports.justice_involved_state_day_aggregated_metrics` INFO:root:Inserting into table [michelle_sandbox_impact_reports.justice_involved_state_day_aggregated_metrics_materialized] result of query: SELECT * FROM `recidiviz-staging.michelle_sandbox_impact_reports.justice_involved_state_day_aggregated_metrics` INFO:root:### BQ DAG PROCESSING STATS ### Total processing time: 156.13 sec Nodes processed: 2 Average queue wait time: 0.0 seconds Max queue wait time: 0.0 seconds Top [25] most expensive nodes in DAG: 1) 118.93 sec: michelle_sandbox_impact_reports.justice_involved_state_day_aggregated_metrics 2) 37.20 sec: michelle_sandbox_analyst_data.person_spans Most expensive path [156.13 seconds total]: * 37.20 sec: michelle_sandbox_analyst_data.person_spans * 118.93 sec: michelle_sandbox_impact_reports.justice_involved_state_day_aggregated_metrics ``` ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Closes #XXXX ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [ ] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [x] This pull request has a descriptive title and information useful to a reviewer - [x] Potential security implications or infrastructural changes have been considered, if relevant --------- Co-authored-by: Michelle Orden <michelleorden@Michelles-MacBook-Pro.local> GitOrigin-RevId: 53956b1831c71f7964759fd1cf4808c075887257
…ata#33718) ## Description of the change What we call "incident severity" is in ND actually the severity of the sanction associated with an incident. There can be many incident severity levels per incarceration incident, which is causing entity merging errors in ingest (see [this failed job](https://console.cloud.google.com/dataflow/jobs/us-east1/2024-09-26_03_09_25-13577281294432618412?project=recidiviz-staging) for an example) This PR selectively associates the highest sanction severity level that was assigned as a result of each incarceration incident to store in the `incident_severity` field. The reason we use this information most often is to verify criteria such as "a person has not had a level 3 incident in the last year", so saving the highest level of severity will serve that purpose. It would be easier in this individual case to have severity hang off of `incarceration_incident_outcome`, because that is the way the severity is assigned in the state, but that does not seem to be the case for other states. Sandbox ingest pipeline succeeded [here](https://console.cloud.google.com/dataflow/jobs/us-west1/2024-09-26_07_23_12-12239994496108515441;graphView=0?project=recidiviz-staging&pageState=(%22dfTime%22:(%22l%22:%22dfJobMaxTime%22))) ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Closes #XXXX ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [ ] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [ ] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: d8deb976795c64b6942327e708953c4050ab7e85
…n ICE detainer (Recidiviz/recidiviz-data#33689) ## Description of the change Criteria: is US citizen or legal permanent resident without an ICE detainer. Uploaded it all to sandbox and it's looking good (under `hsalas`). Eligibility changed from 4259 to 2692 in `RELEASE_TO_TPR_REQUEST`. ``` python -m recidiviz.tools.load_views_to_sandbox \ --sandbox_dataset_prefix hsalas auto \ --load_up_to_datasets task_eligibility ``` ## Related issues Closes Recidiviz/recidiviz-data#33381 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [ ] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [ ] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: cabeebfd96d41738fded525734827c031fb0357d
…rvision compartments (Recidiviz/recidiviz-data#33698) ## Description of the change We recently got feedback from a TT that a client was not eligible for LSU yet since they needed to serve one year on active supervision following an OWI Recidiviz/recidiviz-dashboards#6375. They were showing us as eligible despite being in `TEMPORARY_CUSTODY` for most of the previous year. This pr updates the compartment levels listed as **inactive supervision** to include `TEMPORARY_CUSTODY`. Previous to the `TEMPORARY_CUSTODY` inference changes, these time periods were excluded based on `correctional_level = IN_CUSTODY` 13 (out of 1807) fewer clients are eligible for LSU after this change. ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Closes Recidiviz/recidiviz-dashboards#6375 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [ ] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: b7ee3859ec59a843fa8f2a3ababac3a46110aef7
…viz-data#33466) ## Description of the change - This PR creates an `experiments_metadata.experiment_assignments` view that pulls from a google backed sheet and a manually updated table. - Updates the README file so that the `gcloud auth login` command includes `--enable-gdrive-access --update-adc`. It was also auto-formatted as I saved it. - Migrates all mentions of `experiments` to `experiments_metadata`. - Adds a validation to check if `experiment_assignments_large` is in sync in prod vs staging - Deleted `experiment_asignments_materialized.yaml`, since it no longer had any references. - Fixed small bug in`update_source_table_yaml`. ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [ ] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [x] This pull request has a descriptive title and information useful to a reviewer - [x] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: ac624db50e47f90b0a9f7af44282481b0f1b4aa8
…33687) ## Description of the change Fixes an issue where creating two opportunity configs in rapid succession could cause them both to be marked active. I wasn't able to reproduce the database race locally, but [the Postgres docs](https://www.postgresql.org/docs/current/transaction-iso.html) indicate that the new isolation level setting should cause the transaction to fail if there's this kind of conflict. I didn't add any retry logic because these collisions are likely to occur only by accident. (It would also be possible to eliminate the separate UPDATE by defining the set of active configurations to be the ones with the highest id for a given featureVariant, and then filtering out the ones that have been explicitly deactivated. That would make querying more complicated and lock us into sequential ids.) On the frontend I also disabled the submit button during the submission process, which should prevent this issue in practice. ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Closes #XXXX ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [ ] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [x] This pull request has a descriptive title and information useful to a reviewer - [x] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: cef94155c0d48f55ae3e58c40eb852c8fb6b1d2d
…ciations when a panel is clicked on. (Recidiviz/recidiviz-data#33589) ## Description of the change Add backend endpoints to only fetch user-agency associations when a panel is clicked on. Advances Recidiviz/recidiviz-data#33622 These are the backend endpoints necessary to support this frontend change. Recidiviz/justice-counts#1519 Currently, the admin panel takes >40 seconds to load. This is because we are making backend api calls to fetch ALL users and ALL agencies and ALL of their many associations. So if we have N users and M agencies, instead of fetching N+M elements, we are fetching potentially N*M elements! This change introduces two limited endpoints for fetching all agency and user data WITHOUT the agency-user associations, which should greatly reduce the amount of data we need to load each time the admin panel is rendered. ## Tests Added tests for each endpoint. Tested this locally. Deployed this change to https://test---publisher-web-b47yvyxs3q-uc.a.run.app/ for more thorough testing on Staging. This play test link uses brandon/admin-panel-speedup-backend for the backend and brandon/admin-panel-speedup-frontend for the frontend. GitOrigin-RevId: ad382fe665475377104c1d979da2495112b02494
…/recidiviz-data#33728) ## Description of the change [US_ND] Added not enrolled in programming criteria for MIN ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Closes #XXXX ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [ ] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [ ] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 4d89bcb2e2b0dabcb793b1f651b8b32aada577f4
…viz/recidiviz-data#33697) ## Description of the change Add support for the addition/deletion/rename of a column in the raw file config `columns_at_datetime` to be used by `read_and_validate_column_headers` to get the column names to validate the raw file headers against in the import DAG ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Recidiviz/recidiviz-data#33695 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [x] This pull request has a descriptive title and information useful to a reviewer - [x] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 6dccc0051bec147f772d4baf905d655ace70e3f8
…types/admin (Recidiviz/recidiviz-data#33565) Bumps [@google-cloud/firestore](https://github.com/googleapis/nodejs-firestore) from 6.2.0 to 7.10.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/googleapis/nodejs-firestore/releases"><code>@google-cloud/firestore</code>'s releases</a>.</em></p> <blockquote> <h2>v7.10.0</h2> <h2><a href="https://github.com/googleapis/nodejs-firestore/compare/v7.9.0...v7.10.0">7.10.0</a> (2024-09-05)</h2> <h3>Features</h3> <ul> <li>Expose proto changes for the bulk delete api (<a href="https://github.com/googleapis/nodejs-firestore/commit/23ce89175ce315648ce9af3994cba0decc48ba47">23ce891</a>)</li> <li>Expose the proto changes to support FindNearest.distance_result_field parameter and the FindNearest.distance_threshold parameter (<a href="https://github.com/googleapis/nodejs-firestore/commit/23ce89175ce315648ce9af3994cba0decc48ba47">23ce891</a>)</li> <li>Return computed distance and set distance thresholds on VectorQueries (<a href="https://redirect.github.com/googleapis/nodejs-firestore/issues/2090">Recidiviz/recidiviz-data#2090</a>) (<a href="https://github.com/googleapis/nodejs-firestore/commit/b5ca84f076ca0668e90ca3fc7dd878f732ccd956">b5ca84f</a>)</li> </ul> <h2>v7.9.0</h2> <h2><a href="https://github.com/googleapis/nodejs-firestore/compare/v7.8.0...v7.9.0">7.9.0</a> (2024-06-25)</h2> <h3>Features</h3> <ul> <li>Update FirebaseFirestore.v1 and FirebaseFirestore.v1beta1 auto-gen types (<a href="https://github.com/googleapis/nodejs-firestore/commit/6732d4da3c5ea851dccb0515757fbfb521f21410">6732d4d</a>)</li> </ul> <h2>v7.8.0</h2> <h2><a href="https://github.com/googleapis/nodejs-firestore/compare/v7.7.0...v7.8.0">7.8.0</a> (2024-05-28)</h2> <h3>Features</h3> <ul> <li>Query profiling for VectorQuery (<a href="https://github.com/googleapis/nodejs-firestore/commit/d406f14612a4890e405913aadc75c7ee22993f2b">d406f14</a>)</li> <li>Update Nodejs generator to send API versions in headers for GAPICs (<a href="https://redirect.github.com/googleapis/nodejs-firestore/issues/2041">Recidiviz/recidiviz-data#2041</a>) (<a href="https://github.com/googleapis/nodejs-firestore/commit/6dbe4b0baac261f03f9032765b375938ce5e46d7">6dbe4b0</a>)</li> </ul> <h2>v7.7.0</h2> <h2><a href="https://github.com/googleapis/nodejs-firestore/compare/v7.6.0...v7.7.0">7.7.0</a> (2024-05-07)</h2> <h3>Features</h3> <ul> <li>Add several fields to manage state of database encryption update (<a href="https://github.com/googleapis/nodejs-firestore/commit/5811492357c7b66324839c02bcbf45a5b6d6d7e7">5811492</a>)</li> <li>Lazy-started transactions (<a href="https://redirect.github.com/googleapis/nodejs-firestore/issues/2017">Recidiviz/recidiviz-data#2017</a>) (<a href="https://github.com/googleapis/nodejs-firestore/commit/2c726a176407c45f519846052469e1bbbbc24750">2c726a1</a>)</li> </ul> <h3>Bug Fixes</h3> <ul> <li>Nonblocking rollback (<a href="https://redirect.github.com/googleapis/nodejs-firestore/issues/2039">Recidiviz/recidiviz-data#2039</a>) (<a href="https://github.com/googleapis/nodejs-firestore/commit/52099c8eb8ce8aba0ab5aee9f3dd4c4a59c2afd4">52099c8</a>)</li> <li>Upgrade the <code>google-gax</code> dependency version. (<a href="https://redirect.github.com/googleapis/nodejs-firestore/issues/2040">Recidiviz/recidiviz-data#2040</a>) (<a href="https://github.com/googleapis/nodejs-firestore/commit/0b9efa6d5a3d46ad2f084aef58c529e710c7f596">0b9efa6</a>)</li> </ul> <h2>v7.6.0</h2> <h2><a href="https://github.com/googleapis/nodejs-firestore/compare/v7.5.0...v7.6.0">7.6.0</a> (2024-04-02)</h2> <h3>Features</h3> <ul> <li>Vector Search (<a href="https://redirect.github.com/googleapis/nodejs-firestore/issues/2006">Recidiviz/recidiviz-data#2006</a>) (<a href="https://github.com/googleapis/nodejs-firestore/commit/e906b4260da11fe5a1c34ae5f68d9f5717a99dab">e906b42</a>)</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/googleapis/nodejs-firestore/blob/main/CHANGELOG.md"><code>@google-cloud/firestore</code>'s changelog</a>.</em></p> <blockquote> <h2><a href="https://github.com/googleapis/nodejs-firestore/compare/v7.9.0...v7.10.0">7.10.0</a> (2024-09-05)</h2> <h3>Features</h3> <ul> <li>Expose proto changes for the bulk delete api (<a href="https://github.com/googleapis/nodejs-firestore/commit/23ce89175ce315648ce9af3994cba0decc48ba47">23ce891</a>)</li> <li>Expose the proto changes to support FindNearest.distance_result_field parameter and the FindNearest.distance_threshold parameter (<a href="https://github.com/googleapis/nodejs-firestore/commit/23ce89175ce315648ce9af3994cba0decc48ba47">23ce891</a>)</li> <li>Return computed distance and set distance thresholds on VectorQueries (<a href="https://redirect.github.com/googleapis/nodejs-firestore/issues/2090">Recidiviz/recidiviz-data#2090</a>) (<a href="https://github.com/googleapis/nodejs-firestore/commit/b5ca84f076ca0668e90ca3fc7dd878f732ccd956">b5ca84f</a>)</li> </ul> <h2><a href="https://github.com/googleapis/nodejs-firestore/compare/v7.8.0...v7.9.0">7.9.0</a> (2024-06-25)</h2> <h3>Features</h3> <ul> <li>Update FirebaseFirestore.v1 and FirebaseFirestore.v1beta1 auto-gen types (<a href="https://github.com/googleapis/nodejs-firestore/commit/6732d4da3c5ea851dccb0515757fbfb521f21410">6732d4d</a>)</li> </ul> <h2><a href="https://github.com/googleapis/nodejs-firestore/compare/v7.7.0...v7.8.0">7.8.0</a> (2024-05-28)</h2> <h3>Features</h3> <ul> <li>Query profiling for VectorQuery (<a href="https://github.com/googleapis/nodejs-firestore/commit/d406f14612a4890e405913aadc75c7ee22993f2b">d406f14</a>)</li> <li>Update Nodejs generator to send API versions in headers for GAPICs (<a href="https://redirect.github.com/googleapis/nodejs-firestore/issues/2041">Recidiviz/recidiviz-data#2041</a>) (<a href="https://github.com/googleapis/nodejs-firestore/commit/6dbe4b0baac261f03f9032765b375938ce5e46d7">6dbe4b0</a>)</li> </ul> <h2><a href="https://github.com/googleapis/nodejs-firestore/compare/v7.6.0...v7.7.0">7.7.0</a> (2024-05-07)</h2> <h3>Features</h3> <ul> <li>Add several fields to manage state of database encryption update (<a href="https://github.com/googleapis/nodejs-firestore/commit/5811492357c7b66324839c02bcbf45a5b6d6d7e7">5811492</a>)</li> <li>Lazy-started transactions (<a href="https://redirect.github.com/googleapis/nodejs-firestore/issues/2017">Recidiviz/recidiviz-data#2017</a>) (<a href="https://github.com/googleapis/nodejs-firestore/commit/2c726a176407c45f519846052469e1bbbbc24750">2c726a1</a>)</li> </ul> <h3>Bug Fixes</h3> <ul> <li>Nonblocking rollback (<a href="https://redirect.github.com/googleapis/nodejs-firestore/issues/2039">Recidiviz/recidiviz-data#2039</a>) (<a href="https://github.com/googleapis/nodejs-firestore/commit/52099c8eb8ce8aba0ab5aee9f3dd4c4a59c2afd4">52099c8</a>)</li> <li>Upgrade the <code>google-gax</code> dependency version. (<a href="https://redirect.github.com/googleapis/nodejs-firestore/issues/2040">Recidiviz/recidiviz-data#2040</a>) (<a href="https://github.com/googleapis/nodejs-firestore/commit/0b9efa6d5a3d46ad2f084aef58c529e710c7f596">0b9efa6</a>)</li> </ul> <h2><a href="https://github.com/googleapis/nodejs-firestore/compare/v7.5.0...v7.6.0">7.6.0</a> (2024-04-02)</h2> <h3>Features</h3> <ul> <li>Vector Search (<a href="https://redirect.github.com/googleapis/nodejs-firestore/issues/2006">Recidiviz/recidiviz-data#2006</a>) (<a href="https://github.com/googleapis/nodejs-firestore/commit/e906b4260da11fe5a1c34ae5f68d9f5717a99dab">e906b42</a>)</li> </ul> <h2><a href="https://github.com/googleapis/nodejs-firestore/compare/v7.4.0...v7.5.0">7.5.0</a> (2024-03-25)</h2> <h3>Features</h3> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/googleapis/nodejs-firestore/commit/8118d37bf27b49d5e695bf18a9550a37ecc34ca2"><code>8118d37</code></a> chore(main): release 7.10.0 (<a href="https://redirect.github.com/googleapis/nodejs-firestore/issues/2168">Recidiviz/recidiviz-data#2168</a>)</li> <li><a href="https://github.com/googleapis/nodejs-firestore/commit/b5ca84f076ca0668e90ca3fc7dd878f732ccd956"><code>b5ca84f</code></a> feat: Return computed distance and set distance thresholds on VectorQueries (...</li> <li><a href="https://github.com/googleapis/nodejs-firestore/commit/4fcefdee40732bdf23eba592c82fb953f0f70051"><code>4fcefde</code></a> refactor: e2e tests using cloud trace v1 api. (<a href="https://redirect.github.com/googleapis/nodejs-firestore/issues/2093">Recidiviz/recidiviz-data#2093</a>)</li> <li><a href="https://github.com/googleapis/nodejs-firestore/commit/23ce89175ce315648ce9af3994cba0decc48ba47"><code>23ce891</code></a> feat: Expose the <code>FindNearest.distance_result_field</code> parameter (<a href="https://redirect.github.com/googleapis/nodejs-firestore/issues/2067">Recidiviz/recidiviz-data#2067</a>)</li> <li><a href="https://github.com/googleapis/nodejs-firestore/commit/e326e415ac7ae729053c8dba57f313a3de98d895"><code>e326e41</code></a> refactor: tracing using OpenTelemetry. (<a href="https://redirect.github.com/googleapis/nodejs-firestore/issues/2085">Recidiviz/recidiviz-data#2085</a>)</li> <li><a href="https://github.com/googleapis/nodejs-firestore/commit/f73e28b69be3ff9f870055af80683f12048549e8"><code>f73e28b</code></a> chore(main): release 7.9.0 (<a href="https://redirect.github.com/googleapis/nodejs-firestore/issues/2073">Recidiviz/recidiviz-data#2073</a>)</li> <li><a href="https://github.com/googleapis/nodejs-firestore/commit/3e91cf390a5163ec24124c09796d94e4c60f7433"><code>3e91cf3</code></a> chore: fix lint errors (<a href="https://redirect.github.com/googleapis/nodejs-firestore/issues/2074">Recidiviz/recidiviz-data#2074</a>)</li> <li><a href="https://github.com/googleapis/nodejs-firestore/commit/6732d4da3c5ea851dccb0515757fbfb521f21410"><code>6732d4d</code></a> build: update gapic generator to allow individual location mixin generation (...</li> <li><a href="https://github.com/googleapis/nodejs-firestore/commit/672e6d81792abcd595d19c642941b06da129c9b0"><code>672e6d8</code></a> build: Running the license script for files in the types folder (<a href="https://redirect.github.com/googleapis/nodejs-firestore/issues/2066">Recidiviz/recidiviz-data#2066</a>)</li> <li><a href="https://github.com/googleapis/nodejs-firestore/commit/337641ab3a2f0b5a5d2fe952d5b09177440095e1"><code>337641a</code></a> Build: Pin the protobuf library to v26.1 (<a href="https://redirect.github.com/googleapis/nodejs-firestore/issues/2064">Recidiviz/recidiviz-data#2064</a>)</li> <li>Additional commits viewable in <a href="https://github.com/googleapis/nodejs-firestore/compare/v6.2.0...v7.10.0">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will 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 version` will 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 dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> GitOrigin-RevId: 536c9c6ba4b7ada7c495e40936b59d701ac522df
…z/recidiviz-data#33736) Bumps [rollup](https://github.com/rollup/rollup) from 2.79.1 to 2.79.2. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/rollup/rollup/blob/master/CHANGELOG.md">rollup's changelog</a>.</em></p> <blockquote> <h1>rollup changelog</h1> <h2>4.22.4</h2> <p><em>2024-09-21</em></p> <h3>Bug Fixes</h3> <ul> <li>Fix a vulnerability in generated code that affects IIFE, UMD and CJS bundles when run in a browser context (<a href="https://redirect.github.com/rollup/rollup/issues/5671">Recidiviz/recidiviz-data#5671</a>)</li> </ul> <h3>Pull Requests</h3> <ul> <li><a href="https://redirect.github.com/rollup/rollup/pull/5670">Recidiviz/recidiviz-data#5670</a>: refactor: Use object.prototype to check for reserved properties (<a href="https://github.com/YuHyeonWook"><code>@YuHyeonWook</code></a>)</li> <li><a href="https://redirect.github.com/rollup/rollup/pull/5671">Recidiviz/recidiviz-data#5671</a>: Fix DOM Clobbering CVE (<a href="https://github.com/lukastaegert"><code>@lukastaegert</code></a>)</li> </ul> <h2>4.22.3</h2> <p><em>2024-09-21</em></p> <h3>Bug Fixes</h3> <ul> <li>Ensure that mutations in modules without side effects are observed while properly handling transitive dependencies (<a href="https://redirect.github.com/rollup/rollup/issues/5669">Recidiviz/recidiviz-data#5669</a>)</li> </ul> <h3>Pull Requests</h3> <ul> <li><a href="https://redirect.github.com/rollup/rollup/pull/5669">Recidiviz/recidiviz-data#5669</a>: Ensure impure dependencies of pure modules are added (<a href="https://github.com/lukastaegert"><code>@lukastaegert</code></a>)</li> </ul> <h2>4.22.2</h2> <p><em>2024-09-20</em></p> <h3>Bug Fixes</h3> <ul> <li>Revert fix for side effect free modules until other issues are investigated (<a href="https://redirect.github.com/rollup/rollup/issues/5667">Recidiviz/recidiviz-data#5667</a>)</li> </ul> <h3>Pull Requests</h3> <ul> <li><a href="https://redirect.github.com/rollup/rollup/pull/5667">Recidiviz/recidiviz-data#5667</a>: Partially revert <a href="https://redirect.github.com/rollup/rollup/issues/5658">Recidiviz/recidiviz-data#5658</a> and re-apply <a href="https://redirect.github.com/rollup/rollup/issues/5644">Recidiviz/recidiviz-data#5644</a> (<a href="https://github.com/lukastaegert"><code>@lukastaegert</code></a>)</li> </ul> <h2>4.22.1</h2> <p><em>2024-09-20</em></p> <h3>Bug Fixes</h3> <ul> <li>Revert <a href="https://redirect.github.com/rollup/rollup/issues/5644">Recidiviz/recidiviz-data#5644</a> "stable chunk hashes" while issues are being investigated</li> </ul> <h3>Pull Requests</h3> <ul> <li><a href="https://redirect.github.com/rollup/rollup/pull/5663">Recidiviz/recidiviz-data#5663</a>: chore(deps): update dependency inquirer to v11 (<a href="https://github.com/renovate"><code>@renovate</code></a>[bot], <a href="https://github.com/lukastaegert"><code>@lukastaegert</code></a>)</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/rollup/rollup/commit/c9bd03d12e96c46122a0372d3bbe9b468cee57da"><code>c9bd03d</code></a> 2.79.2</li> <li><a href="https://github.com/rollup/rollup/commit/48aef33cf2f2a6dfb175afb3bcd6a977c81f1d5c"><code>48aef33</code></a> fix: resolve DOM Clobbering CVE-2024-43788 (backport to v2) (<a href="https://redirect.github.com/rollup/rollup/issues/5677">Recidiviz/recidiviz-data#5677</a>)</li> <li>See full diff in <a href="https://github.com/rollup/rollup/compare/v2.79.1...v2.79.2">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will 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 version` will 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 dependency` will 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](https://github.com/Recidiviz/recidiviz-data/network/alerts). </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> GitOrigin-RevId: f78061f41771be5b344aec22fc14e9fcf5a7db40
Bumps [eslint-import-resolver-typescript](https://github.com/import-js/eslint-import-resolver-typescript) from 2.7.1 to 3.6.3. - [Release notes](https://github.com/import-js/eslint-import-resolver-typescript/releases) - [Changelog](https://github.com/import-js/eslint-import-resolver-typescript/blob/master/CHANGELOG.md) - [Commits](import-js/eslint-import-resolver-typescript@v2.7.1...v3.6.3) --- updated-dependencies: - dependency-name: eslint-import-resolver-typescript dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/frontends/admin-panel/eslint-import-resolver-typescript-3.6.3
branch
from
faa7263 to
67c7938
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps eslint-import-resolver-typescript from 2.7.1 to 3.6.3.
Release notes
Sourced from eslint-import-resolver-typescript's releases.
... (truncated)
Changelog
Sourced from eslint-import-resolver-typescript's changelog.
... (truncated)
Commits
3dfad60chore(deps): update dependency node to v18.20.4 (#309)47561fbchore(deps): update dependency@changesets/clito ^2.27.7 (#308)c9b5626chore: release eslint-import-resolver-typescript (#302)f8d7b82fix(#303): use@nolyfill/is-core-module(#305)a4c6c78fix: ignore bun built-in modules (#288)79148f4chore: release eslint-import-resolver-typescript (#301)ff3d3c6chore(deps): removeis-core-moduledependency (#295)10f9b17Allow either import or import-x plugin as a peer dependency (#294)b777b44ci(workflows/ci): setup node before enabling corepack (#300)4f9db59chore(deps): update dependency node to v18.20.3 (#297)You can trigger a rebase of this PR 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 show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@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)