Skip to content

doc: mark --env-file and --env-file-if-exists as stable - #59925

Merged
aduh95 merged 3 commits into
nodejs:mainfrom
Hilzu:stabilize-env-file
Oct 3, 2025
Merged

doc: mark --env-file and --env-file-if-exists as stable#59925
aduh95 merged 3 commits into
nodejs:mainfrom
Hilzu:stabilize-env-file

Conversation

@Hilzu

@HilzuHilzu commented Sep 18, 2025

Copy link
Copy Markdown
Contributor

As discussed in #49148 (comment) the feature should be ready to be marked stable.

The change could probably be picked to v24 and be featured in the change log.

This is my first time contributing to node so let me know if there's any mistakes.

@nodejs-github-botnodejs-github-bot added the doc Issues and PRs related to the documentations. label Sep 18, 2025
As discussed in the referenced issue the feature should be ready to be
marked as stable.
Refs: nodejs#49148 (comment)
Comment threaddoc/api/cli.md Outdated
Comment threaddoc/api/cli.md Outdated
@aduh95aduh95 added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Sep 23, 2025
@aduh95

Copy link
Copy Markdown
Contributor

Would it make sense to mark as stable process.loadEnvFile and util.parseEnv as well?

@Hilzu

Copy link
Copy Markdown
ContributorAuthor

To me it makes sense at least. I'll create a commit marking those as stable as well. The people that know the env system better can comment if it should be included or not.

@anonriganonrig added the request-ci Add this label to start a Jenkins CI on a PR. label Sep 24, 2025
@github-actionsgithub-actionsBot added request-ci-failed An error occurred while starting CI via request-ci label, and manual interventon is needed. and removed request-ci Add this label to start a Jenkins CI on a PR. labels Sep 24, 2025
@github-actions

Copy link
Copy Markdown
Contributor
Failed to start CI
 ⚠ Commits were pushed since the last approving review:
⚠ - doc: mark --env-file and --env-file-if-exists as stable
⚠ - doc: use correct terminology for newly stable feature
⚠ - doc: mark `process.loadEnvFile` and `util.parseEnv` as stable
✘ Refusing to run CI on potentially unsafe PR
https://github.com/nodejs/node/actions/runs/17975693366

@anonriganonrig added request-ci Add this label to start a Jenkins CI on a PR. and removed request-ci-failed An error occurred while starting CI via request-ci label, and manual interventon is needed. labels Sep 24, 2025
@github-actionsgithub-actionsBot removed the request-ci Add this label to start a Jenkins CI on a PR. label Sep 24, 2025
@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@aduh95

Copy link
Copy Markdown
Contributor

@anonrig doc-only PRs do not need a Jenkins CI run FYI

@Hilzu

Hilzu commented Oct 3, 2025

Copy link
Copy Markdown
ContributorAuthor

The failed CI run is most likely flaky and shouldn't be relevant for this PR as it is just a documentation update. Is there anything else I need to do or is this just waiting to land?

@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@aduh95
aduh95 merged commit bb04959 into nodejs:mainOct 3, 2025
51 of 54 checks passed
@aduh95

Copy link
Copy Markdown
Contributor

Landed in bb04959

targos pushed a commit that referenced this pull request Oct 6, 2025
As discussed in the referenced issue the feature should be ready to be
marked as stable.
Refs: #49148 (comment)
PR-URL: #59925
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>
aduh95 pushed a commit that referenced this pull request Oct 11, 2025
As discussed in the referenced issue the feature should be ready to be
marked as stable.
Refs: #49148 (comment)
PR-URL: #59925
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>
aduh95 pushed a commit that referenced this pull request Oct 11, 2025
As discussed in the referenced issue the feature should be ready to be
marked as stable.
Refs: #49148 (comment)
PR-URL: #59925
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author readyPRs that have at least one approval, no pending requests for changes, and a CI started.docIssues and PRs related to the documentations.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants

@Hilzu@aduh95@nodejs-github-bot@lpinca@anonrig@aymen94@gurgunday