Skip to content

chore(deps): update dependency dotenv to v16.6.1#38

Open
Magi3r wants to merge 1 commit into
mainfrom
renovate/dotenv-16.x-lockfile
Open

chore(deps): update dependency dotenv to v16.6.1#38
Magi3r wants to merge 1 commit into
mainfrom
renovate/dotenv-16.x-lockfile

Conversation

@Magi3r

@Magi3r Magi3r commented Jun 26, 2025

Copy link
Copy Markdown
Owner

This PR contains the following updates:

Package Type Update Change
dotenv dependencies minor 16.5.0 -> 16.6.1

Release Notes

motdotla/dotenv (dotenv)

v16.6.1

Compare Source

Changed
  • Default quiet to true – hiding the runtime log message (#​874)
  • NOTICE: 17.0.0 will be released with quiet defaulting to false. Use config({ quiet: true }) to suppress.
  • And check out the new dotenvx. As coding workflows evolve and agents increasingly handle secrets, encrypted .env files offer a much safer way to deploy both agents and code together with secure secrets. Simply switch require('dotenv').config() for require('@​dotenvx/dotenvx').config().

v16.6.0

Compare Source

Added
  • Default log helpful message [dotenv@16.6.0] injecting env (1) from .env (#​870)
  • Use { quiet: true } to suppress
  • Aligns dotenv more closely with dotenvx.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@Magi3r Magi3r changed the title chore(deps): update dependency dotenv to v16.6.0 chore(deps): update dependency dotenv to v16.6.1 Jun 27, 2025
@Magi3r
Magi3r force-pushed the renovate/dotenv-16.x-lockfile branch from 520a500 to 2987242 Compare September 20, 2025 22:03
@Magi3r

Magi3r commented Oct 23, 2025

Copy link
Copy Markdown
Owner Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml
undefined

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants