@verdaccio/logger 6.0.0-6-next.44 → 7.0.0-next.1

package/CHANGELOG.md

@@ -1,5 +1,187 @@
 # @verdaccio/logger
 
+## 7.0.0-next.1
+
+### Patch Changes
+
+- @verdaccio/logger-commons@7.0.0-next.1
+
+## 7.0.0-next.0
+
+### Major Changes
+
+- feat!: bump to v7
+
+### Patch Changes
+
+- Updated dependencies
+  - @verdaccio/logger-commons@7.0.0-next.0
+
+## 6.0.0
+
+### Major Changes
+
+- 292c0a37f: feat!: replace deprecated request dependency by got
+
+  This is a big refactoring of the core, fetching dependencies, improve code, more tests and better stability. This is essential for the next release, will take some time but would allow modularize more the core.
+
+  ## Notes
+
+  - Remove deprecated `request` by other `got`, retry improved, custom Agent ( got does not include it built-in)
+  - Remove `async` dependency from storage (used by core) it was linked with proxy somehow safe to remove now
+  - Refactor with promises instead callback wherever is possible
+  - ~Document the API~
+  - Improve testing, integration tests
+  - Bugfix
+  - Clean up old validations
+  - Improve performance
+
+  ## 💥 Breaking changes
+
+  - Plugin API methods were callbacks based are returning promises, this will break current storage plugins, check documentation for upgrade.
+  - Write Tarball, Read Tarball methods parameters change, a new set of options like `AbortController` signals are being provided to the `addAbortSignal` can be internally used with Streams when a request is aborted. eg: `addAbortSignal(signal, fs.createReadStream(pathName));`
+  - `@verdaccio/streams` stream abort support is legacy is being deprecated removed
+  - Remove AWS and Google Cloud packages for future refactoring [#2574](https://github.com/verdaccio/verdaccio/pull/2574).
+
+- a3a209b5e: feat: migrate to pino.js 8
+- 794af76c5: Remove Node 12 support
+
+  - We need move to the new `undici` and does not support Node.js 12
+
+- 10aeb4f13: feat!: experiments config renamed to flags
+
+  - The `experiments` configuration is renamed to `flags`. The functionality is exactly the same.
+
+  ```js
+  flags: token: false;
+  search: false;
+  ```
+
+  - The `self_path` property from the config file is being removed in favor of `config_file` full path.
+  - Refactor `config` module, better types and utilities
+
+- e367c3f1e: - Replace signature handler for legacy tokens by removing deprecated crypto.createDecipher by createCipheriv
+
+  - Introduce environment variables for legacy tokens
+
+  ### Code Improvements
+
+  - Add debug library for improve developer experience
+
+  ### Breaking change
+
+  - The new signature invalidates all previous tokens generated by Verdaccio 4 or previous versions.
+  - The secret key must have 32 characters long.
+
+  ### New environment variables
+
+  - `VERDACCIO_LEGACY_ALGORITHM`: Allows to define the specific algorithm for the token signature which by default is `aes-256-ctr`
+  - `VERDACCIO_LEGACY_ENCRYPTION_KEY`: By default, the token stores in the database, but using this variable allows to get it from memory
+
+- 82cb0f2bf: feat!: config.logs throw an error, logging config not longer accept array or logs property
+
+  ### 💥 Breaking change
+
+  This is valid
+
+  ```yaml
+  log: { type: stdout, format: pretty, level: http }
+  ```
+
+  This is invalid
+
+  ```yaml
+  logs: { type: stdout, format: pretty, level: http }
+  ```
+
+  or
+
+  ```yaml
+  logs:
+    - [{ type: stdout, format: pretty, level: http }]
+  ```
+
+- b3e8438f6: logging prettifier only in development mode
+
+  - Verdaccio prettify `@verdaccio/logger-prettify` the logging which looks beautiful. But there are scenarios which does not make sense in production. This feature enables disable by default the prettifies if production `NODE_ENV` is enabled.
+  - Updates pino.js to `^6.7.0`.
+  - Suppress the warning when prettifier is enabled `suppressFlushSyncWarning`
+
+- 730b5d8cc: feat: upgrade to pino v7
+- 8f43bf17d: feat: node api new structure based on promise
+
+  ```js
+  import { runServer } from '@verdaccio/node-api';
+  // or
+  import { runServer } from 'verdaccio';
+
+  const app = await runServer(); // default configuration
+  const app = await runServer('./config/config.yaml');
+  const app = await runServer({ configuration });
+  app.listen(4000, (event) => {
+    // do something
+  });
+  ```
+
+  ### Breaking Change
+
+  If you are using the node-api, the new structure is Promise based and less arguments.
+
+### Minor Changes
+
+- ef88da3b4: feat: improve support for fs promises older nodejs
+- 631abe1ac: feat: refactor logger
+- b61f762d6: feat: add server rate limit protection to all request
+
+  To modify custom values, use the server settings property.
+
+  ```markdown
+  server:
+
+  ## https://www.npmjs.com/package/express-rate-limit#configuration-options
+
+  rateLimit:
+  windowMs: 1000
+  max: 10000
+  ```
+
+  The values are intended to be high, if you want to improve security of your server consider
+  using different values.
+
+- 154b2ecd3: refactor: remove @verdaccio/commons-api in favor @verdaccio/core and remove duplications
+- aa763baec: feat: add typescript project references settings
+
+  Reading https://ebaytech.berlin/optimizing-multi-package-apps-with-typescript-project-references-d5c57a3b4440 I realized I can use project references to solve the issue to pre-compile modules on develop mode.
+
+  It allows to navigate (IDE) trough the packages without need compile the packages.
+
+  Add two `tsconfig`, one using the previous existing configuration that is able to produce declaration files (`tsconfig.build`) and a new one `tsconfig` which is enables [_projects references_](https://www.typescriptlang.org/docs/handbook/project-references.html).
+
+- 6c1eb021b: feat: use warning codes for deprecation warnings
+
+### Patch Changes
+
+- e75c0a3b9: hydrate template placeholders in log messages when format is set to 'json'
+- 351aeeaa8: fix(deps): @verdaccio/utils should be a prod dep of local-storage
+- a610ef26b: chore: add release step to private regisry on merge changeset pr
+- 34f0f1101: Enable prerelease mode with **changesets**
+- b78f35257: Fix re-opening log files using SIGUSR2
+- 2c594910d: do not show deprecation warning on default logger config
+- 65f88b826: bump logger packages
+- 68ea21214: ESLint Warnings Fixed
+
+  Related to issue #1461
+
+  - max-len: most of the sensible max-len errors are fixed
+  - no-unused-vars: most of these types of errors are fixed by deleting not needed declarations
+  - @typescript-eslint/no-unused-vars: same as above
+
+- Updated dependencies [631abe1ac]
+- Updated dependencies [84b2dffdb]
+- Updated dependencies [65f88b826]
+- Updated dependencies [4a33e269b]
+  - @verdaccio/logger-commons@6.0.0
+
 ## 6.0.0-6-next.44
 
 ### Patch Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@verdaccio/logger",
-  "version": "6.0.0-6-next.44",
+  "version": "7.0.0-next.1",
   "description": "logger",
   "main": "./build/index.js",
   "types": "./build/index.d.ts",
@@ -29,11 +29,11 @@
     "node": ">=12"
   },
   "dependencies": {
-    "@verdaccio/logger-commons": "6.0.0-6-next.44",
+    "@verdaccio/logger-commons": "7.0.0-next.1",
     "pino": "8.14.1"
   },
   "devDependencies": {
-    "@verdaccio/types": "11.0.0-6-next.25"
+    "@verdaccio/types": "12.0.0-next.0"
   },
   "funding": {
     "type": "opencollective",