Merge pull request #72 from dequelabs/release

chore(release): 3.1.0

.eslintrc.js

@@ -0,0 +1,29 @@
+module.exports = {
+  env: {
+    browser: true,
+    es6: true,
+    node: true,
+    webextensions: true,
+  },
+  extends: [
+    'eslint:recommended',
+    'plugin:@typescript-eslint/eslint-recommended',
+    'plugin:@typescript-eslint/recommended',
+    'prettier',
+  ],
+  plugins: ['eslint-plugin-import', '@typescript-eslint'],
+  root: true,
+  rules: {
+    '@typescript-eslint/no-explicit-any': 'off',
+    'comma-dangle': 0
+  },
+  overrides: [
+    {
+      files: ['*.ts'],
+      parser: '@typescript-eslint/parser',
+      parserOptions: {
+        project: './tsconfig.json',
+      },
+    },
+  ],
+}

CHANGELOG.md

@@ -2,17 +2,26 @@
 
 All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.
 
-## [3.0.0](https://github.com/dequelabs/puppeteer-devtools/compare/v2.0.1...v3.0.0) (2022-02-10)
+## [3.1.0](https://github.com/dequelabs/puppeteer-devtools/compare/v3.0.0...v3.1.0) (2023-07-13)
+
+### Features
+
+- upgrade puppeteer to 14.1.1 ([#70](https://github.com/dequelabs/puppeteer-devtools/issues/70)) ([56abb8d](https://github.com/dequelabs/puppeteer-devtools/commit/56abb8d8769a37f4eca346bac15d66c34bb28ffd))
 
+### Bug Fixes
+
+- correct puppeteer imports ([#71](https://github.com/dequelabs/puppeteer-devtools/issues/71)) ([da93565](https://github.com/dequelabs/puppeteer-devtools/commit/da935658143d6c90dabc901ad493205346d322f3))
+
+## [3.0.0](https://github.com/dequelabs/puppeteer-devtools/compare/v2.0.1...v3.0.0) (2022-02-10)
 
 ### ⚠ BREAKING CHANGES
 
-* Updates internal method used to access/control extension panels, rolling to puppeteer@^9
+- Updates internal method used to access/control extension panels, rolling to puppeteer@^9
 
 ### Features
 
-* supports getting background page ([#55](https://github.com/dequelabs/puppeteer-devtools/issues/55)) ([65881a1](https://github.com/dequelabs/puppeteer-devtools/commit/65881a1e5f891e5fe4163b574da40aa73e1fa161))
-* update puppeteer to 9.1.1 ([#50](https://github.com/dequelabs/puppeteer-devtools/issues/50)) ([8390e70](https://github.com/dequelabs/puppeteer-devtools/commit/8390e70d8384cc0e3c306dae4bf0debcca85e7e9))
+- supports getting background page ([#55](https://github.com/dequelabs/puppeteer-devtools/issues/55)) ([65881a1](https://github.com/dequelabs/puppeteer-devtools/commit/65881a1e5f891e5fe4163b574da40aa73e1fa161))
+- update puppeteer to 9.1.1 ([#50](https://github.com/dequelabs/puppeteer-devtools/issues/50)) ([8390e70](https://github.com/dequelabs/puppeteer-devtools/commit/8390e70d8384cc0e3c306dae4bf0debcca85e7e9))
 
 ### [2.0.1](https://github.com/dequelabs/puppeteer-devtools/compare/v2.0.0...v2.0.1) (2021-04-02)
 

SECURITY.md

@@ -0,0 +1,31 @@
+## Security
+
+Deque takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organization [Dequelabs](https://github.com/dequelabs).
+
+If you believe you have found a security vulnerability in any Deque-owned repository that meets [Deque's definition of a security vulnerability](https://aka.ms/opensource/security/definition), please report it to us as described below.
+
+## Reporting Security Issues
+
+**Please do not report security vulnerabilities through public GitHub issues.**
+
+Instead, email them to Deque Security at [security@deque.com](mailto:security@deque.com).
+
+You should receive a response within 24 business hours. If for some reason you do not, please follow up via email to ensure we received your original message.
+
+Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:
+
+  * Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
+  * Full paths of source file(s) related to the manifestation of the issue
+  * The location of the affected source code (tag/branch/commit or direct URL)
+  * Any special configuration required to reproduce the issue (e.g. OS, browser, settings, options etc.)
+  * Step-by-step instructions to reproduce the issue
+  * Proof-of-concept or exploit code (if possible)
+  * Impact of the issue, including how an attacker might exploit the issue
+
+This information will help us triage your report more quickly.
+
+We currently do not have a bug bounty program.
+
+## Preferred Languages
+
+We prefer all communications to be in English.

code_of_conduct.md

@@ -0,0 +1,17 @@
+## Introduction
+
+Deque is committed to providing a safe, inclusive, and welcoming virtual environment for contributors.
+
+We created this policy not because we anticipate bad behavior, but because we believe that articulating our values and obligations to one another reinforces a level of respect among contributors and because having a code of conduct provides us with clear avenues to correct our virtual culture should it ever stray from that course.
+
+## Code of Conduct Policy
+
+We expect all contributors to Deque open-source projects to uphold the principles of this Code of Conduct. We do not tolerate disruptive or disrespectful behavior, messages, images, or interactions by any participant, in any form.
+
+We will not tolerate harassment or discrimination based on age, ancestry, color, gender identity or expression, national origin, physical or mental disability, religion, sexual orientation, or any other characteristic.
+
+## Enforcement and Reporting
+
+Contributors asked to stop any harassing behavior are expected to comply immediately; regardless, Deque reserves the right to remove or block anyone from any repository at the discretion of Deque employees.
+
+If you have any concerns, please contact a code-owner or other Deque employee via direct message on the [axe Community Slack](https://accessibility.deque.com/axe-community) with details about the nature of the concern.