Skip to content

chore(cloudflare): use node parseEnv instead of dotenv#15447

Merged
ematipico merged 1 commit intomainfrom
chore/cf-parse-env
Feb 9, 2026
Merged

chore(cloudflare): use node parseEnv instead of dotenv#15447
ematipico merged 1 commit intomainfrom
chore/cf-parse-env

Conversation

@florian-lefebvre
Copy link
Member

Changes

  • Instead of using dotenv, we now use the built-in parseEnv utility available in node

Testing

Should pass

Docs

N/A, internal change

@florian-lefebvre florian-lefebvre self-assigned this Feb 9, 2026
@changeset-bot
Copy link

changeset-bot bot commented Feb 9, 2026

⚠️ No Changeset found

Latest commit: a6b9777

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@github-actions github-actions bot added the pkg: integration Related to any renderer integration (scope) label Feb 9, 2026
@ematipico ematipico merged commit 690ebea into main Feb 9, 2026
23 checks passed
@ematipico ematipico deleted the chore/cf-parse-env branch February 9, 2026 09:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pkg: integration Related to any renderer integration (scope)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments