Skip to content

Update npm release instructions to omit PRs from release notes#4951

Merged
tekton-robot merged 1 commit into
tektoncd:mainfrom
AlanGreene:npm_release_note_skip
May 13, 2026
Merged

Update npm release instructions to omit PRs from release notes#4951
tekton-robot merged 1 commit into
tektoncd:mainfrom
AlanGreene:npm_release_note_skip

Conversation

@AlanGreene
Copy link
Copy Markdown
Member

@AlanGreene AlanGreene commented May 11, 2026

Changes

Publication of the npm packages is irrelevant to most users of the Dashboard application and should not be included in the release notes published with each Dashboard release.

PRs with the label release-note-none are already excluded from the GH generated release notes, configured at

exclude:
labels:
- release-note-none
.

/kind documentation

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

  • Docs included if any changes are user facing
  • Tests included if any functionality added or changed
  • Follows the commit message standard
  • Meets the Tekton contributor standards (including
    functionality, content, code)
  • Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
  • Release notes block below has been updated with any user facing changes (new features, significant UI changes, API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)
  • Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

NONE

…e notes

Publication of the npm packages is irrelevant to most users of the Dashboard
application and should not be included in the release notes published with
each Dashboard release.
@tekton-robot tekton-robot added kind/documentation Categorizes issue or PR as related to documentation. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels May 11, 2026
Copy link
Copy Markdown
Contributor

@kaushalnavneet kaushalnavneet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @AlanGreene

@kaushalnavneet
Copy link
Copy Markdown
Contributor

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label May 13, 2026
Copy link
Copy Markdown
Contributor

@briangleeson briangleeson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@tekton-robot
Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: briangleeson, kaushalnavneet

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 13, 2026
@tekton-robot tekton-robot merged commit 26c3005 into tektoncd:main May 13, 2026
15 checks passed
@AlanGreene AlanGreene deleted the npm_release_note_skip branch May 13, 2026 15:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/documentation Categorizes issue or PR as related to documentation. lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants