Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
build(deps): bump @nestjs/config from 3.3.0 to 4.0.0 (#1638)
Bumps [@nestjs/config](https://github.com/nestjs/config) from 3.3.0 to 4.0.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/nestjs/config/releases"><code>@nestjs/config</code>'s releases</a>.</em></p> <blockquote> <h2>Release 4.0.0</h2> <h4>Breaking changes</h4> <p>The order in which configuration variables are read by the <code>ConfigService#get</code> method has been updated. The new order is:</p> <ul> <li>Internal configuration (config namespaces and custom config files)</li> <li>Validated environment variables (if validation is enabled and a schema is provided)</li> <li>The <code>process.env</code> object</li> </ul> <p>Previously, validated environment variables and the <code>process.env</code> object were read first, preventing them from being overridden by internal configuration. With this update, internal configuration will now always take precedence over environment variables.</p> <p>Additionally, the <code>ignoreEnvVars</code> configuration option, which previously allowed disabling validation of the <code>process.env</code> object, has been deprecated. Instead, use the <code>validatePredefined</code> option (set to <code>false</code> to disable validation of predefined environment variables). Predefined environment variables refer to <code>process.env</code> variables that were set before the module was imported. For example, if you start your application with <code>PORT=3000 node main.js</code>, the <code>PORT</code> variable is considered predefined. However, variables loaded by the <code>ConfigModule</code> from a <code>.env</code> file are not classified as predefined.</p> <p>A new <code>skipProcessEnv</code> option has also been introduced. This option allows you to prevent the <code>ConfigService#get</code> method from accessing the <code>process.env</code> object entirely, which can be helpful when you want to restrict the service from reading environment variables directly.</p> <h4>Changelog</h4> <ul> <li>chore: update config attributes to more self descriptive names (c2eaf04)</li> <li>chore(deps): update nest monorepo to v11 (1c20713)</li> <li>feat: order of reading variables, add skip predefined (c53c63c)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/nestjs/config/commit/163a4a8da0ad8296c581d3ccdde03da2fc3d392f"><code>163a4a8</code></a> chore(): release v4.0.0</li> <li><a href="https://github.com/nestjs/config/commit/c2eaf04c89a99b8aea24de95acc0c93cf59eaf9c"><code>c2eaf04</code></a> chore: update config attributes to more self descriptive names</li> <li><a href="https://github.com/nestjs/config/commit/ce18cb8718fa37c78542aeac943350e0b2a20b23"><code>ce18cb8</code></a> Merge branch 'master' into next</li> <li><a href="https://github.com/nestjs/config/commit/49c13fc8554406aae5f4c727629050700d698a99"><code>49c13fc</code></a> test: update integration test to use new dotenv-expand opts</li> <li><a href="https://github.com/nestjs/config/commit/a1225dbf29f2fa07fc1fbad74b532325b53ec88b"><code>a1225db</code></a> chore: upgrade eslint, update deps, ci setup</li> <li><a href="https://github.com/nestjs/config/commit/1c54dde2525745eeb14f7299abc623036c0b8dde"><code>1c54dde</code></a> Merge pull request <a href="https://github.com/nestjs/config/issues/1919">#1919</a> from foxadb/refactor-missing-return-types</li> <li><a href="https://github.com/nestjs/config/commit/6411b7d8f977835e73a689cc8ab6ab4731c6f730"><code>6411b7d</code></a> Merge pull request <a href="https://github.com/nestjs/config/issues/1925">#1925</a> from nestjs/renovate/major-nest-monorepo</li> <li><a href="https://github.com/nestjs/config/commit/e9c87273f02871816a344fff1871e1c13a598ae7"><code>e9c8727</code></a> Merge pull request <a href="https://github.com/nestjs/config/issues/1883">#1883</a> from nestjs/feat/skip-predefined-change-order</li> <li><a href="https://github.com/nestjs/config/commit/94852a51ca935e39052e6d41a21744e1ce89e2c6"><code>94852a5</code></a> chore(deps): update dependency lint-staged to v15.4.1 (<a href="https://github.com/nestjs/config/issues/1926">#1926</a>)</li> <li><a href="https://github.com/nestjs/config/commit/49eec577213a450ae1120927ec3542ca5af18087"><code>49eec57</code></a> chore(deps): update dependency lint-staged to v15.4.0 (<a href="https://github.com/nestjs/config/issues/1924">#1924</a>)</li> <li>Additional commits viewable in <a href="https://github.com/nestjs/config/compare/3.3.0...4.0.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=@nestjs/config&package-manager=npm_and_yarn&previous-version=3.3.0&new-version=4.0.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details>
- Loading branch information