ueberdb2 4.0.17 → 4.1.2

package/package.json

@@ -63,10 +63,13 @@
     "url": "https://github.com/ether/ueberDB.git"
   },
   "main": "./dist/index",
-  "version": "4.0.17",
+  "version": "4.1.2",
   "bugs": {
     "url": "https://github.com/ether/ueberDB/issues"
   },
+  "files": [
+    "dist"
+  ],
   "homepage": "https://github.com/ether/ueberDB",
   "scripts": {
     "lint": "eslint .",

package/.eslintignore

@@ -1,2 +0,0 @@
-dist
-**/*.ts

package/.eslintrc.cjs

@@ -1,66 +0,0 @@
-'use strict';
-
-// This is a workaround for https://github.com/eslint/eslint/issues/3458
-require('eslint-config-etherpad/patch/modern-module-resolution');
-
-module.exports = {
-  parserOptions: {
-    project: ['./tsconfig.json'],
-  },
-
-  root: true,
-  extends: 'etherpad/node',
-
-  rules: {
-    'mocha/no-exports': 'off',
-    '@typescript-eslint/no-unsafe-call': 'off',
-    'max-len': 'off',
-    '@typescript-eslint/restrict-template-expressions': 'off',
-    '@typescript-eslint/no-unsafe-member-access': 'off',
-    'n/no-missing-import': 'off',
-    'strict': 'off',
-    '@typescript-eslint/no-unsafe-return': 'off',
-    '@typescript-eslint/no-explicit-any': 'off',
-    '@typescript-eslint/no-unsafe-argument': 'off',
-    '@typescript-eslint/no-unsafe-assignment': 'off',
-    'prefer-arrow/prefer-arrow-functions': 'off',
-    '@typescript-eslint/await-thenable': 'off',
-    '@typescript-eslint/brace-style': 'off',
-    '@typescript-eslint/comma-spacing': 'off',
-    '@typescript-eslint/consistent-type-assertions': 'off',
-    '@typescript-eslint/consistent-type-definitions': 'off',
-    '@typescript-eslint/default-param-last': 'off',
-    '@typescript-eslint/dot-notation': 'off',
-    '@typescript-eslint/explicit-function-return-type': 'off',
-    '@typescript-eslint/explicit-member-accessibility': 'off',
-    'func-call-spacing': 'off',
-    '@typescript-eslint/no-floating-promises': 'off',
-    'camelcase': 'off',
-    'n/no-unpublished-import': 'off',
-    'n/no-unpublished-require': 'off',
-    'no-unused-vars': 'off',
-    '@typescript-eslint/no-unused-vars': 'off',
-    '@typescript-eslint/ban-ts-comment': 'off',
-    '@typescript-eslint/restrict-plus-operands': 'off',
-  },
-  overrides: [
-    {
-      files: [
-        'lib/**/*',
-        'databases/**/*',
-        'tests/**/*',
-      ],
-      extends: 'etherpad/tests/backend',
-      overrides: [
-        {
-          files: [
-            'lib/**/*',
-            'databases/**/*',
-            'tests/**/*',
-          ],
-
-        },
-      ],
-    },
-  ],
-};

package/.github/dependabot.yml

@@ -1,11 +0,0 @@
-version: 2
-updates:
-  - package-ecosystem: "github-actions"
-    directory: "/"
-    schedule:
-      interval: "daily"
-  - package-ecosystem: "npm"
-    directory: "/"
-    schedule:
-      interval: "daily"
-    versioning-strategy: "increase"

package/.github/workflows/npmpublish.yml

@@ -1,134 +0,0 @@
-name: Node.js Package
-
-on:
-  pull_request:
-  push:
-    branches:
-      - main
-      - master
-      - v[0-9]+
-
-jobs:
-  test:
-    runs-on: ubuntu-latest
-    services:
-      couchdb:
-        image: couchdb
-        ports:
-          - 5984:5984
-        env:
-          COUCHDB_USER: ueberdb
-          COUCHDB_PASSWORD: ueberdb
-      elasticsearch:
-        image: elasticsearch:7.17.3
-        ports:
-          - 9200:9200
-        env:
-          discovery.type: single-node
-      mongo:
-        image: mongo
-        ports:
-          - 27017:27017
-      mysql:
-        # The default authentication used in MySQL 8.0 isn't supported by the
-        # mysql npm package: https://github.com/mysqljs/mysql/issues/2002
-        image: mariadb
-        ports:
-          - 3306:3306
-        env:
-          MYSQL_ROOT_PASSWORD: password
-          MYSQL_USER: ueberdb
-          MYSQL_PASSWORD: ueberdb
-          MYSQL_DATABASE: ueberdb
-      postgres:
-        image: postgres
-        ports:
-          - 5432:5432
-        env:
-          POSTGRES_USER: ueberdb
-          POSTGRES_PASSWORD: ueberdb
-          POSTGRES_DB: ueberdb
-        options: >-
-          --health-cmd="pg_isready -d postgresql://ueberdb:ueberdb@127.0.0.1/ueberdb"
-          --health-interval=10s
-          --health-timeout=5s
-          --health-retries=5
-      redis:
-        image: redis
-        ports:
-          - 6379:6379
-    timeout-minutes: 10
-    steps:
-      - uses: actions/checkout@v3
-      - uses: actions/setup-node@v3
-        with:
-          node-version: 20
-      - run: npm ci
-      # Optional dependencies must be installed manually.
-      - run: npm i sqlite3
-
-      # Verify databases are reachable.
-      - name: MySQL client and server check
-        run: |
-          mysql --version &&
-          mysql -h 127.0.0.1 -u ueberdb -pueberdb -e "SHOW TABLES;" ueberdb
-      - name: PostgreSQL client and server check
-        run: |
-          psql --version &&
-          psql -d postgresql://ueberdb:ueberdb@127.0.0.1/ueberdb -c '\dt'
-
-      - run: npm test
-      - run: npm run lint
-
-  publish-npm:
-    if: github.event_name == 'push'
-    needs: test
-    runs-on: ubuntu-latest
-    steps:
-      -
-        uses: actions/checkout@v3
-        with:
-          fetch-depth: 0
-      -
-        uses: actions/setup-node@v3
-        with:
-          node-version: 20
-          registry-url: https://registry.npmjs.org/
-          cache: 'npm'
-      # This is required if the package has a prepare script that uses something
-      # in dependencies or devDependencies. This is also needed for bumping the
-      # version.
-      -
-        run: npm ci
-      -
-        name: Bump version (patch)
-        run: |
-          LATEST_TAG=$(git describe --tags --abbrev=0) || exit 1
-          NEW_COMMITS=$(git rev-list --count "${LATEST_TAG}"..) || exit 1
-          [ "${NEW_COMMITS}" -gt 0 ] || exit 0
-          git config user.name 'github-actions[bot]'
-          git config user.email '41898282+github-actions[bot]@users.noreply.github.com'
-          npm version patch
-          # Update the branch before pushing the tag in case the branch can't be
-          # fast-forwarded.
-          git push
-          git push --follow-tags
-      # `npm publish` must come after `git push` otherwise there is a race
-      # condition: If two PRs are merged back-to-back then master/main will be
-      # updated with the commits from the second PR before the first PR's
-      # workflow has a chance to push the commit generated by `npm version
-      # patch`. This causes the first PR's `git push` step to fail after the
-      # package has already been published, which in turn will cause all future
-      # workflow runs to fail because they will all attempt to use the same
-      # already-used version number. By running `npm publish` after `git push`,
-      # back-to-back merges will cause the first merge's workflow to fail but
-      # the second's will succeed.
-      -
-        run: npm run publish
-        env:
-          NODE_AUTH_TOKEN: ${{secrets.NPM_TOKEN}}
-      -
-        name: Add package to etherpad organization
-        run: npm access grant read-write etherpad:developers
-        env:
-          NODE_AUTH_TOKEN: ${{secrets.NPM_TOKEN}}

package/.travis.yml

@@ -1,46 +0,0 @@
-language: node_js
-
-node_js:
-  - 14
-
-services:
-  - docker
-  - mysql
-  - postgresql
-  - couchdb
-  - sqlite3
-  - redis
-  - cassandra
-  - elasticsearch
-  - mongodb
-  - rethinkdb
-
-before_install:
-  - mysql -e 'CREATE DATABASE ueberdb;'
-  - mysql -e 'CREATE USER "ueberdb"@"localhost" identified by "ueberdb";'
-  - mysql -e "ALTER DATABASE ueberdb CHARACTER SET utf8mb4 COLLATE utf8mb4_bin;"
-  - mysql -e "grant CREATE,ALTER,SELECT,INSERT,UPDATE,DELETE on ueberdb.* to 'ueberdb'@'localhost';"
-  - mysql -e "CREATE TABLE \`store\` (\`key\` varchar(100) COLLATE utf8mb4_bin NOT NULL DEFAULT '',\`value\` longtext COLLATE utf8mb4_bin NOT NULL,PRIMARY KEY (\`key\`)) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_bin;" ueberdb
-#  - cp /etc/rethinkdb/default.conf.sample /etc/rethinkdb/instances.d/instance1.conf
-
-#addons:
-#  rethinkdb: '2.3.4'
-
-# Brings in procedure required for creating large data set
-  - mysql ueberdb < test/lib/mysql.sql
-  - mysql ueberdb -e 'CALL generate_data();';
-  - psql -c 'create database ueberdb;' -U postgres
-#  - psql -c "grant CREATE,ALTER,SELECT,INSERT,UPDATE,DELETE on ueberdb.* to 'ueberdb'@'localhost';" -U postgres
-
-install:
-  - "export GIT_HASH=$(git rev-parse --verify --short HEAD)"
-
-jobs:
-  include:
-    - name: "Run the Backend tests"
-      install:
-        - "npm install"
-
-notifications:
-  email:
-    - john@mclear.co.uk

package/CHANGELOG.md

@@ -1,304 +0,0 @@
-# Notable Changes
-
-## v4.0.1
-
-Security fix:
-
-  * `getSub()` now returns `null` when it encounters a non-"own" property
-    (including `__proto__`) or any non-object while walking the given property
-    path. This should make it easier to avoid accidental prototype pollution
-    vulnerabilities.
-
-## v4.0.0
-
-Compatibility changes:
-
-  * `redis`: The `socket` and `client_options` settings, deprecated since
-    v1.3.1, have been removed.
-  * `redis`: The client configuration object has changed with the new version of
-    the `redis` client library. See the [`redis` client library
-    documentation](https://github.com/redis/node-redis/blob/redis%404.1.0/docs/client-configuration.md)
-    for details.
-
-Bug fixes:
-
-  * `redis`: Several `findKeys()` fixes.
-
-Updated database dependencies:
-
-  * `redis`: Updated `redis` from 3.1.2 to 4.1.0.
-
-## v3.0.2
-
-Security fix:
-
-  * `getSub()` now returns `null` when it encounters a non-"own" property
-    (including `__proto__`) or any non-object while walking the given property
-    path. This should make it easier to avoid accidental prototype pollution
-    vulnerabilities.
-
-## v3.0.1
-
-Bug fixes:
-
-  * Fixed `findKeys()` calls containing special regular expression characters
-    (applicable to the database drivers that use the glob-to-regex helper
-    function).
-
-## v3.0.0
-
-Compatibility changes:
-
-  * Minimum supported Node.js version is now 14.15.0.
-  * `elasticsearch`: New index name and mapping (schema). To automatically copy
-    existing data to the new index when the ueberdb client is initialized, set
-    the `migrate_to_newer_schema` option to `true`.
-  * As mentioned in the v2.2.0 changes, passing callbacks to the database
-    methods is deprecated. Use the returned Promises instead.
-  * `postgrespool`: As mentioned in the v1.4.15 changes, `postgrespool` is
-    deprecated. Use `postgres` instead.
-  * `redis`: As mentioned in the v1.3.1 changes, the `socket` and
-    `client_options` settings are deprecated. Pass the [client options
-    object](https://www.npmjs.com/package/redis/v/3.1.2#options-object-properties)
-    directly.
-
-Bug fixes:
-
-  * `elasticsearch`: Rewrote driver to fix numerous bugs and modernize the code.
-
-Updated database dependencies:
-
-  * `couch`: Updated `nano` to 10.0.0.
-  * `dirty_git`: Updated `simple-git` to 3.7.1.
-  * `elasticsearch`: Switched the client library from the deprecated
-    `elasticsearch` to `@elastic/elasticsearch` version 7.17.0.
-  * `postgres`: Updated `pg` to 8.7.3.
-  * `sqlite`: Updated `sqlite3` to 5.0.6.
-
-## v2.2.4
-
-Security fix:
-
-  * `getSub()` now returns `null` when it encounters a non-"own" property
-    (including `__proto__`) or any non-object while walking the given property
-    path. This should make it easier to avoid accidental prototype pollution
-    vulnerabilities.
-
-## v2.2.0
-
-Compatibility changes:
-
-  * Passing callbacks to the database methods is deprecated; use the returned
-    Promises instead.
-
-New features:
-
-  * Database methods now return a Promise if a callback is not provided.
-
-Bug fixes:
-
-  * A call to `flush()` immediately after a call to `set()`, `setSub()`, or
-    `remove()` (within the same ECMAScript macro- or microtask) now flushes the
-    new write operation.
-  * Fixed a bug where `findKeys()` would return stale results when write
-    buffering is enabled and writes are pending.
-  * `couch`: Rewrote driver to fix numerous bugs.
-
-## v2.1.1
-
-Security fix:
-
-  * Fix `setSub()` prototype pollution vulnerability.
-
-## v2.1.0
-
-  * `memory`: New `data` setting that allows users to supply the backing Map
-    object (rather than create a new Map).
-
-Updated database dependencies:
-
-  * `dirty_git`: Updated `simple-git` to 3.6.0.
-  * `mssql`: Updated `mssql` to 8.1.0.
-
-## v2.0.0
-
-* When saving an object that has a `.toJSON()` method, the value returned from
-  that method is saved to the database instead of the object itself. This
-  matches [the behavior of
-  `JSON.stringify()`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/JSON/stringify#tojson_behavior).
-  The `.toJSON()` method is used even if the chosen database driver never
-  actually converts anything to JSON.
-* New `memory` database driver that stores values in memory only.
-
-## v1.4.19
-
-Updated database (and other) dependencies:
-* `mongodb`: Updated `mongodb` to 3.7.3.
-* `mssql`: Updated `mssql` to 7.3.0.
-* `dirty_git`: Updated `simple-git` to 2.47.0.
-
-## v1.4.16
-
-* `postgres`: You can now provide a connection string instead of a settings
-  object. For example:
-  ```javascript
-  const db = new ueberdb.Database('postgres', 'postgres://user:password@host/dbname');
-  ```
-
-## v1.4.15
-
-* `postgres`, `postgrespool`: The `postgrespool` database driver was renamed to
-  `postgres`, replacing the old `postgres` driver. The old `postgrespool` name
-  is still usable, but is deprecated. For users of the old `postgres` driver,
-  this change increases the number of concurrent database connections. You may
-  need to increase your configured connection limit.
-* `sqlite`: Updated `sqlite3` to 5.0.2.
-
-## v1.4.14
-
-Updated dependencies:
-* `cassandra`: Updated `cassandra-driver` to 4.6.3.
-* `couch`: Updated `nano` to 9.0.3.
-* `dirty`: Updated `dirty` to 1.1.3.
-* `dirty_git`: Updated `simple-git` to 2.45.0.
-* `mongodb`: Updated `mongodb` to 3.6.11.
-* `mssql`: Updated `mssql` to 7.2.1.
-* `postgres`, `postgrespool`: Updated `pg` to 8.7.1.
-
-## v1.4.13
-
-* `mongodb`: The `dbName` setting has been renamed to `database` for consistency
-  with other database drivers. The `dbName` setting will continue to work (for
-  backwards compatibility), but it is deprecated and is ignored if `database` is
-  set.
-* `mongodb`: The `database` (formerly `dbName`) setting is now optional. If it
-  is not specified, the database name embedded in the `url` setting is used.
-
-## v1.4.8
-
-* `redis`: Updated `redis` dependency to 3.1.2.
-
-## v1.4.7
-
-* Each write operation in a bulk write batch is now retried if the bulk write
-  fails.
-* Fixed write metrics for `setSub()` read failures.
-
-## v1.4.6
-
-* `mysql`: Use a connection pool to improve performance and simplify the code.
-
-## v1.4.5
-
-* `mysql`: Reconnect on fatal error.
-* `mysql`: Log MySQL errors.
-
-## v1.4.4
-
-* New experimental setting to limit the number of operations written at a time
-  when flushing outstanding writes.
-* `mysql`: Bulk writes are limited to 100 changes at a time to avoid query
-  timeouts.
-* `mysql`: Raised default cache size from 500 entries to 10000.
-
-## v1.4.2
-
-* Refined the experimental read and write metrics.
-
-## v1.4.1
-
-* The two callback arguments in `remove()`, `set()`, and `setSub()` have
-  changed: Instead of a callback that is called after the write is buffered and
-  another callback that is called after the write is committed, both callbacks
-  are now called after the write is committed. Futhermore, the second callback
-  argument is now deprecated.
-* Modernized record locking.
-* Experimental metrics for reads, writes, and locking.
-
-## v1.3.2
-
-* `dirty`: Updated `dirty` dependency.
-
-## v1.3.1
-
-* `redis`: The database config object is now passed directly to the `redis`
-  package. For details, see
-  https://www.npmjs.com/package/redis/v/3.0.2#options-object-properties.
-  Old-style settings objects (where the `redis` options are in the
-  `client_options` property) are still supported but deprecated.
-
-## v1.2.9
-
-* `dirty`: Workaround for a bug in the upstream `dirty` driver.
-
-## v1.2.7
-
-* `redis`: Experimental support for passing the settings object directly to the
-  `redis` package.
-
-## v1.2.6
-
-* `redis`: Fixed "Callback was already called" exception during init.
-
-## v1.2.5
-
-* All: Fixed a major bug introduced in v1.1.10 that caused `setSub()` to
-  silently discard changes.
-* All: Fixed a bug that prevented cache entries from being marked as most
-  recently used.
-
-## v1.2.4
-
-* `mssql`: Updated `mssql` dependency.
-* `dirty_git`: Updated `simple-git` dependency.
-* `sqlite`: Updated `sqlite3` dependency.
-
-## v1.2.3
-
-* `mssql`: Updated `mssql` dependency.
-
-## v1.2.2
-
-* All: Fixed minor `setSub()` corner cases.
-
-## v1.2.1
-
-* New `flush()` method.
-* The `doShutdown()` method is deprecated. Use `flush()` instead.
-* The `close()` method now flushes unwritten entries before closing the database
-  connection.
-* Bug fix: `null`/`undefined` is no longer cached if there is an error reading
-  from the database.
-
-## v1.1.10
-
-* Major performance improvement: The caching logic was rewritten with much more
-  efficient algorithms. Also: Scans for entries to evict is performed less
-  often. Depending on your workload you might observe a slight memory usage
-  increase.
-
-## v1.1.7
-
-* `mysql` dependency bumped to 7.0.0-alpha4 to avoid a security vulnerability in
-  one of its indirect dependencies.
-
-## v1.1.6
-
-* Bug fix: When write buffering is disabled, reads of keys with values that were
-  changed but not yet written to the underlying database used to return the
-  previous value. Now the updated value is returned.
-* Minor performance improvement: Setting a key to the same value no longer
-  triggers a database write.
-
-## v1.1.5
-
-* Minor performance improvement: Debug log message strings are no longer
-  generated if debug logging is not enabled.
-
-## v1.1.1
-
-* The `database()` constructor is deprecated; use `Database()` instead.
-
-## Older
-
-See the Git history.

package/CONTRIBUTING.md

@@ -1,103 +0,0 @@
-# Contributor Guidelines
-(Please talk to people on the mailing list before you change this page, see our section on [how to get in touch](https://github.com/ether/etherpad-lite#get-in-touch))
-
-## Pull requests
-
-* the commit series in the PR should be _linear_ (it **should not contain merge commits**). This is necessary because we want to be able to [bisect](https://en.wikipedia.org/wiki/Bisection_(software_engineering)) bugs easily. Rewrite history/perform a rebase if necessary
-* PRs should be issued against the **develop** branch: we never pull directly into **master**
-* PRs **should not have conflicts** with develop. If there are, please resolve them rebasing and force-pushing
-* when preparing your PR, please make sure that you have included the relevant **changes to the documentation** (preferably with usage examples)
-* contain meaningful and detailed **commit messages** in the form:
-  ```
-  submodule: description
-
-  longer description of the change you have made, eventually mentioning the
-  number of the issue that is being fixed, in the form: Fixes #someIssueNumber
-  ```
-* if the PR is a **bug fix**:
-  * the first commit in the series must be a test that shows the failure
-  * subsequent commits will fix the bug and make the test pass
-  * the final commit message should include the text `Fixes: #xxx` to link it to its bug report
-* think about stability: code has to be backwards compatible as much as possible. Always **assume your code will be run with an older version of the DB/config file**
-* if you want to remove a feature, **deprecate it instead**:
-  * write an issue with your deprecation plan
-  * output a `WARN` in the log informing that the feature is going to be removed
-  * remove the feature in the next version
-* if you want to add a new feature, put it under a **feature flag**:
-  * once the new feature has reached a minimal level of stability, do a PR for it, so it can be integrated early
-  * expose a mechanism for enabling/disabling the feature
-  * the new feature should be **disabled** by default. With the feature disabled, the code path should be exactly the same as before your contribution. This is a __necessary condition__ for early integration
-* think of the PR not as something that __you wrote__, but as something that __someone else is going to read__. The commit series in the PR should tell a novice developer the story of your thoughts when developing it
-
-## How to write a bug report
-
-* Please be polite, we all are humans and problems can occur.
-* Please add as much information as possible, for example
-  * client os(s) and version(s)
-    * browser(s) and version(s), is the problem reproducible on different clients
-    * special environments like firewalls or antivirus
-  * host os and version
-    * npm and nodejs version
-    * Logfiles if available
-  * steps to reproduce
-  * what you expected to happen
-  * what actually happened
-* Please format logfiles and code examples with markdown see github Markdown help below the issue textarea for more information.
-
-## General goals of UeberDB
-To make sure everybody is going in the same direction:
-* easy to install for admins and easy to use for people
-* easy to integrate into other apps, but also usable as standalone
-* lightweight and scalable
-* extensible, as much functionality should be extendable with plugins so changes don't have to be done in core.
-
-## How to work with git?
-* Don't work in your master branch.
-* Make a new branch for every feature you're working on. (This ensures that you can work you can do lots of small, independent pull requests instead of one big one with complete different features)
-* Don't use the online edit function of github (this only creates ugly and not working commits!)
-* Try to make clean commits that are easy readable (including descriptive commit messages!)
-* Test before you push. Sounds easy, it isn't!
-* Don't check in stuff that gets generated during build or runtime
-* Make small pull requests that are easy to review but make sure they do add value by themselves / individually
-
-## Coding style
-* Do write comments. (You don't have to comment every line, but if you come up with something that's a bit complex/weird, just leave a comment. Bear in mind that you will probably leave the project at some point and that other people will read your code. Undocumented huge amounts of code are worthless!)
-* Never ever use tabs
-* Indentation: JS/CSS: 2 spaces; HTML: 4 spaces
-* Don't overengineer. Don't try to solve any possible problem in one step, but try to solve problems as easy as possible and improve the solution over time!
-* Do generalize sooner or later! (if an old solution, quickly hacked together, poses more problems than it solves today, refactor it!)
-* Keep it compatible. Do not introduce changes to the public API, db schema or configurations too lightly. Don't make incompatible changes without good reasons!
-* If you do make changes, document them! (see below)
-* Use protocol independent urls "//"
-
-## Branching model / git workflow
-see git flow http://nvie.com/posts/a-successful-git-branching-model/
-
-### `master` branch
-* the stable
-* This is the branch everyone should use for production stuff
-
-### feature branches (in your own repos)
-* these are the branches where you develop your features in
-* If it's ready to go out, it will be merged into develop
-
-Over the time we pull features from feature branches into the develop branch. Every month we pull from develop into master. Bugs in master get fixed in hotfix branches. These branches will get merged into master AND develop. There should never be commits in master that aren't in develop
-
-## Testing
-Front-end tests are found in the `tests/frontend/` folder in the repository. Run them by pointing your browser to `<yourdomainhere>/tests/frontend`.
-
-Back-end tests can be run via `npm test`.
-
-## Things you can help with
-The Etherpad Foundation is much more than software.  So if you aren't a developer then worry not, there is still a LOT you can do!  A big part of what we do is community engagement.  You can help in the following ways
- * Triage bugs (applying labels) and confirming their existence
- * Testing fixes (simply applying them and seeing if it fixes your issue or not) - Some git experience required
- * Notifying large site admins of new releases
- * Writing Changelogs for releases
- * Creating Windows packages
- * Creating releases
- * Bumping dependencies periodically and checking they don't break anything
- * Write proposals for grants
- * Co-Author and Publish CVEs
- * Work with SFC to maintain legal side of project
-

package/SECURITY.md

@@ -1,5 +0,0 @@
-# Security Policy
-
-## Reporting a Vulnerability
-
-Please email contact@etherpad.org to report security related issues.