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

[New Snap] D3 Connect #698

Closed
2 of 7 tasks
Montoya opened this issue Jul 16, 2024 · 1 comment · Fixed by #831
Closed
2 of 7 tasks

[New Snap] D3 Connect #698

Montoya opened this issue Jul 16, 2024 · 1 comment · Fixed by #831

Comments

@Montoya
Copy link
Contributor

Montoya commented Jul 16, 2024

Checklist

All items in the list below needs to be satisfied.

  • Is the Snap repository publicly accessible and linked in this ticket? https://github.com/d3-inc/d3-connect-snap/
  • Is the Snap distributed on npm and linked in this ticket? https://www.npmjs.com/package/@d3-inc/d3connect-snap
  • Has an audit been performed and the audit report attached or linked in this issue? An audit is not required for this Snap
  • Is a complete list of discovered vulnerabilities from the audit documented in this issue?
  • For vulnerabilities that have been deemed necessary to be addressed, are the links to the fixes attached to this issue?
  • For vulnerabilities that have been deemed not necessary to be addressed, is a reason for each of them documented in this issue?
  • The corresponding pull request in this repo has been merged.
@Montoya
Copy link
Contributor Author

Montoya commented Jul 16, 2024

The version to be allowlisted is 0.3.1

This Snap uses the domain resolution feature which is not live yet. This allowlist request is on hold.

FrederikBolding added a commit that referenced this issue Oct 21, 2024
Closes: #698

---------

Co-authored-by: Mario Christopher <[email protected]>
Co-authored-by: Frederik Bolding <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant