GeezerVison is showing github.com — v16.1.0 release proposal by targos · Pull Request #38522 · nodejs/node
Conversation
targos
commented
May 3, 2021
•
edited
Loading
Uh oh!
There was an error while loading. Please reload this page.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
bricss, DerekNonGeneric, and bl-ue reacted with thumbs up emoji
bricss, DerekNonGeneric, and bl-ue reacted with rocket emoji
All reactions
-
👍
3 reactions
-
🚀
3 reactions
Main goal of using a GitHub Action for labelling PRs has been to move
the mapping between files changed -> label into a configuration file
local to the nodejs/node repository.
Previously any changes to that mapping meant having to grasp the
nodejs/github-bot project, open a PR with the neccessary changes, get
approval from its maintainers before those changes finally got pushed
to production.
The logic involved in using the file paths / label configuration and
resolving the labels to be applied, has been moved into a custom GitHub
Action project: nodejs/node-pr-labeler.
Aside from removing the external dependency the nodejs-github-bot is in
practise, it also reduces the bar for contributors since the resulting
project is a lot smaller and less complex than nodejs/github-bot.
PR-URL: #38301
Fixes: nodejs/github-bot#294
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
`output.diagnostic` is a list that is appended to on SmartOS when
retrying a test due to `ECONNREFUSED`. The test runner checks if
`output.diagnostic` is truthy and, if so, assigns its value to
`self.traceback`. However `self.traceback` is supposed to be a string,
and `_printDiagnostic()` in the `TapProgressIndicator` attempts to call
`splitlines()` on it, which fails if it is a list with:
AttributeError: 'list' object has no attribute 'splitlines'
PR-URL: #38289
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Christian Clauss <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Benjamin Gruenbaum <[email protected]>
Do not call `.displayPrompt()` twice after the `eval` callback
resulted in an error.
(This does not affect the default eval because it doesn’t use
the callback if an error occurs.)
PR-URL: #38314
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Benjamin Gruenbaum <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
This commit adds a suggestion for a template to be used as part of the
security release process. One step of this process is to create an email
to nodejs-sec group and currently would contain a copy and pasted
version of what is published on nodejs.org. This suggestion is to
instead use a link to the blog post.
PR-URL: #38290
Refs: #38143
Reviewed-By: Michael Dawson <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Policy tests can fail if a `package.json` exists in any of the parent
directories above the test. The existing checks are done for the
ancestors of the test directory but some tests execute from the tmpdir.
PR-URL: #38285
Refs: #38088
Refs: #35600
Refs: #35633
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Previously, the code path would allocated a tracked ArrayBuffer
that defers cleanup and deallocation of the underlying data with
a SetImmediate. Avoid the unnecessary deferral by just allocating
a `BackingStore` directly and writing into it.
Fixes: #38300
Refs: #38336
PR-URL: #38337
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Khaidi Chu <[email protected]>
Reviewed-By: Matteo Collina <[email protected]>
Reviewed-By: Joyee Cheung <[email protected]>
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
- [
0e446d6048] - debugger: enable linter on internal/inspector/inspect\_client (Antoine du Hamel) #38417
- [
9f0e80aa4d] - debugger: refactor internal/inspector/\_inspect to use more primordials (Antoine du Hamel) #38406
Notice the backslashes are not from the commit messages, seems like a bug in the tool that generates the commit list.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
- [
0e446d6048] - debugger: enable linter on internal/inspector/inspect\_client (Antoine du Hamel) #38417
- [
9f0e80aa4d] - debugger: refactor internal/inspector/\_inspect to use more primordials (Antoine du Hamel) #38406
Notice the backslashes are not from the commit messages, seems like a bug in the tool that generates the commit list.
The tool is https://github.com/nodejs/changelog-maker/
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Notable changes:
fs:
* (SEMVER-MINOR) allow no-params fsPromises fileHandle read (Nitzan Uziely) #38287
PR-URL: #38522
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
CITGM looks okay. There are some modules like Jest that fail to be downloaded (error is "Invalid package, must have name and version"), but I can reproduce with v16.0.0 too.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
targos
added a commit
that referenced
this pull request
May 4, 2021
Notable changes:
fs:
* (SEMVER-MINOR) allow no-params fsPromises fileHandle read (Nitzan Uziely) #38287
PR-URL: #38522
targos
added a commit
to targos/nodejs.org
that referenced
this pull request
May 4, 2021
targos
added a commit
to nodejs/nodejs.org
that referenced
this pull request
May 4, 2021
Uh oh!
There was an error while loading. Please reload this page.
Assignees
No one assigned
Labels
release
Issues and PRs related to Node.js releases.
Milestone
No milestone
Development
Successfully merging this pull request may close these issues.
Uh oh!
There was an error while loading. Please reload this page.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
|