Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update dependency gatsby to v4 [security] #117

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jun 10, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
gatsby (source, changelog) ^3.0.0 -> ^4.25.7 age adoption passing confidence

GitHub Vulnerability Alerts

CVE-2023-34238

Impact

The Gatsby framework prior to versions 4.25.7 and 5.9.1 contain a Local File Inclusion vulnerability in the __file-code-frame and __original-stack-frame paths, exposed when running the Gatsby develop server (gatsby develop).

The following steps can be used to reproduce the vulnerability:


# Create a new Gatsby project
$ npm init gatsby
$ cd my-gatsby-site

# Start the Gatsby develop server
$ gatsby develop

# Execute the Local File Inclusion vulnerability in __file-code-frame
$ curl "http://127.0.0.1:8000/__file-code-frame?filePath=/etc/passwd&lineNumber=1"

# Execute the Local File Inclusion vulnerability in __original-stack-frame
$ curl "http://127.0.0.1:8000/__original-stack-frame?moduleId=/etc/hosts&lineNumber=1&skipSourceMap=1"

It should be noted that by default gatsby develop is only accessible via the localhost 127.0.0.1, and one would need to intentionally expose the server to other interfaces to exploit this vulnerability by using server options such as --host 0.0.0.0, -H 0.0.0.0, or the GATSBY_HOST=0.0.0.0 environment variable.

Patches

A patch has been introduced in gatsby@5.9.1 and gatsby@4.25.7 which mitigates the issue.

Workarounds

As stated above, by default gatsby develop is only exposed to the localhost 127.0.0.1. For those using the develop server in the default configuration no risk is posed. If other ranges are required, preventing the develop server from being exposed to untrusted interfaces or IP address ranges would mitigate the risk from this vulnerability.

We encourage projects to upgrade to the latest major release branch for all Gatsby plugins to ensure the latest security updates and bug fixes are received in a timely manner.

Credits

We would like to thank Maxwell Garrett of Assetnote for bringing the __file-code-frame issue to our attention.

For more information

Email us at security@gatsbyjs.com.


Release Notes

gatsbyjs/gatsby (gatsby)

v4.25.7

Compare Source

v4.25.6

Compare Source

v4.25.5

Compare Source

v4.25.4

Compare Source

v4.25.3

Compare Source

v4.25.2

Compare Source

v4.25.1

Compare Source

v4.25.0

Compare Source

v4.24.8

Compare Source

v4.24.7

Compare Source

v4.24.6

Compare Source

v4.24.5

Compare Source

v4.24.4

Compare Source

v4.24.3

Compare Source

v4.24.2

Compare Source

v4.24.1

Compare Source

v4.24.0: v4.24

Compare Source

Welcome to gatsby@4.24.0 release (September 2022 #2)

Key highlights of this release:

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

Full changelog

v4.23.1

Compare Source

v4.23.0: v4.23

Compare Source

Welcome to gatsby@4.23.0 release (September 2022 #1)

Key highlights of this release:

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

Full changelog

v4.22.1

Compare Source

v4.22.0: v4.22

Compare Source

Welcome to gatsby@4.22.0 release (August 2022 #3)

Key highlights of this release:

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

Full changelog

v4.21.1

Compare Source

v4.21.0: v4.21

Compare Source

Welcome to gatsby@4.21.0 release (August 2022 #2)

Key highlights of this release:

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

Full changelog

v4.20.0: v4.20

Compare Source

Welcome to gatsby@4.20.0 release (August 2022 #1)

Key highlights of this release:

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

Full changelog

v4.19.2

Compare Source

v4.19.1

Compare Source

v4.19.0: v4.19

Compare Source

Welcome to gatsby@4.19.0 release (July 2022 #2)

Key highlights of this release:

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

Full changelog

v4.18.2

Compare Source

v4.18.1

Compare Source

v4.18.0: v4.18

Compare Source

Welcome to gatsby@4.18.0 release (July 2022 #1)

Key highlights of this release:

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

Full changelog

v4.17.2

Compare Source

v4.17.1

Compare Source

v4.17.0: v4.17

Compare Source

Welcome to gatsby@4.17.0 release (June 2022 #2)

Key highlights of this release:

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

Full changelog

v4.16.0: v4.16

Compare Source

Welcome to gatsby@4.16.0 release (June 2022 #1)

Key highlights of this release:

Also check out notable bugfixes.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

Full changelog

v4.15.2

Compare Source

v4.15.1

Compare Source

v4.15.0: v4.15

Compare Source

Welcome to gatsby@4.15.0 release (May 2022 #2)

Key highlights of this release:

Also check out notable bugfixes.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

[Full changelog][full-changelog]

v4.14.1

Compare Source

v4.14.0: v4.14

Compare Source

Welcome to gatsby@4.14.0 release (May 2022 #1)

Key highlights of this release:

Also check out notable bugfixes.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

Full changelog

v4.13.1

Compare Source

v4.13.0: v4.13

Compare Source

Welcome to gatsby@4.13.0 release (April 2022 #2)

Key highlights of this release:

Also check out notable bugfixes.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know
if you have any issues.

Previous release notes

Full changelog

v4.12.1

Compare Source

v4.12.0: v4.12

Compare Source

Welcome to gatsby@4.12.0 release (April 2022 #1)

Key highlights of this release:

Also check out notable bugfixes.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know
if you have any issues.

Previous release notes

Full changelog

v4.11.3

Compare Source

v4.11.2

Compare Source

v4.11.1

Compare Source

v4.11.0: v4.11

Compare Source

Welcome to gatsby@4.11.0 release (March 2022 #3)

Key highlights of this release:

Also check out notable bugfixes.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know
if you have any issues.

Previous release notes

Full changelog

v4.10.3

Compare Source

v4.10.2

Compare Source

v4.10.1

Compare Source

v4.10.0: v4.10

Compare Source

Welcome to gatsby@4.10.0 release (March 2022 #2)

Key highlights of this release:

Also check out notable bugfixes.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know
if you have any issues.

Previous release notes

Full changelog

v4.9.3

Compare Source

v4.9.2

Compare Source

v4.9.1

Compare Source

v4.9.0: v4.9

Compare Source

Welcome to gatsby@4.9.0 release (March 2022 #1)

Key highlights of this release:

Also check out notable bugfixes.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

Full changelog

v4.8.2

Compare Source

v4.8.1

Compare Source

v4.8.0: v4.8

Compare Source

Welcome to gatsby@4.8.0 release (February 2022 #2)

Key highlights of this release:

Also check out notable bugfixes.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know
if you have any issues.

Previous release notes

Full changelog

v4.7.2

Compare Source

v4.7.1

Compare Source

v4.7.0: v4.7

Compare Source

Welcome to gatsby@4.7.0 release (February 2022 #1)

Key highlights of this release:

Also check out notable bugfixes.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know
if you have any issues.

Previous release notes

Full changelog

v4.6.2

Compare Source

v4.6.1

Compare Source

v4.6.0: v4.6

Compare Source

Welcome to gatsby@4.6.0 release (January 2022 #2)

Key highlights of this release:

Also check out notable bugfixes.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know
if you have any issues.

Previous release notes

Full changelog

v4.5.5

Compare Source

v4.5.4

Compare Source

v4.5.3

Compare Source

v4.5.2

Compare Source

v4.5.1

Compare Source

v4.5.0: v4.5

Compare Source

Welcome to gatsby@4.5.0 release (January 2022 #1)

Key highlights of this release:

Also check out notable bugfixes.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know
if you have any issues.

Previous release notes

Full changelog

v4.4.0: v4.4

Compare Source

Welcome to gatsby@4.4.0 release (December 2021 #1)

Key highlights of this release:

Also check out notable bugfixes.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know
if you have any issues.

Previous release notes

Full changelog

v4.3.0: v4.3

Compare Source

Welcome to gatsby@4.3.0 release (November 2021 #​3)

Key highlights of this release:

Also check out notable bugfixes.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know
if you have any issues.

Previous release notes

Full changelog

v4.2.0: v4.2

Compare Source

Welcome to gatsby@4.2.0 release (November 2021 #2).

Key highlights of this release:

Also check out notable bugfixes.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know
if you have any issues.

Previous release notes

Full changelog

v4.1.6

Compare Source

v4.1.5

Compare Source

v4.1.4

Compare Source

v4.1.3

Compare Source

v4.1.2

Compare Source

v4.1.1

Compare Source

v4.1.0: v4.1

Compare Source

Welcome to gatsby@4.1.0 release (November 2021 #1).

Key highlights of this release:

Also check out notable bugfixes.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know
if you have any issues.

Previous release notes

Full changelog

v4.0.2

Compare Source

v4.0.1

Compare Source

v4.0.0: v4.0.0

Compare Source

Welcome to gatsby@4.0.0 release (October 2021 #1).

We've released Gatsby 3 in March 2021 and now have a lot of exciting new features for Gatsby 4!
We’ve tried to make migration smooth. Please refer to the migration guide
and let us know if you encounter any issues when migrating.

Key highlights of this release:

Also check out notable bugfixes and improvements.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know
if you have any issues.

Previous release notes for 3.14

Full changelog

v3.15.0

Compare Source

v3.14.6

Compare Source

v3.14.5

Compare Source

v3.14.4

Compare Source

v3.14.3

Compare Source

v3.14.2

Compare Source

v3.14.1

Compare Source

v3.14.0: v3.14 (September 2021 #​1)

Compare Source

Welcome to gatsby@3.14.0 release (September 2021 #1)

This is the final minor release for gatsby v3. Gatsby v4 beta is already published behind the next npm tag and the next stable release will be gatsby@4.0.0. See what's inside!

We will keep publishing patches for 3.14.x with hotfixes until 4.0.0 stable is published and at least several weeks after.

Key highlights of this release:

Also, check out notable bugfixes.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know
if you have any issues.

Previous release notes

Full changelog

v3.13.1

Compare Source

v3.13.0: v3.13 (August 2021 #​3)

Compare Source

Welcome to gatsby@3.13.0 release (August 2021 #3)

Key highlights of this release:

Also check out notable bugfixes.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know
if you have any issues.

Previous release notes

Full changelog

v3.12.1

Compare Source

v3.12.0: v3.12 (August 2021 #​2)

Compare Source

Welcome to gatsby@3.12.0 release (August 2021 #2)

Key highlights of this release:

Also check out notable bugfixes.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know
if you have any issues.

Previous release notes

Full changelog

v3.11.1

Compare Source

v3.11.0: v3.11 (August 2021 #​1)

Compare Source

Welcome to gatsby@3.11.0 release (August 2021 #​1)

Key highlights of this release:

Also check out notable bugfixes.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know
if you have any issues.

Previous release notes

Full changelog

v3.10.2

Compare Source

v3.10.1

Compare Source

v3.10.0: v3.10 (July 2021 #​2)

Compare Source

Welcome to gatsby@3.10.0 release (July 2021 #​2)

Key highlights of this release:

Also check out notable bugfixes.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know
if you have any issues.

Previous release notes

Full changelog

v3.9.1

Compare Source

v3.9.0: v3.9 (July 2021 #​1)

Compare Source

Welcome to gatsby@3.9.0 release (July 2021 #​1)

Key highlights of this release:

Also check out notable bugfixes.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know
if you have any issues.

Previous release notes

Full changelog

v3.8.1

Compare Source

v3.8.0: v3.8 (June 2021 #​2)

Compare Source

Welcome to gatsby@3.8.0 release (June 2021 #2)

Key highlights of this release:


Configuration

📅 Schedule: Branch creation - "" (UTC), 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 has been generated by Mend Renovate. View repository job log here.

@codecov
Copy link

codecov bot commented Jun 10, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.82%. Comparing base (d6a81c4) to head (cf77c36).
Report is 1 commits behind head on master.

Current head cf77c36 differs from pull request most recent head 1d689e5

Please upload reports for the commit 1d689e5 to get more accurate results.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #117   +/-   ##
=======================================
  Coverage   93.82%   93.82%           
=======================================
  Files          14       14           
  Lines         356      356           
  Branches       81       81           
=======================================
  Hits          334      334           
  Misses         21       21           
  Partials        1        1           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from 19c9ead to f1d6439 Compare June 13, 2023 16:22
@renovate renovate bot changed the title fix(deps): update dependency gatsby to v4 [security] fix(deps): update dependency gatsby to v5 [security] Jun 13, 2023
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from f1d6439 to 7c3a9c6 Compare June 13, 2023 19:05
@renovate renovate bot changed the title fix(deps): update dependency gatsby to v5 [security] fix(deps): update dependency gatsby to v4 [security] Jun 13, 2023
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from 7c3a9c6 to d500026 Compare June 18, 2023 06:31
@renovate renovate bot changed the title fix(deps): update dependency gatsby to v4 [security] fix(deps): update dependency gatsby to v5 [security] Jun 18, 2023
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from d500026 to 0b98281 Compare June 18, 2023 10:53
@renovate renovate bot changed the title fix(deps): update dependency gatsby to v5 [security] fix(deps): update dependency gatsby to v4 [security] Jun 18, 2023
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from 0b98281 to 26deda7 Compare June 19, 2023 07:23
@renovate renovate bot changed the title fix(deps): update dependency gatsby to v4 [security] fix(deps): update dependency gatsby to v5 [security] Jun 19, 2023
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from 26deda7 to 4f5d1cf Compare June 19, 2023 13:32
@renovate renovate bot changed the title fix(deps): update dependency gatsby to v5 [security] fix(deps): update dependency gatsby to v4 [security] Jun 19, 2023
@renovate renovate bot changed the title fix(deps): update dependency gatsby to v4 [security] fix(deps): update dependency gatsby to v5 [security] Jun 29, 2023
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from 4f5d1cf to ebe9f6f Compare June 29, 2023 08:15
@renovate renovate bot changed the title fix(deps): update dependency gatsby to v5 [security] fix(deps): update dependency gatsby to v4 [security] Jun 29, 2023
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from ebe9f6f to d5a75bf Compare June 29, 2023 12:00
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from d5a75bf to 70510f9 Compare July 6, 2023 14:59
@renovate renovate bot changed the title fix(deps): update dependency gatsby to v4 [security] fix(deps): update dependency gatsby to v5 [security] Jul 6, 2023
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from 70510f9 to 757cc88 Compare July 6, 2023 20:03
@renovate renovate bot changed the title fix(deps): update dependency gatsby to v5 [security] fix(deps): update dependency gatsby to v4 [security] Jul 6, 2023
@renovate renovate bot changed the title fix(deps): update dependency gatsby to v4 [security] fix(deps): update dependency gatsby to v5 [security] Jul 9, 2023
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch 2 times, most recently from dbd3423 to 41c04d2 Compare July 9, 2023 13:02
@renovate renovate bot changed the title fix(deps): update dependency gatsby to v5 [security] fix(deps): update dependency gatsby to v4 [security] Jul 9, 2023
@renovate renovate bot changed the title fix(deps): update dependency gatsby to v4 [security] fix(deps): update dependency gatsby to v5 [security] Jul 16, 2023
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from 41c04d2 to 06ef82f Compare July 16, 2023 13:53
@renovate renovate bot changed the title fix(deps): update dependency gatsby to v5 [security] fix(deps): update dependency gatsby to v4 [security] Jul 16, 2023
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from 06ef82f to 235b9f8 Compare July 16, 2023 17:22
@renovate renovate bot changed the title fix(deps): update dependency gatsby to v4 [security] fix(deps): update dependency gatsby to v5 [security] Jul 19, 2023
@renovate renovate bot changed the title fix(deps): update dependency gatsby to v5 [security] fix(deps): update dependency gatsby to v4 [security] Apr 14, 2024
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from 7462f80 to e195fdc Compare April 21, 2024 11:48
@renovate renovate bot changed the title fix(deps): update dependency gatsby to v4 [security] fix(deps): update dependency gatsby to v5 [security] Apr 21, 2024
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from e195fdc to 3e74c54 Compare April 21, 2024 12:17
@renovate renovate bot changed the title fix(deps): update dependency gatsby to v5 [security] fix(deps): update dependency gatsby to v4 [security] Apr 21, 2024
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from 3e74c54 to 7a9d1b0 Compare April 25, 2024 08:12
@renovate renovate bot changed the title fix(deps): update dependency gatsby to v4 [security] fix(deps): update dependency gatsby to v5 [security] Apr 25, 2024
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from 7a9d1b0 to 2f06aa2 Compare April 25, 2024 09:47
@renovate renovate bot changed the title fix(deps): update dependency gatsby to v5 [security] fix(deps): update dependency gatsby to v4 [security] Apr 25, 2024
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from 2f06aa2 to b3fd069 Compare May 1, 2024 11:10
@renovate renovate bot changed the title fix(deps): update dependency gatsby to v4 [security] fix(deps): update dependency gatsby to v5 [security] May 1, 2024
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from b3fd069 to 5f651f0 Compare May 1, 2024 12:47
@renovate renovate bot changed the title fix(deps): update dependency gatsby to v5 [security] fix(deps): update dependency gatsby to v4 [security] May 1, 2024
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from 5f651f0 to a9ec772 Compare May 9, 2024 10:56
@renovate renovate bot changed the title fix(deps): update dependency gatsby to v4 [security] fix(deps): update dependency gatsby to v5 [security] May 9, 2024
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from a9ec772 to e466e09 Compare May 9, 2024 12:38
@renovate renovate bot changed the title fix(deps): update dependency gatsby to v5 [security] fix(deps): update dependency gatsby to v4 [security] May 9, 2024
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from e466e09 to 28aa1de Compare May 15, 2024 17:03
@renovate renovate bot changed the title fix(deps): update dependency gatsby to v4 [security] fix(deps): update dependency gatsby to v5 [security] May 15, 2024
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from 28aa1de to c2914be Compare May 16, 2024 00:09
@renovate renovate bot changed the title fix(deps): update dependency gatsby to v5 [security] fix(deps): update dependency gatsby to v4 [security] May 16, 2024
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from c2914be to 2963553 Compare June 4, 2024 13:32
@renovate renovate bot changed the title fix(deps): update dependency gatsby to v4 [security] fix(deps): update dependency gatsby to v5 [security] Jun 4, 2024
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from 2963553 to 51e8c73 Compare June 4, 2024 16:58
@renovate renovate bot changed the title fix(deps): update dependency gatsby to v5 [security] fix(deps): update dependency gatsby to v4 [security] Jun 4, 2024
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from 51e8c73 to fa3ddd8 Compare June 27, 2024 10:19
@renovate renovate bot changed the title fix(deps): update dependency gatsby to v4 [security] fix(deps): update dependency gatsby to v5 [security] Jun 27, 2024
@renovate renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from fa3ddd8 to 1d689e5 Compare June 27, 2024 12:02
@renovate renovate bot changed the title fix(deps): update dependency gatsby to v5 [security] fix(deps): update dependency gatsby to v4 [security] Jun 27, 2024
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.

None yet

0 participants