Skip to content

doc: add version when diagnostics_channel APIs were added - #40208

Closed
Flarna wants to merge 1 commit into
nodejs:masterfrom
Flarna:doc_diag-channel_created
Closed

doc: add version when diagnostics_channel APIs were added#40208
Flarna wants to merge 1 commit into
nodejs:masterfrom
Flarna:doc_diag-channel_created

Conversation

@Flarna

@FlarnaFlarna commented Sep 24, 2021

Copy link
Copy Markdown
Member

Add a yaml section to document when diagnostics_channel APIs were introduced.

Refs.: #34895

@nodejs-github-botnodejs-github-bot added the doc Issues and PRs related to the documentations. label Sep 24, 2021
@Flarna
Flarnaforce-pushed the doc_diag-channel_created branch 2 times, most recently from 3615a52 to d1e4736CompareSeptember 24, 2021 12:00
Add a yaml section to document when diagnostics_channel APIs were
introduced.
@Flarna
Flarnaforce-pushed the doc_diag-channel_created branch from d1e4736 to b70b0d6CompareSeptember 24, 2021 12:06
@FlarnaFlarna added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Sep 24, 2021
@Flarna
Flarna requested a review from QardSeptember 24, 2021 12:15
@tniessen

Copy link
Copy Markdown
Member

I'm not quite sure how the module scoped <!--introduced_in=v15.1.0--> relates to this.

@Qard

Qard commented Sep 24, 2021

Copy link
Copy Markdown
Member

As far as I understand it, the introduced_in thing is for telling the version changer thing at the top of the page what version to start its range at. It doesn't seem to support features introduced partway through the life of one version and then backported partway through the life of another.

@Flarna

Copy link
Copy Markdown
MemberAuthor

I'm not quite sure how the module scoped <!--introduced_in=v15.1.0--> relates to this.

I don't know either. it's not visible if you browse the docs. At least the version matches so seem to be fine.

@jasnelljasnell added the fast-track PRs that do not need to wait for 48 hours to land. label Sep 25, 2021
@github-actions

Copy link
Copy Markdown
Contributor

Fast-track has been requested by @jasnell. Please 👍 to approve.

@FlarnaFlarna added the commit-queue Add this label to land a pull request using GitHub Actions. label Sep 25, 2021
@github-actionsgithub-actionsBot removed the commit-queue Add this label to land a pull request using GitHub Actions. label Sep 25, 2021
@github-actions

Copy link
Copy Markdown
Contributor

Landed in ae876d4...b0ef080

nodejs-github-bot pushed a commit that referenced this pull request Sep 25, 2021
Add a yaml section to document when diagnostics_channel APIs were
introduced.
PR-URL: #40208
Reviewed-By: Stephen Belanger <admin@stephenbelanger.com>
Reviewed-By: Tobias Nießen <tniessen@tnie.de>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
@Flarna
Flarna deleted the doc_diag-channel_created branch September 25, 2021 16:17
targos pushed a commit that referenced this pull request Oct 4, 2021
Add a yaml section to document when diagnostics_channel APIs were
introduced.
PR-URL: #40208
Reviewed-By: Stephen Belanger <admin@stephenbelanger.com>
Reviewed-By: Tobias Nießen <tniessen@tnie.de>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
@MesteeryMesteery added the diagnostics_channel Issues and PRs related to diagnostics channel label Oct 13, 2021
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.diagnostics_channelIssues and PRs related to diagnostics channeldocIssues and PRs related to the documentations.fast-trackPRs that do not need to wait for 48 hours to land.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants

@Flarna@tniessen@Qard@jasnell@cjihrig@nodejs-github-bot@Mesteery