profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/Ptival/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Valentin Robert Ptival Galois, Inc. San Diego, CA http://ptival.github.io Programming Languages and Software Verification

GaloisInc/grift 42

Galois RISC-V ISA Formal Tools

nikivazou/verified_string_matching 6

Verified Parallelized Version of String Mathcing

GaloisInc/bv-sized 5

A bitvector datatype that is parameterized by the vector width.

Ptival/00-lambda 2

Starter code for 00-lambda

GaloisInc/bv-sized-float 1

Floating-point operations for bv-sized

13Kill/EnScredPoto 0

Ceci n'est pas la v2 de ProxiBanque.

issue commentge-high-assurance/RACK

SPARQLGraph - maximum stack size exceeded / circular graphs

I've implemented a partial fix. SPARQLgraph now makes it very difficult for you to create a circular graph. Further improvements are possible, but let's see whether this one gets us what we need.

Robert-Adelard

comment created time in 26 minutes

fork slindley/module-linking

Proposal for allowing modules to define, import and export modules and instances

fork in 5 hours

delete branch Ptival/PeaCoq

delete branch : dependabot/npm_and_yarn/web/npm-check-updates-11.6.0

delete time in 9 hours

PR closed Ptival/PeaCoq

Bump npm-check-updates from 2.14.2 to 11.6.0 in /web dependencies

Bumps npm-check-updates from 2.14.2 to 11.6.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/raineorshine/npm-check-updates/releases">npm-check-updates's releases</a>.</em></p> <blockquote> <h2>v11.5.0</h2> <h2>Minor</h2> <p><code>npm-check-updates</code> will now auto-detect yarn and apply <code>--packageManager yarn</code> when <code>yarn.lock</code> is present and <code>package-lock.json</code> is <strong>not</strong> present. You can override this by explicitly setting <code>--packageManager npm</code>. It will print "Using yarn" when the auto-detection is triggered.</p> <h2>v11.4.0</h2> <h2>Minor</h2> <ul> <li>Use <code>--peer</code> to check peer dependencies of installed packages and filter updates to compatible versions. <ul> <li>791aa22 Respect peer dependencies (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/869">#869</a>)</li> </ul> </li> <li>Bump <code>mem</code> (minor)</li> </ul> <h2>Patch</h2> <ul> <li>696168b <code>--deep</code>: Fix Windows path</li> <li>Bump dependencies (patch)</li> </ul> <h2>v11.2.0</h2> <p>Wildcards and globs can now be used in filters without having to use regex:</p> <pre lang="sh"><code>ncu react-* # upgrade packages that start with "react-" ncu !commander # upgrade everything except "commander" </code></pre> <p>Since special characters are not allowed in package names, this change <em>shouldn't</em> break anything, but please let me know if a filter that was working before <code>v11.2.0</code> is not now!</p> <h3>Commits</h3> <p>ee27448 Add filter support for wildcards and glob expressions. Fixes <a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/219">#219</a>.</p> <h2>v11.0.0</h2> <h3>Breaking</h3> <ul> <li><code>--packageFile</code> - Now interprets its argument as a glob pattern. It is possible that a previously supplied argument may be interepreted differently now (though I'm not aware of specific instances). Due to our conservative release policy we are releasing as a major version upgrade and allowing developers to assess for themselves.</li> </ul> <h3>Features</h3> <ul> <li><code>--deep</code> - Run recursively in current working directory. Alias of <code>--packageFile '/package.json'</code>.</li> </ul> <p>See: <a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/785">#785</a></p> <p><a href="https://github.com/raineorshine/npm-check-updates/compare/v10.3.1...v11.0.0">https://github.com/raineorshine/npm-check-updates/compare/v10.3.1...v11.0.0</a></p> <h2>v10.0.0</h2> <h2>[10.0.0] - 2020-11-08</h2> <h3>Breaking</h3> <ul> <li>Specifiying both the <code>--filter</code> option and argument filters will now throw an error. Use one or the other. Previously the arguments would override the <code>--filter</code> option, which made for a confusing result when accidentally not quoting the option in the shell. This change is only breaking for those who are relying on the incorrect behavior of argument filters overriding <code>--filter</code>.</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/raineorshine/npm-check-updates/blob/main/CHANGELOG.md">npm-check-updates's changelog</a>.</em></p> <blockquote> <h1>Changelog</h1> <p>This file documents all <strong>major version</strong> releases. For other releases, you'll have to read the <a href="https://github.com/raineorshine/npm-check-updates/">commit history</a>.</p> <h2>[11.0.0] - 2021-01-20</h2> <h3>Breaking</h3> <ul> <li><code>--packageFile</code> - Now interprets its argument as a glob pattern. It is possible that a previously supplied argument may be interepreted differently now (though I'm not aware of specific instances). Due to our conservative release policy we are releasing as a major version upgrade and allowing developers to assess for themselves.</li> </ul> <h3>Features</h3> <ul> <li><code>--deep</code> - Run recursively in current working directory. Alias of <code>--packageFile '/package.json'</code>.</li> </ul> <p>See: <a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/785">#785</a></p> <p><a href="https://github.com/raineorshine/npm-check-updates/compare/v10.3.1...v11.0.0">https://github.com/raineorshine/npm-check-updates/compare/v10.3.1...v11.0.0</a></p> <h2>[10.0.0] - 2020-11-08</h2> <h3>Breaking</h3> <ul> <li>Specifiying both the <code>--filter</code> option and argument filters will now throw an error. Use one or the other. Previously the arguments would override the <code>--filter</code> option, which made for a confusing result when accidentally not quoting the option in the shell. This change is only breaking for those who are relying on the incorrect behavior of argument filters overriding <code>--filter</code>.</li> </ul> <p>See: <a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/759#issuecomment-723587297">#759</a></p> <p><a href="https://github.com/raineorshine/npm-check-updates/compare/v9.2.4...v10.0.0">https://github.com/raineorshine/npm-check-updates/compare/v9.2.4...v10.0.0</a></p> <h2>[9.0.0] - 2020-09-10</h2> <h3>Breaking</h3> <ul> <li>Versions marked as <code>deprecated</code> in npm are now ignored by default. If the latest version is deprecated, the next highest non-deprecated version will be suggested. Use <code>--deprecated</code> to include deprecated versions (old behavior).</li> </ul> <p><a href="https://github.com/raineorshine/npm-check-updates/compare/v8.1.1...v9.0.0">https://github.com/raineorshine/npm-check-updates/compare/v8.1.1...v9.0.0</a></p> <h2>[8.0.0] - 2020-08-29</h2> <h3>Breaking</h3> <ul> <li><code>--semverLevel major</code> is now <code>--target minor</code>. <code>--semverLevel minor</code> is now <code>--target patch</code>. This change was made to provide more intuitive semantics for <code>--semverLevel</code> (now <code>--target</code>). Most people assumed it meant the inclusive upper bound, so now it reflects that. <a href="https://github.com/raineorshine/npm-check-updates/commits/a2111f4c2">a2111f4c2</a></li> <li>Programmatic usage: <code>run</code> now defaults to <code>silent: true</code> instead of <code>loglevel: 'silent</code>, unless <code>loglevel</code> is explicitly specified. If you overrode <code>silent</code> or <code>loglevel</code>, this may affect the logging behavior. <a href="https://github.com/raineorshine/npm-check-updates/commits/423e024">423e024</a></li> </ul> <h3>Deprecated</h3> <p>Options that controlled the target version (upper bound) of upgrades have been consolidated under <code>--target</code>. The old options are aliased with a deprecation warning and will be removed in the next major version. No functionality has been removed.</p> <ul> <li><code>--greatest</code>: Renamed to <code>--target greatest</code></li> <li><code>--newest</code>: Renamed to <code>--target newest</code></li> <li><code>--semverLevel</code>: Renamed to <code>--target</code></li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/dfcbe8e1b73b3e24d07fe3d46e4958fae5029ebb"><code>dfcbe8e</code></a> 11.6.0</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/f43e09561a70aa53bb0a04e2cc410f41a0bbfdc2"><code>f43e095</code></a> Bump dependencies</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/18358a4d08a5f2d532600cfc5e6bf24e0f30af9c"><code>18358a4</code></a> feat: --mergeConfig option for --deep to inherit config settings (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/897">#897</a>)</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/7f538ed3c9b3e9f028058ad118a8dd4f7eb83cae"><code>7f538ed</code></a> 11.5.13</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/a1ad7c991859e6fbdf0557df407a792bf57e2eb8"><code>a1ad7c9</code></a> getCurrentDependencies: Guard comparison of duplicates (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/893">#893</a>).</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/486535fd605ceb8cf402029dde784bb404e36c0c"><code>486535f</code></a> 11.5.12</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/d864ad78300d645009c3ee05b2379bf089c60788"><code>d864ad7</code></a> Bump dependencies</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/9faf86e90d0560d8976c96f332761f156302b9ed"><code>9faf86e</code></a> Only print upgradedPeerDependencies if --peer is set.</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/74e959fe1fe4224c4d2f041cc16181a54d0cab24"><code>74e959f</code></a> test/doctor/options: Add required license field to package.json.</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/e8eb22b38d5eb858ff3fb770680cdc2ac0c2460a"><code>e8eb22b</code></a> Use lowest version when a dependency is in more than one section (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/892">#892</a>).</li> <li>Additional commits viewable in <a href="https://github.com/raineorshine/npm-check-updates/compare/v2.14.2...v11.6.0">compare view</a></li> </ul> </details> <br />

Dependabot compatibility score

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.


<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 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)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

</details>

+1 -1

1 comment

1 changed file

dependabot-preview[bot]

pr closed time in 9 hours

pull request commentPtival/PeaCoq

Bump npm-check-updates from 2.14.2 to 11.6.0 in /web

Superseded by #99.

dependabot-preview[bot]

comment created time in 9 hours

PR opened Ptival/PeaCoq

Bump npm-check-updates from 2.14.2 to 11.7.1 in /web

Bumps npm-check-updates from 2.14.2 to 11.7.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/raineorshine/npm-check-updates/releases">npm-check-updates's releases</a>.</em></p> <blockquote> <h2>v11.5.0</h2> <h2>Minor</h2> <p><code>npm-check-updates</code> will now auto-detect yarn and apply <code>--packageManager yarn</code> when <code>yarn.lock</code> is present and <code>package-lock.json</code> is <strong>not</strong> present. You can override this by explicitly setting <code>--packageManager npm</code>. It will print "Using yarn" when the auto-detection is triggered.</p> <h2>v11.4.0</h2> <h2>Minor</h2> <ul> <li>Use <code>--peer</code> to check peer dependencies of installed packages and filter updates to compatible versions. <ul> <li>791aa22 Respect peer dependencies (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/869">#869</a>)</li> </ul> </li> <li>Bump <code>mem</code> (minor)</li> </ul> <h2>Patch</h2> <ul> <li>696168b <code>--deep</code>: Fix Windows path</li> <li>Bump dependencies (patch)</li> </ul> <h2>v11.2.0</h2> <p>Wildcards and globs can now be used in filters without having to use regex:</p> <pre lang="sh"><code>ncu react-* # upgrade packages that start with "react-" ncu !commander # upgrade everything except "commander" </code></pre> <p>Since special characters are not allowed in package names, this change <em>shouldn't</em> break anything, but please let me know if a filter that was working before <code>v11.2.0</code> is not now!</p> <h3>Commits</h3> <p>ee27448 Add filter support for wildcards and glob expressions. Fixes <a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/219">#219</a>.</p> <h2>v11.0.0</h2> <h3>Breaking</h3> <ul> <li><code>--packageFile</code> - Now interprets its argument as a glob pattern. It is possible that a previously supplied argument may be interepreted differently now (though I'm not aware of specific instances). Due to our conservative release policy we are releasing as a major version upgrade and allowing developers to assess for themselves.</li> </ul> <h3>Features</h3> <ul> <li><code>--deep</code> - Run recursively in current working directory. Alias of <code>--packageFile '/package.json'</code>.</li> </ul> <p>See: <a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/785">#785</a></p> <p><a href="https://github.com/raineorshine/npm-check-updates/compare/v10.3.1...v11.0.0">https://github.com/raineorshine/npm-check-updates/compare/v10.3.1...v11.0.0</a></p> <h2>v10.0.0</h2> <h2>[10.0.0] - 2020-11-08</h2> <h3>Breaking</h3> <ul> <li>Specifiying both the <code>--filter</code> option and argument filters will now throw an error. Use one or the other. Previously the arguments would override the <code>--filter</code> option, which made for a confusing result when accidentally not quoting the option in the shell. This change is only breaking for those who are relying on the incorrect behavior of argument filters overriding <code>--filter</code>.</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/raineorshine/npm-check-updates/blob/main/CHANGELOG.md">npm-check-updates's changelog</a>.</em></p> <blockquote> <h1>Changelog</h1> <p>This file documents all <strong>major version</strong> releases. For other releases, you'll have to read the <a href="https://github.com/raineorshine/npm-check-updates/">commit history</a>.</p> <h2>[11.0.0] - 2021-01-20</h2> <h3>Breaking</h3> <ul> <li><code>--packageFile</code> - Now interprets its argument as a glob pattern. It is possible that a previously supplied argument may be interepreted differently now (though I'm not aware of specific instances). Due to our conservative release policy we are releasing as a major version upgrade and allowing developers to assess for themselves.</li> </ul> <h3>Features</h3> <ul> <li><code>--deep</code> - Run recursively in current working directory. Alias of <code>--packageFile '/package.json'</code>.</li> </ul> <p>See: <a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/785">#785</a></p> <p><a href="https://github.com/raineorshine/npm-check-updates/compare/v10.3.1...v11.0.0">https://github.com/raineorshine/npm-check-updates/compare/v10.3.1...v11.0.0</a></p> <h2>[10.0.0] - 2020-11-08</h2> <h3>Breaking</h3> <ul> <li>Specifiying both the <code>--filter</code> option and argument filters will now throw an error. Use one or the other. Previously the arguments would override the <code>--filter</code> option, which made for a confusing result when accidentally not quoting the option in the shell. This change is only breaking for those who are relying on the incorrect behavior of argument filters overriding <code>--filter</code>.</li> </ul> <p>See: <a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/759#issuecomment-723587297">#759</a></p> <p><a href="https://github.com/raineorshine/npm-check-updates/compare/v9.2.4...v10.0.0">https://github.com/raineorshine/npm-check-updates/compare/v9.2.4...v10.0.0</a></p> <h2>[9.0.0] - 2020-09-10</h2> <h3>Breaking</h3> <ul> <li>Versions marked as <code>deprecated</code> in npm are now ignored by default. If the latest version is deprecated, the next highest non-deprecated version will be suggested. Use <code>--deprecated</code> to include deprecated versions (old behavior).</li> </ul> <p><a href="https://github.com/raineorshine/npm-check-updates/compare/v8.1.1...v9.0.0">https://github.com/raineorshine/npm-check-updates/compare/v8.1.1...v9.0.0</a></p> <h2>[8.0.0] - 2020-08-29</h2> <h3>Breaking</h3> <ul> <li><code>--semverLevel major</code> is now <code>--target minor</code>. <code>--semverLevel minor</code> is now <code>--target patch</code>. This change was made to provide more intuitive semantics for <code>--semverLevel</code> (now <code>--target</code>). Most people assumed it meant the inclusive upper bound, so now it reflects that. <a href="https://github.com/raineorshine/npm-check-updates/commits/a2111f4c2">a2111f4c2</a></li> <li>Programmatic usage: <code>run</code> now defaults to <code>silent: true</code> instead of <code>loglevel: 'silent</code>, unless <code>loglevel</code> is explicitly specified. If you overrode <code>silent</code> or <code>loglevel</code>, this may affect the logging behavior. <a href="https://github.com/raineorshine/npm-check-updates/commits/423e024">423e024</a></li> </ul> <h3>Deprecated</h3> <p>Options that controlled the target version (upper bound) of upgrades have been consolidated under <code>--target</code>. The old options are aliased with a deprecation warning and will be removed in the next major version. No functionality has been removed.</p> <ul> <li><code>--greatest</code>: Renamed to <code>--target greatest</code></li> <li><code>--newest</code>: Renamed to <code>--target newest</code></li> <li><code>--semverLevel</code>: Renamed to <code>--target</code></li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/857b825f0f57f3d23ca1c53e2a8f12b5ec8b4976"><code>857b825</code></a> 11.7.1</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/be8bacd7375df19a97daa62646e2477fb1f735da"><code>be8bacd</code></a> Revert mocha which does not support nodejs v10.</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/6ab8c08b39f6b25eb3b67c10b2e19893f52f0a98"><code>6ab8c08</code></a> 11.7.0</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/d777e7d3149e9c35f4a4b77a7c4479b53b24508a"><code>d777e7d</code></a> Bump dependencies</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/07d5060cfd9ee81941b387ce27fa52f5fca59d0b"><code>07d5060</code></a> packageData: Accept object type (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/908">#908</a>)</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/a7a03d9706f832055b4ce7028a63c6e11713782a"><code>a7a03d9</code></a> build(deps-dev): bump eslint from 7.26.0 to 7.27.0 (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/902">#902</a>)</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/7b6dc9e6395257b8fa78f17945e08bfc07faeeca"><code>7b6dc9e</code></a> build(deps-dev): bump eslint-config-standard from 16.0.2 to 16.0.3 (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/901">#901</a>)</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/69fee55b3ddab8e1260a86a59eaac0b905ae135f"><code>69fee55</code></a> build(deps-dev): bump eslint-plugin-import from 2.23.0 to 2.23.4 (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/900">#900</a>)</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/dfcbe8e1b73b3e24d07fe3d46e4958fae5029ebb"><code>dfcbe8e</code></a> 11.6.0</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/f43e09561a70aa53bb0a04e2cc410f41a0bbfdc2"><code>f43e095</code></a> Bump dependencies</li> <li>Additional commits viewable in <a href="https://github.com/raineorshine/npm-check-updates/compare/v2.14.2...v11.7.1">compare view</a></li> </ul> </details> <br />

Dependabot compatibility score

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.


<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 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)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

</details>

+1 -1

0 comment

1 changed file

pr created time in 9 hours

delete branch Ptival/PeaCoq

delete branch : dependabot/npm_and_yarn/web/mathjax-3.1.4

delete time in 10 hours

PR closed Ptival/PeaCoq

Bump mathjax from 2.7.9 to 3.1.4 in /web dependencies

Bumps mathjax from 2.7.9 to 3.1.4. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/mathjax/MathJax/releases">mathjax's releases</a>.</em></p> <blockquote> <h2>MathJax v3.1.4</h2> <p>This is a hot fix release to fix two problems with the recent 3.1.3 version. See the <a href="https://github.com/mathjax/MathJax-src/releases/tag/3.1.4">release notes</a> for details.</p> <h2>MathJax 3.1.3</h2> <p>This is a bug fix release that resolves more than 70 issues, and updates a number of modules on which MathJax relies. See the <a href="https://github.com/mathjax/MathJax-src/releases/tag/3.1.3">release notes</a> for details.</p> <h2>MathJax v3.1.2</h2> <p>Hot fix to correct regression introduced in v3.1.1 that caused control sequences followed by spaces to not be recognized.</p> <h2>MathJax v3.1.1</h2> <p>This is a bug fix release to address issues that arose from the recent 3.1.0 release. See the <a href="https://github.com/mathjax/MathJax-src/releases/tag/3.1.0">release notes</a> for details.</p> <h2>MathJax v3.1.0</h2> <p>This is a feature release that includes a number of API improvements, new extensions, and updates to the assistive tools, as described in the <a href="https://github.com/mathjax/MathJax-src/releases/tag/3.1.0">release notes</a>.</p> <h2>MathJax v3.0.5</h2> <p>This is a hot fix release to resolve an important issue with horizontal stretchy characters (e.g., <code>\overline</code> and <code>\overrightarrow</code>) in CommonHTML output that was introduced in the recent version 3.0.4 release.</p> <h2>MathJax v3.0.4</h2> <p>This is a bug-fix release. See the <a href="https://github.com/mathjax/MathJax-src/releases/tag/3.0.4">release notes</a> for details.</p> <p>Note that version 3.0.2 and 3.0.3 had problems with their <code>npm</code> deployment (some files where missing from the package), so were removed. This is the next actual version after 3.0.1</p> <h2>MathJax v3.0.1</h2> <p>This is a bug-fix release. See the <a href="https://github.com/mathjax/MathJax-src/releases/tag/3.0.1">release notes</a> for details.</p> <h2>MathJax v3.0.0</h2> <p>After over two years of development, the MathJax team is pleased to announce the official release of MathJax 3.0.0!</p> <p>This version is a complete rewrite of MathJax from the ground up using modern programming techniques, including Typescript, ES6 modules, Promises, and more.</p> <p>Please see the <a href="http://docs.mathjax.org/en/v3.0-latest/upgrading/whats-new-3.0.html">What's New in v3.0</a> section of the documentation for details about the new version 3.0.0.</p> <p>Please see the <a href="http://docs.mathjax.org/en/v3.0-latest/upgrading/v2.html">Upgrading from v2</a> instructions for details about what is and isn't in version 3, and how to upgrade your site from version 2. Note in particular that there is a <a href="https://mathjax.github.io/MathJax-demos-web/convert-configuration/convert-configuration.html">configuration converter</a> that can help you move from version 2 to version 3.</p> <p>See the <a href="http://docs.mathjax.org/">documentation</a> for details about how to use MathJax.</p> <p>See the <a href="https://github.com/mathjax/MathJax-src">MathJax Source Repository</a> for the source code for versions 3.</p> <p>There are two repositories that contain examples of using MathJax, one for web pages, and one for use with node on a server:</p> <ul> <li><a href="https://github.com/mathjax/MathJax-demos-web#mathjax-demos-web">MathJax Web Examples</a></li> <li><a href="https://github.com/mathjax/MathJax-demos-node#mathjax-demos-node">MathJax Node Examples</a></li> </ul> <p>Please use the <a href="https://github.com/mathjax/MathJax/issues">MathJax Issue Tracker</a> to report problems in version 3 of MathJax.</p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/mathjax/MathJax/commit/be11806df1ae075508e33500c990497062ef3c5a"><code>be11806</code></a> Merge branch 'develop'</li> <li><a href="https://github.com/mathjax/MathJax/commit/e0575afdda9d94b9ba1d9045ebbce15b4476c465"><code>e0575af</code></a> Update to version 3.1.4</li> <li><a href="https://github.com/mathjax/MathJax/commit/af2bacdb2a38245a4a68c84bf7a5fb2e6da35426"><code>af2bacd</code></a> Merge branch 'develop'</li> <li><a href="https://github.com/mathjax/MathJax/commit/de316b931638887c26525aad4ac55acaca7093cd"><code>de316b9</code></a> Update package.json and files to v3.1.3</li> <li><a href="https://github.com/mathjax/MathJax/commit/ec5c85494ad89f5e60c727c0b5c8534a966be09d"><code>ec5c854</code></a> Merge branch 'update-shields' into develop</li> <li><a href="https://github.com/mathjax/MathJax/commit/10160614b6b5844f231c91423533fbddd28d55cb"><code>1016061</code></a> Merge branch 'update-shields'</li> <li><a href="https://github.com/mathjax/MathJax/commit/117409ac26dbabf70b9915dc49d9623e0000fde5"><code>117409a</code></a> Add shields for rank and downloads</li> <li><a href="https://github.com/mathjax/MathJax/commit/1335230503dddfeb0e07687308a55795d9c005e8"><code>1335230</code></a> Update issue templates</li> <li><a href="https://github.com/mathjax/MathJax/commit/c8292351190ce249f7143f224dbe7a190c8228fe"><code>c829235</code></a> Update to version 3.1.2</li> <li><a href="https://github.com/mathjax/MathJax/commit/3ee0287eb1d6101aef8ec5af1e06042a656a91fc"><code>3ee0287</code></a> Update to version 3.1.1</li> <li>Additional commits viewable in <a href="https://github.com/mathjax/MathJax/compare/2.7.9...3.1.4">compare view</a></li> </ul> </details> <br />

Dependabot compatibility score

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.


<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 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)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

</details>

+1 -1

1 comment

1 changed file

dependabot-preview[bot]

pr closed time in 10 hours

pull request commentPtival/PeaCoq

Bump mathjax from 2.7.9 to 3.1.4 in /web

Superseded by #98.

dependabot-preview[bot]

comment created time in 10 hours

create barnchPtival/PeaCoq

branch : dependabot/npm_and_yarn/web/mathjax-3.2.0

created branch time in 10 hours

PR opened Ptival/PeaCoq

Bump mathjax from 2.7.9 to 3.2.0 in /web

Bumps mathjax from 2.7.9 to 3.2.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/mathjax/MathJax/releases">mathjax's releases</a>.</em></p> <blockquote> <h2>MathJax v3.2.0</h2> <p>This is a feature release that includes a new lazy-typesetting extension, nine new TeX extensions, a port of the v2 MML3 extension, new Hindi support in the expression explorer, along with several other improvements, and a number of bug fixes. See the <a href="https://github.com/mathjax/MathJax-src/releases/tag/3.2.0">release notes</a> for details.</p> <h2>MathJax v3.1.4</h2> <p>This is a hot fix release to fix two problems with the recent 3.1.3 version. See the <a href="https://github.com/mathjax/MathJax-src/releases/tag/3.1.4">release notes</a> for details.</p> <h2>MathJax 3.1.3</h2> <p>This is a bug fix release that resolves more than 70 issues, and updates a number of modules on which MathJax relies. See the <a href="https://github.com/mathjax/MathJax-src/releases/tag/3.1.3">release notes</a> for details.</p> <h2>MathJax v3.1.2</h2> <p>Hot fix to correct regression introduced in v3.1.1 that caused control sequences followed by spaces to not be recognized.</p> <h2>MathJax v3.1.1</h2> <p>This is a bug fix release to address issues that arose from the recent 3.1.0 release. See the <a href="https://github.com/mathjax/MathJax-src/releases/tag/3.1.0">release notes</a> for details.</p> <h2>MathJax v3.1.0</h2> <p>This is a feature release that includes a number of API improvements, new extensions, and updates to the assistive tools, as described in the <a href="https://github.com/mathjax/MathJax-src/releases/tag/3.1.0">release notes</a>.</p> <h2>MathJax v3.0.5</h2> <p>This is a hot fix release to resolve an important issue with horizontal stretchy characters (e.g., <code>\overline</code> and <code>\overrightarrow</code>) in CommonHTML output that was introduced in the recent version 3.0.4 release.</p> <h2>MathJax v3.0.4</h2> <p>This is a bug-fix release. See the <a href="https://github.com/mathjax/MathJax-src/releases/tag/3.0.4">release notes</a> for details.</p> <p>Note that version 3.0.2 and 3.0.3 had problems with their <code>npm</code> deployment (some files where missing from the package), so were removed. This is the next actual version after 3.0.1</p> <h2>MathJax v3.0.1</h2> <p>This is a bug-fix release. See the <a href="https://github.com/mathjax/MathJax-src/releases/tag/3.0.1">release notes</a> for details.</p> <h2>MathJax v3.0.0</h2> <p>After over two years of development, the MathJax team is pleased to announce the official release of MathJax 3.0.0!</p> <p>This version is a complete rewrite of MathJax from the ground up using modern programming techniques, including Typescript, ES6 modules, Promises, and more.</p> <p>Please see the <a href="http://docs.mathjax.org/en/v3.0-latest/upgrading/whats-new-3.0.html">What's New in v3.0</a> section of the documentation for details about the new version 3.0.0.</p> <p>Please see the <a href="http://docs.mathjax.org/en/v3.0-latest/upgrading/v2.html">Upgrading from v2</a> instructions for details about what is and isn't in version 3, and how to upgrade your site from version 2. Note in particular that there is a <a href="https://mathjax.github.io/MathJax-demos-web/convert-configuration/convert-configuration.html">configuration converter</a> that can help you move from version 2 to version 3.</p> <p>See the <a href="http://docs.mathjax.org/">documentation</a> for details about how to use MathJax.</p> <p>See the <a href="https://github.com/mathjax/MathJax-src">MathJax Source Repository</a> for the source code for versions 3.</p> <p>There are two repositories that contain examples of using MathJax, one for web pages, and one for use with node on a server:</p> <ul> <li><a href="https://github.com/mathjax/MathJax-demos-web#mathjax-demos-web">MathJax Web Examples</a></li> <li><a href="https://github.com/mathjax/MathJax-demos-node#mathjax-demos-node">MathJax Node Examples</a></li> </ul> <p>Please use the <a href="https://github.com/mathjax/MathJax/issues">MathJax Issue Tracker</a> to report problems in version 3 of MathJax.</p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/mathjax/MathJax/commit/7146ffa47956e7dae05739cfe905d8aaf1e4780a"><code>7146ffa</code></a> Release version 3.2.0</li> <li><a href="https://github.com/mathjax/MathJax/commit/05b057160d5210bb1c41510a7b0ed2e1b8a5c2b9"><code>05b0571</code></a> Update to version 3.2.0</li> <li><a href="https://github.com/mathjax/MathJax/commit/be11806df1ae075508e33500c990497062ef3c5a"><code>be11806</code></a> Merge branch 'develop'</li> <li><a href="https://github.com/mathjax/MathJax/commit/e0575afdda9d94b9ba1d9045ebbce15b4476c465"><code>e0575af</code></a> Update to version 3.1.4</li> <li><a href="https://github.com/mathjax/MathJax/commit/af2bacdb2a38245a4a68c84bf7a5fb2e6da35426"><code>af2bacd</code></a> Merge branch 'develop'</li> <li><a href="https://github.com/mathjax/MathJax/commit/de316b931638887c26525aad4ac55acaca7093cd"><code>de316b9</code></a> Update package.json and files to v3.1.3</li> <li><a href="https://github.com/mathjax/MathJax/commit/ec5c85494ad89f5e60c727c0b5c8534a966be09d"><code>ec5c854</code></a> Merge branch 'update-shields' into develop</li> <li><a href="https://github.com/mathjax/MathJax/commit/10160614b6b5844f231c91423533fbddd28d55cb"><code>1016061</code></a> Merge branch 'update-shields'</li> <li><a href="https://github.com/mathjax/MathJax/commit/117409ac26dbabf70b9915dc49d9623e0000fde5"><code>117409a</code></a> Add shields for rank and downloads</li> <li><a href="https://github.com/mathjax/MathJax/commit/1335230503dddfeb0e07687308a55795d9c005e8"><code>1335230</code></a> Update issue templates</li> <li>Additional commits viewable in <a href="https://github.com/mathjax/MathJax/compare/2.7.9...3.2.0">compare view</a></li> </ul> </details> <br />

Dependabot compatibility score

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.


<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 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)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

</details>

+1 -1

0 comment

1 changed file

pr created time in 10 hours

delete branch Ptival/chick

delete branch : dependabot/npm_and_yarn/frontend/npm-check-updates-11.6.0

delete time in 10 hours

PR closed Ptival/chick

Bump npm-check-updates from 2.14.2 to 11.6.0 in /frontend dependencies

Bumps npm-check-updates from 2.14.2 to 11.6.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/raineorshine/npm-check-updates/releases">npm-check-updates's releases</a>.</em></p> <blockquote> <h2>v11.5.0</h2> <h2>Minor</h2> <p><code>npm-check-updates</code> will now auto-detect yarn and apply <code>--packageManager yarn</code> when <code>yarn.lock</code> is present and <code>package-lock.json</code> is <strong>not</strong> present. You can override this by explicitly setting <code>--packageManager npm</code>. It will print "Using yarn" when the auto-detection is triggered.</p> <h2>v11.4.0</h2> <h2>Minor</h2> <ul> <li>Use <code>--peer</code> to check peer dependencies of installed packages and filter updates to compatible versions. <ul> <li>791aa22 Respect peer dependencies (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/869">#869</a>)</li> </ul> </li> <li>Bump <code>mem</code> (minor)</li> </ul> <h2>Patch</h2> <ul> <li>696168b <code>--deep</code>: Fix Windows path</li> <li>Bump dependencies (patch)</li> </ul> <h2>v11.2.0</h2> <p>Wildcards and globs can now be used in filters without having to use regex:</p> <pre lang="sh"><code>ncu react-* # upgrade packages that start with "react-" ncu !commander # upgrade everything except "commander" </code></pre> <p>Since special characters are not allowed in package names, this change <em>shouldn't</em> break anything, but please let me know if a filter that was working before <code>v11.2.0</code> is not now!</p> <h3>Commits</h3> <p>ee27448 Add filter support for wildcards and glob expressions. Fixes <a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/219">#219</a>.</p> <h2>v11.0.0</h2> <h3>Breaking</h3> <ul> <li><code>--packageFile</code> - Now interprets its argument as a glob pattern. It is possible that a previously supplied argument may be interepreted differently now (though I'm not aware of specific instances). Due to our conservative release policy we are releasing as a major version upgrade and allowing developers to assess for themselves.</li> </ul> <h3>Features</h3> <ul> <li><code>--deep</code> - Run recursively in current working directory. Alias of <code>--packageFile '/package.json'</code>.</li> </ul> <p>See: <a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/785">#785</a></p> <p><a href="https://github.com/raineorshine/npm-check-updates/compare/v10.3.1...v11.0.0">https://github.com/raineorshine/npm-check-updates/compare/v10.3.1...v11.0.0</a></p> <h2>v10.0.0</h2> <h2>[10.0.0] - 2020-11-08</h2> <h3>Breaking</h3> <ul> <li>Specifiying both the <code>--filter</code> option and argument filters will now throw an error. Use one or the other. Previously the arguments would override the <code>--filter</code> option, which made for a confusing result when accidentally not quoting the option in the shell. This change is only breaking for those who are relying on the incorrect behavior of argument filters overriding <code>--filter</code>.</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/raineorshine/npm-check-updates/blob/main/CHANGELOG.md">npm-check-updates's changelog</a>.</em></p> <blockquote> <h1>Changelog</h1> <p>This file documents all <strong>major version</strong> releases. For other releases, you'll have to read the <a href="https://github.com/raineorshine/npm-check-updates/">commit history</a>.</p> <h2>[11.0.0] - 2021-01-20</h2> <h3>Breaking</h3> <ul> <li><code>--packageFile</code> - Now interprets its argument as a glob pattern. It is possible that a previously supplied argument may be interepreted differently now (though I'm not aware of specific instances). Due to our conservative release policy we are releasing as a major version upgrade and allowing developers to assess for themselves.</li> </ul> <h3>Features</h3> <ul> <li><code>--deep</code> - Run recursively in current working directory. Alias of <code>--packageFile '/package.json'</code>.</li> </ul> <p>See: <a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/785">#785</a></p> <p><a href="https://github.com/raineorshine/npm-check-updates/compare/v10.3.1...v11.0.0">https://github.com/raineorshine/npm-check-updates/compare/v10.3.1...v11.0.0</a></p> <h2>[10.0.0] - 2020-11-08</h2> <h3>Breaking</h3> <ul> <li>Specifiying both the <code>--filter</code> option and argument filters will now throw an error. Use one or the other. Previously the arguments would override the <code>--filter</code> option, which made for a confusing result when accidentally not quoting the option in the shell. This change is only breaking for those who are relying on the incorrect behavior of argument filters overriding <code>--filter</code>.</li> </ul> <p>See: <a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/759#issuecomment-723587297">#759</a></p> <p><a href="https://github.com/raineorshine/npm-check-updates/compare/v9.2.4...v10.0.0">https://github.com/raineorshine/npm-check-updates/compare/v9.2.4...v10.0.0</a></p> <h2>[9.0.0] - 2020-09-10</h2> <h3>Breaking</h3> <ul> <li>Versions marked as <code>deprecated</code> in npm are now ignored by default. If the latest version is deprecated, the next highest non-deprecated version will be suggested. Use <code>--deprecated</code> to include deprecated versions (old behavior).</li> </ul> <p><a href="https://github.com/raineorshine/npm-check-updates/compare/v8.1.1...v9.0.0">https://github.com/raineorshine/npm-check-updates/compare/v8.1.1...v9.0.0</a></p> <h2>[8.0.0] - 2020-08-29</h2> <h3>Breaking</h3> <ul> <li><code>--semverLevel major</code> is now <code>--target minor</code>. <code>--semverLevel minor</code> is now <code>--target patch</code>. This change was made to provide more intuitive semantics for <code>--semverLevel</code> (now <code>--target</code>). Most people assumed it meant the inclusive upper bound, so now it reflects that. <a href="https://github.com/raineorshine/npm-check-updates/commits/a2111f4c2">a2111f4c2</a></li> <li>Programmatic usage: <code>run</code> now defaults to <code>silent: true</code> instead of <code>loglevel: 'silent</code>, unless <code>loglevel</code> is explicitly specified. If you overrode <code>silent</code> or <code>loglevel</code>, this may affect the logging behavior. <a href="https://github.com/raineorshine/npm-check-updates/commits/423e024">423e024</a></li> </ul> <h3>Deprecated</h3> <p>Options that controlled the target version (upper bound) of upgrades have been consolidated under <code>--target</code>. The old options are aliased with a deprecation warning and will be removed in the next major version. No functionality has been removed.</p> <ul> <li><code>--greatest</code>: Renamed to <code>--target greatest</code></li> <li><code>--newest</code>: Renamed to <code>--target newest</code></li> <li><code>--semverLevel</code>: Renamed to <code>--target</code></li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/dfcbe8e1b73b3e24d07fe3d46e4958fae5029ebb"><code>dfcbe8e</code></a> 11.6.0</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/f43e09561a70aa53bb0a04e2cc410f41a0bbfdc2"><code>f43e095</code></a> Bump dependencies</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/18358a4d08a5f2d532600cfc5e6bf24e0f30af9c"><code>18358a4</code></a> feat: --mergeConfig option for --deep to inherit config settings (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/897">#897</a>)</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/7f538ed3c9b3e9f028058ad118a8dd4f7eb83cae"><code>7f538ed</code></a> 11.5.13</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/a1ad7c991859e6fbdf0557df407a792bf57e2eb8"><code>a1ad7c9</code></a> getCurrentDependencies: Guard comparison of duplicates (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/893">#893</a>).</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/486535fd605ceb8cf402029dde784bb404e36c0c"><code>486535f</code></a> 11.5.12</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/d864ad78300d645009c3ee05b2379bf089c60788"><code>d864ad7</code></a> Bump dependencies</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/9faf86e90d0560d8976c96f332761f156302b9ed"><code>9faf86e</code></a> Only print upgradedPeerDependencies if --peer is set.</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/74e959fe1fe4224c4d2f041cc16181a54d0cab24"><code>74e959f</code></a> test/doctor/options: Add required license field to package.json.</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/e8eb22b38d5eb858ff3fb770680cdc2ac0c2460a"><code>e8eb22b</code></a> Use lowest version when a dependency is in more than one section (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/892">#892</a>).</li> <li>Additional commits viewable in <a href="https://github.com/raineorshine/npm-check-updates/compare/v2.14.2...v11.6.0">compare view</a></li> </ul> </details> <br />

Dependabot compatibility score

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.


<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 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)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

</details>

+1 -1

1 comment

1 changed file

dependabot-preview[bot]

pr closed time in 10 hours

pull request commentPtival/chick

Bump npm-check-updates from 2.14.2 to 11.6.0 in /frontend

Superseded by #35.

dependabot-preview[bot]

comment created time in 10 hours

PR opened Ptival/chick

Bump npm-check-updates from 2.14.2 to 11.7.1 in /frontend

Bumps npm-check-updates from 2.14.2 to 11.7.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/raineorshine/npm-check-updates/releases">npm-check-updates's releases</a>.</em></p> <blockquote> <h2>v11.5.0</h2> <h2>Minor</h2> <p><code>npm-check-updates</code> will now auto-detect yarn and apply <code>--packageManager yarn</code> when <code>yarn.lock</code> is present and <code>package-lock.json</code> is <strong>not</strong> present. You can override this by explicitly setting <code>--packageManager npm</code>. It will print "Using yarn" when the auto-detection is triggered.</p> <h2>v11.4.0</h2> <h2>Minor</h2> <ul> <li>Use <code>--peer</code> to check peer dependencies of installed packages and filter updates to compatible versions. <ul> <li>791aa22 Respect peer dependencies (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/869">#869</a>)</li> </ul> </li> <li>Bump <code>mem</code> (minor)</li> </ul> <h2>Patch</h2> <ul> <li>696168b <code>--deep</code>: Fix Windows path</li> <li>Bump dependencies (patch)</li> </ul> <h2>v11.2.0</h2> <p>Wildcards and globs can now be used in filters without having to use regex:</p> <pre lang="sh"><code>ncu react-* # upgrade packages that start with "react-" ncu !commander # upgrade everything except "commander" </code></pre> <p>Since special characters are not allowed in package names, this change <em>shouldn't</em> break anything, but please let me know if a filter that was working before <code>v11.2.0</code> is not now!</p> <h3>Commits</h3> <p>ee27448 Add filter support for wildcards and glob expressions. Fixes <a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/219">#219</a>.</p> <h2>v11.0.0</h2> <h3>Breaking</h3> <ul> <li><code>--packageFile</code> - Now interprets its argument as a glob pattern. It is possible that a previously supplied argument may be interepreted differently now (though I'm not aware of specific instances). Due to our conservative release policy we are releasing as a major version upgrade and allowing developers to assess for themselves.</li> </ul> <h3>Features</h3> <ul> <li><code>--deep</code> - Run recursively in current working directory. Alias of <code>--packageFile '/package.json'</code>.</li> </ul> <p>See: <a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/785">#785</a></p> <p><a href="https://github.com/raineorshine/npm-check-updates/compare/v10.3.1...v11.0.0">https://github.com/raineorshine/npm-check-updates/compare/v10.3.1...v11.0.0</a></p> <h2>v10.0.0</h2> <h2>[10.0.0] - 2020-11-08</h2> <h3>Breaking</h3> <ul> <li>Specifiying both the <code>--filter</code> option and argument filters will now throw an error. Use one or the other. Previously the arguments would override the <code>--filter</code> option, which made for a confusing result when accidentally not quoting the option in the shell. This change is only breaking for those who are relying on the incorrect behavior of argument filters overriding <code>--filter</code>.</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/raineorshine/npm-check-updates/blob/main/CHANGELOG.md">npm-check-updates's changelog</a>.</em></p> <blockquote> <h1>Changelog</h1> <p>This file documents all <strong>major version</strong> releases. For other releases, you'll have to read the <a href="https://github.com/raineorshine/npm-check-updates/">commit history</a>.</p> <h2>[11.0.0] - 2021-01-20</h2> <h3>Breaking</h3> <ul> <li><code>--packageFile</code> - Now interprets its argument as a glob pattern. It is possible that a previously supplied argument may be interepreted differently now (though I'm not aware of specific instances). Due to our conservative release policy we are releasing as a major version upgrade and allowing developers to assess for themselves.</li> </ul> <h3>Features</h3> <ul> <li><code>--deep</code> - Run recursively in current working directory. Alias of <code>--packageFile '/package.json'</code>.</li> </ul> <p>See: <a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/785">#785</a></p> <p><a href="https://github.com/raineorshine/npm-check-updates/compare/v10.3.1...v11.0.0">https://github.com/raineorshine/npm-check-updates/compare/v10.3.1...v11.0.0</a></p> <h2>[10.0.0] - 2020-11-08</h2> <h3>Breaking</h3> <ul> <li>Specifiying both the <code>--filter</code> option and argument filters will now throw an error. Use one or the other. Previously the arguments would override the <code>--filter</code> option, which made for a confusing result when accidentally not quoting the option in the shell. This change is only breaking for those who are relying on the incorrect behavior of argument filters overriding <code>--filter</code>.</li> </ul> <p>See: <a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/759#issuecomment-723587297">#759</a></p> <p><a href="https://github.com/raineorshine/npm-check-updates/compare/v9.2.4...v10.0.0">https://github.com/raineorshine/npm-check-updates/compare/v9.2.4...v10.0.0</a></p> <h2>[9.0.0] - 2020-09-10</h2> <h3>Breaking</h3> <ul> <li>Versions marked as <code>deprecated</code> in npm are now ignored by default. If the latest version is deprecated, the next highest non-deprecated version will be suggested. Use <code>--deprecated</code> to include deprecated versions (old behavior).</li> </ul> <p><a href="https://github.com/raineorshine/npm-check-updates/compare/v8.1.1...v9.0.0">https://github.com/raineorshine/npm-check-updates/compare/v8.1.1...v9.0.0</a></p> <h2>[8.0.0] - 2020-08-29</h2> <h3>Breaking</h3> <ul> <li><code>--semverLevel major</code> is now <code>--target minor</code>. <code>--semverLevel minor</code> is now <code>--target patch</code>. This change was made to provide more intuitive semantics for <code>--semverLevel</code> (now <code>--target</code>). Most people assumed it meant the inclusive upper bound, so now it reflects that. <a href="https://github.com/raineorshine/npm-check-updates/commits/a2111f4c2">a2111f4c2</a></li> <li>Programmatic usage: <code>run</code> now defaults to <code>silent: true</code> instead of <code>loglevel: 'silent</code>, unless <code>loglevel</code> is explicitly specified. If you overrode <code>silent</code> or <code>loglevel</code>, this may affect the logging behavior. <a href="https://github.com/raineorshine/npm-check-updates/commits/423e024">423e024</a></li> </ul> <h3>Deprecated</h3> <p>Options that controlled the target version (upper bound) of upgrades have been consolidated under <code>--target</code>. The old options are aliased with a deprecation warning and will be removed in the next major version. No functionality has been removed.</p> <ul> <li><code>--greatest</code>: Renamed to <code>--target greatest</code></li> <li><code>--newest</code>: Renamed to <code>--target newest</code></li> <li><code>--semverLevel</code>: Renamed to <code>--target</code></li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/857b825f0f57f3d23ca1c53e2a8f12b5ec8b4976"><code>857b825</code></a> 11.7.1</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/be8bacd7375df19a97daa62646e2477fb1f735da"><code>be8bacd</code></a> Revert mocha which does not support nodejs v10.</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/6ab8c08b39f6b25eb3b67c10b2e19893f52f0a98"><code>6ab8c08</code></a> 11.7.0</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/d777e7d3149e9c35f4a4b77a7c4479b53b24508a"><code>d777e7d</code></a> Bump dependencies</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/07d5060cfd9ee81941b387ce27fa52f5fca59d0b"><code>07d5060</code></a> packageData: Accept object type (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/908">#908</a>)</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/a7a03d9706f832055b4ce7028a63c6e11713782a"><code>a7a03d9</code></a> build(deps-dev): bump eslint from 7.26.0 to 7.27.0 (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/902">#902</a>)</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/7b6dc9e6395257b8fa78f17945e08bfc07faeeca"><code>7b6dc9e</code></a> build(deps-dev): bump eslint-config-standard from 16.0.2 to 16.0.3 (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/901">#901</a>)</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/69fee55b3ddab8e1260a86a59eaac0b905ae135f"><code>69fee55</code></a> build(deps-dev): bump eslint-plugin-import from 2.23.0 to 2.23.4 (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/900">#900</a>)</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/dfcbe8e1b73b3e24d07fe3d46e4958fae5029ebb"><code>dfcbe8e</code></a> 11.6.0</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/f43e09561a70aa53bb0a04e2cc410f41a0bbfdc2"><code>f43e095</code></a> Bump dependencies</li> <li>Additional commits viewable in <a href="https://github.com/raineorshine/npm-check-updates/compare/v2.14.2...v11.7.1">compare view</a></li> </ul> </details> <br />

Dependabot compatibility score

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.


<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 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)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

</details>

+1 -1

0 comment

1 changed file

pr created time in 10 hours

delete branch Ptival/peacoq-frontend

delete branch : dependabot/npm_and_yarn/npm-check-updates-11.6.0

delete time in 10 hours

PR closed Ptival/peacoq-frontend

Bump npm-check-updates from 11.5.11 to 11.6.0 dependencies

Bumps npm-check-updates from 11.5.11 to 11.6.0. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/dfcbe8e1b73b3e24d07fe3d46e4958fae5029ebb"><code>dfcbe8e</code></a> 11.6.0</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/f43e09561a70aa53bb0a04e2cc410f41a0bbfdc2"><code>f43e095</code></a> Bump dependencies</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/18358a4d08a5f2d532600cfc5e6bf24e0f30af9c"><code>18358a4</code></a> feat: --mergeConfig option for --deep to inherit config settings (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/897">#897</a>)</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/7f538ed3c9b3e9f028058ad118a8dd4f7eb83cae"><code>7f538ed</code></a> 11.5.13</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/a1ad7c991859e6fbdf0557df407a792bf57e2eb8"><code>a1ad7c9</code></a> getCurrentDependencies: Guard comparison of duplicates (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/893">#893</a>).</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/486535fd605ceb8cf402029dde784bb404e36c0c"><code>486535f</code></a> 11.5.12</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/d864ad78300d645009c3ee05b2379bf089c60788"><code>d864ad7</code></a> Bump dependencies</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/9faf86e90d0560d8976c96f332761f156302b9ed"><code>9faf86e</code></a> Only print upgradedPeerDependencies if --peer is set.</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/74e959fe1fe4224c4d2f041cc16181a54d0cab24"><code>74e959f</code></a> test/doctor/options: Add required license field to package.json.</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/e8eb22b38d5eb858ff3fb770680cdc2ac0c2460a"><code>e8eb22b</code></a> Use lowest version when a dependency is in more than one section (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/892">#892</a>).</li> <li>See full diff in <a href="https://github.com/raineorshine/npm-check-updates/compare/v11.5.11...v11.6.0">compare view</a></li> </ul> </details> <br />

Dependabot compatibility score

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.


<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 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>

+1 -1

1 comment

1 changed file

dependabot[bot]

pr closed time in 10 hours

pull request commentPtival/peacoq-frontend

Bump npm-check-updates from 11.5.11 to 11.6.0

Superseded by #38.

dependabot[bot]

comment created time in 10 hours

PR opened Ptival/peacoq-frontend

Bump npm-check-updates from 11.5.11 to 11.7.1

Bumps npm-check-updates from 11.5.11 to 11.7.1. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/857b825f0f57f3d23ca1c53e2a8f12b5ec8b4976"><code>857b825</code></a> 11.7.1</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/be8bacd7375df19a97daa62646e2477fb1f735da"><code>be8bacd</code></a> Revert mocha which does not support nodejs v10.</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/6ab8c08b39f6b25eb3b67c10b2e19893f52f0a98"><code>6ab8c08</code></a> 11.7.0</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/d777e7d3149e9c35f4a4b77a7c4479b53b24508a"><code>d777e7d</code></a> Bump dependencies</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/07d5060cfd9ee81941b387ce27fa52f5fca59d0b"><code>07d5060</code></a> packageData: Accept object type (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/908">#908</a>)</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/a7a03d9706f832055b4ce7028a63c6e11713782a"><code>a7a03d9</code></a> build(deps-dev): bump eslint from 7.26.0 to 7.27.0 (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/902">#902</a>)</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/7b6dc9e6395257b8fa78f17945e08bfc07faeeca"><code>7b6dc9e</code></a> build(deps-dev): bump eslint-config-standard from 16.0.2 to 16.0.3 (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/901">#901</a>)</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/69fee55b3ddab8e1260a86a59eaac0b905ae135f"><code>69fee55</code></a> build(deps-dev): bump eslint-plugin-import from 2.23.0 to 2.23.4 (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/900">#900</a>)</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/dfcbe8e1b73b3e24d07fe3d46e4958fae5029ebb"><code>dfcbe8e</code></a> 11.6.0</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/f43e09561a70aa53bb0a04e2cc410f41a0bbfdc2"><code>f43e095</code></a> Bump dependencies</li> <li>Additional commits viewable in <a href="https://github.com/raineorshine/npm-check-updates/compare/v11.5.11...v11.7.1">compare view</a></li> </ul> </details> <br />

Dependabot compatibility score

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.


<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 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>

+1 -1

0 comment

1 changed file

pr created time in 10 hours

push eventGaloisInc/crucible

Rob Dockins

commit sha 8346f897189199bdd8481530cb7ccafbb3b2dd34

Add crucible-syntax support for the struct type and operations

view details

Rob Dockins

commit sha 79250baf9ac5c1a4e419508af03b148be9a374eb

Add a new Crucible type for representing sequence values. Unlike vectors, sequences are explicitly represented as cons-lists and are designed to be merged effeciently, even at different lengths.

view details

Rob Dockins

commit sha 0e6cb06687602137634be5785cffdd0a651d4798

Add support for the sequence type to crucible-syntax. Add a very basic test case.

view details

Rob Dockins

commit sha 38d1205685fcb6e1c69fc3dd90073ce4541d1dda

Comments, minor fixes, and a concretization function

view details

Rob Dockins

commit sha 5b42d0491d30ea0ce5d183623cccaee056ea844f

Add additional sequence tests

view details

Rob Dockins

commit sha 93bbbc98fbf0b4c16a5149caefb301defa15bdb1

Add a pretty printer and traversal function for SymSequence.

view details

Rob Dockins

commit sha 87d86cffc76e8b63aed5c2c4cbc28fa136a080d5

Update crucible-syntax README with new types.

view details

robdockins

commit sha 4de077c9e57610df891c22da021966f73a51d787

Merge pull request #759 from GaloisInc/seq Sequences

view details

Aaron Tomb

commit sha 584d47d384104c06a92b3820882639e9898e4b0d

Bump what4 submodule (#765) Adds fix for GaloisInc/what4#133

view details

Aaron Tomb

commit sha ab989709ab17facf2b85368e79d081b80e0ddf9a

Enable manual trigger of crux-llvm binary tarballs

view details

Aaron Tomb

commit sha 5148f86547d1a485493aa488c060148e07260e50

Always upload crux-llvm tarballs

view details

push time in 16 hours

delete branch GaloisInc/crucible

delete branch : at-crux-mcsat

delete time in 16 hours

push eventGaloisInc/crucible

Aaron Tomb

commit sha 584d47d384104c06a92b3820882639e9898e4b0d

Bump what4 submodule (#765) Adds fix for GaloisInc/what4#133

view details

push time in 16 hours

PR merged GaloisInc/crucible

Bump what4 submodule

Adds fix for GaloisInc/what4#133

+1 -1

2 comments

1 changed file

atomb

pr closed time in 16 hours

push eventGaloisInc/saw-script

Rob Dockins

commit sha de30403dfba43cf21a14101acafc3a4e2a65338a

Improve `scAbstractExts` and `scGeneralizeExts` Previously, these functions were not working correctly when the _types_ of some `ExtCns` values mention some of the `ExtCns` values being abstracted or generalized. Now we are careful to both evaluate inside the types of `ExtCns` values occuring inside the term, as well as making sure that the types of `ExtCns` values in the list are processed properly in the context of the outer values.

view details

mergify[bot]

commit sha a511d6a17cccd5c5e20e3fec15560d83137047c8

Merge pull request #1335 from GaloisInc/dep-abs Improve `scAbstractExts` and `scGeneralizeExts`

view details

Rob Dockins

commit sha 3c70694969021e450110e0aa95af0136020cfa9d

Remove the obsolete `SAWScript.VerificationCheck` and `SAWScript.PathVC` modules.

view details

Rob Dockins

commit sha 20ddad9b1ff1ca4fb8fdf6d805ce774cc3f52b35

Add simulator value support for term model evaluation. This mostly just adds `LocalName` values to functions and Pi types so meaningful names can be round-tripped. We also add a `VTyTerm` constructor to `TValue` for types that cannot be fully evaluated (because they are blocked on a variable, etc).

view details

Rob Dockins

commit sha 1e3657d575f84d0a7cf927a8c219e3334df823cb

In the saw-core simulator, distinguish dependent from non-dependent Pi types. During simulation, notice the special case where the variable does not appear in the body of the Pi type.

view details

Rob Dockins

commit sha b852b1419f253065f051a8cb219c338ad68204d3

Expand the types of values that can be in a `TypedTerm`. In addition to Cryptol value types, Cryptol kinds and general SAWCore types can also appear.

view details

Rob Dockins

commit sha 81c800afb44440b28b603173cce947bf25d93b84

Update SAWScript with the new, more permissive, notion of `TypedTerm`

view details

Rob Dockins

commit sha 9a46e6d1bd4881cf8617afb2c195c960b352e334

Update saw-remote-api with TypedTerm changes

view details

Rob Dockins

commit sha 55e3eb13265eb205955487865028eefc161392d4

warning police

view details

robdockins

commit sha a02fe4474bb3cb58f575e5dfaccdfd87154d345b

Merge pull request #1336 from GaloisInc/typed-term Typed term

view details

Rob Dockins

commit sha 0e4839332a6b1ac35f6a83e98cf0c54bd49229e5

Split `VToNat` into `VBVToNat` and `VIntToNat` This distinguishes the two different coercions that can occur, and allows us to track the width of the bitvector type in `VBVToNat`.

view details

Rob Dockins

commit sha ffc1d201ba9b2710a0b2b8a158fac95d5ff580b6

Move some operations from the concrete simulator into `Prim` where they can be reused more easily.

view details

Rob Dockins

commit sha bd213b0f7328ab4c03689df1f2cd48bb98b3865f

Refactor and rework how recursors are implemented. The main techincal change here is to allow "recursors" to be value forms in their own right at the AST level, conceptually separate from recursor applications. This simplifies a variety of things relating to the implementation of recursors; in particular, the terms representing iota reductions require fewer free variables and have simpler types. The "recursor" value is specified by giving: the data type, the parameters to that data type, the elimination motive, and the constructor eliminator functions. The data defining a recursor are constant throughout the execution of recursive elimination. A "recursor application" takes a recursor value, values for the indices of the data type being eliminated, and the argument to be eliminated. Although this change allows recursor values to be abstracted by lambdas and for recursor applications to be built separately from a concrete recursor value, there is currently no surface syntax for building such a "partially applied" recursor, nor for the new type of recursor values. As before, only fully-applied recursors are allowed by the parser/typechecker front-end.

view details

Rob Dockins

commit sha 2656efcf82976d9cad5016f529fd95c29fcc3786

Pipe type info through mux operations.

view details

Rob Dockins

commit sha e360dccf89d71757c43f4939983ac2e192450174

Add type information to the simulator evaluation environment Split the collection of arguments to data constructors to keep parameters separate from regular arguments.

view details

Rob Dockins

commit sha 33a4c377a8332c3a71d0d674901f522bed36e555

Refactor the names of data type and constructors to carry `PrimName` values instead of just `Ident` and register their names in the naming environment so they participate in pretty printing name resolution.

view details

Rob Dockins

commit sha 432bfa4bb9484c70a83fe9d6da54982ff457c75f

Implement recursors on concrete Nat values

view details

Rob Dockins

commit sha 5c657bb2c49106004266eb33fb36e319719be492

Fix muxing of datatype constructor values. This really only properly handles pretty narrow situations regarding constructors. Muxing data type values will only succeed if the same constructor is used in both values, and if the constructor forms a non-dependent function on its regular (non-parameter) arguments. However, this is similar to the prior situation, where the constructors were required to be the same, and muxing arguments would panic if they differed in shape.

view details

Rob Dockins

commit sha 7f988d0c3d100978fb0dac541bc14e4543137e6d

Better error reporting for recursors and recursor applications

view details

Rob Dockins

commit sha 1707182d59607c5ba184addd63b7428f3211f5d1

Add a notion of `NeutralTerm` for when evaluation gets stuck on opaque values.

view details

push time in 16 hours

push eventGaloisInc/reopt

dependabot[bot]

commit sha d9030bdb92fdafed6fa8fe746d4d5c4a94d37183

Bump normalize-url from 4.5.0 to 4.5.1 in /vscode-plugin Bumps [normalize-url](https://github.com/sindresorhus/normalize-url) from 4.5.0 to 4.5.1. - [Release notes](https://github.com/sindresorhus/normalize-url/releases) - [Commits](https://github.com/sindresorhus/normalize-url/commits) --- updated-dependencies: - dependency-name: normalize-url dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>

view details

Joe Hendrix

commit sha feeed7f579ae255d2c1eeba58e19a55bfe5a2108

Merge pull request #81 from GaloisInc/dependabot/npm_and_yarn/vscode-plugin/normalize-url-4.5.1 Bump normalize-url from 4.5.0 to 4.5.1 in /vscode-plugin

view details

Joe Hendrix

commit sha 64a17e0f4db7e34a831fc4e3844e616789baa471

Improve error message when stack addresses escape.

view details

Joe Hendrix

commit sha 38546c943efd671b696bd5203cc51679224b11bc

Move reopt_explore_tests

view details

Joe Hendrix

commit sha 37d9679c605ee8e4e84786f80e5e496dd7a0c290

Populate entry points using eh_frame fdes; submodule bump.

view details

Joe Hendrix

commit sha de2869a70e841510ed7314a64814e3828d683f28

Reduce Main_explore verbosity; update dependencies.

view details

Joe Hendrix

commit sha 459d9a90b68428ab1d2c908a097253cbc93b69a5

Refactor to reopt events and statistics.

view details

Joe Hendrix

commit sha 792aee62bd8600ead9eee431fdb232a9d96810dd

Formatting/linting clenups

view details

Joe Hendrix

commit sha a13e371564446fa09eceaf070b79f2d64c6fbcb1

Revamp logging and statical analysis. This should support more comprehensive machine readable errors and better statistics on errors.

view details

Joe Hendrix

commit sha 62c6d0920ec5bee29ef1e057971d2a1dc1abf264

Cleanup external-tools and minor refactoring to debug information.

view details

Joe Hendrix

commit sha 619afe2e19e19f18c4175d662eaeed3182f9d9fd

Bump submodules

view details

Joe Hendrix

commit sha b615ce956de3446424df47c2d3ac4a5ae2b6f4fd

Disable reopt-explore tests for merging

view details

Joe Hendrix

commit sha 616f1087a0c32f96e43e33c07bc5e856d3771cb9

Merge pull request #80 from GaloisInc/jhx/invariant Improve stack address error messages; use eh_frame in discovery

view details

Andrew Kent

commit sha c8467921cbd1504195440681fb1a377eb72fcb28

feat: init support for dependency debug info

view details

push time in 17 hours

push eventGaloisInc/reopt-benchmark-binaries

Andrew Kent

commit sha 3dc7ec062264a57498920c2f7e6bfcf29ebccf00

add some debug libraries, modify permissions in archives

view details

push time in 17 hours

push eventGaloisInc/saw-script

Brian Huffman

commit sha c02256e1b02ab7a94f51cda05a09b60475a1ee9c

Add stubs for SuiteB and PrimeEC primitives to `Cryptol.sawcore`.

view details

Brian Huffman

commit sha 5e5409676e5d8d4b3c807db1ece1d501526fe0f3

Support SuiteB and PrimeEC primitives in translator.

view details

Brian Huffman

commit sha a885cc8d0a9811c907681ea750b75915fa5abfce

Extend cryptol-saw-core tests to include SuiteB.cry and PrimeEC.cry.

view details

mergify[bot]

commit sha d2916f83cb863e242a845fd94fe299a539f3eaa6

Merge pull request #1342 from GaloisInc/suiteb-ecc-prims cryptol-saw-core: SuiteB and ECC prims

view details

Rob Dockins

commit sha b8be0f7a2ca4d6b6bbb06af10e73d184f4bd7634

Add a new `default_term` command that applies Cryptol defaulting rules to a SAWCore term.

view details

Rob Dockins

commit sha 8c39944103d22ceb8cc38ede3fd13ab37552a86e

Make the argument order of `scAppend` match the argument order given by the primitive in the prelude.

view details

Rob Dockins

commit sha 205ec9bd718f7ebd0ad0728c4be972fd3541f65a

Use dummy values instead of `panic` for evaluating nondependent pi types. The term model evaluates values in the environment when reflecting neutral terms, so we can't put a panic here. We could also probably be more careful about evaluating only environment terms that are actually needed, but this is an easy fix.

view details

Rob Dockins

commit sha 642c8e7d82fc8d8165658312294d99c4d7c9ccae

Add a new operation for abstracting a term with respect to external constants, but first eta-collapsing as much as possible.

view details

Rob Dockins

commit sha e89a805faed269cd7e929e34ba24496eee3611bc

Implement some additional primitives, mostly involving strings

view details

Rob Dockins

commit sha bfba9658fb80bdee144704e145e338399ed800bd

Implement term constructors for the IntMod operations

view details

mergify[bot]

commit sha dabdee6e8fea3e9011b0e1672dde126501bbac59

Merge pull request #1343 from GaloisInc/misc Misc patches leading to the term model

view details

Ryan Scott

commit sha 0642f4cd0e210b2e197b0a59c4a6eeb11a45b33f

Add enable_lax_pointer_ordering Fixes #1308.

view details

mergify[bot]

commit sha e8703733697228101dd4db637d7fcb677cd887ff

Merge pull request #1309 from GaloisInc/T1308 Add enable_lax_pointer_ordering

view details

Rob Dockins

commit sha 9065e59c437c49d6af79c47c42401936934a667a

Implement a "term model" evaluator. The basic idea behind this evalutor is to use "normalization by evaluation" techniques to perform principled term reduction using the same simulator infrastructure we already have. The main difference from the concrete simulator is that syntax of terms may also appear among the value forms in the simulator. When these unevaluated "neutral" terms appear, the simulator will reconstruct syntax around them corresponding to the constructs it is attempting to evaluate. The result should be a syntactic term that is evaluated "as far as possible" until it gets stuck on some external variable, opaque term, or other term that is (for whatever reason) not in canonical form.

view details

Rob Dockins

commit sha 58d2db3f50d0ffbf51085a65bacd4a47858493e4

Add a `normalize_term` command to experiment with the results of the TermModel evaluator.

view details

Rob Dockins

commit sha c62c0bbfc3713c6c1aee0ad1f082425718835ca6

Implement `extract_uninterp` via the new term model.

view details

Rob Dockins

commit sha 2d9ba22778d12d1349f1d694e8507c4e69ef7a48

Allow the term model to hold some terms "opaque", which will prevent it from evaluating them, similar to how uninterpreted terms are treated in the solver evaluators.

view details

push time in 17 hours