Repository navigation
chore(deps): update dependency node to v26 - #696
Open
ferrlabs-renovate[bot] wants to merge 1 commit into
Open
ferrlabs-renovate[bot] wants to merge 1 commit into
ferrlabs-renovate[bot] wants to merge 1 commit into
Conversation
Signed-off-by: ferrlabs-renovate[bot] <282300760+ferrlabs-renovate[bot]@users.noreply.github.com>
![ferrfleet-interne[bot]](https://avatars.githubusercontent.com/in/5311663?s=60&v=4){kind=small}
There was a problem hiding this comment.
Node 24 to 26 in the setup-node steps of ci.yml (2 places) and publish.yml (1 place). No blocking finding so far, but I'm not approving yet because CI hasn't finished.
- What changed: I did not read the Node 26 release notes. I only checked this repo's own constraints. The root
package.jsonhasengines.node >=22.0.0, so 26 is allowed. pnpm is pinned to 12.8.2 in the workflows. - What breaks here: nothing found. The diff touches only the Node version in three workflow steps. I did not search the repo for APIs removed in Node 25 or 26, so a break there would only show up in CI.
- CI: the
TypecheckandStorybook accessibilityjobs were still running when I looked. Those are the ones that use the new Node version. The security and lint-type checks that finished are green, but they don't exercise Node 26. - Nit: the workflows run on Node 26 while
enginesstill says>=22. Local and CI Node versions can drift without anyone noticing. Consider whether the floor should stay at 22.
I'll treat it as safe to merge once Typecheck and Storybook accessibility pass.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR contains the following updates:
24→2626.13.0Release Notes
actions/node-versions (node)
v26.12.1: 26.12.1Compare Source
Node.js 26.12.1
v26.12.0: 26.12.0Compare Source
Node.js 26.12.0
v26.11.1: 26.11.1Compare Source
Node.js 26.11.1
v26.11.0: 26.11.0Compare Source
Node.js 26.11.0
v26.10.0: 26.10.0Compare Source
Node.js 26.10.0
v26.9.0: 26.9.0Compare Source
Node.js 26.9.0
v26.8.2: 26.8.2Compare Source
Node.js 26.8.2
v26.8.1: 26.8.1Compare Source
Node.js 26.8.1
v26.8.0: 26.8.0Compare Source
Node.js 26.8.0
v26.7.0: 26.7.0Compare Source
Node.js 26.7.0
v26.6.0: 26.6.0Compare Source
Node.js 26.6.0
v26.5.1: 26.5.1Compare Source
Node.js 26.5.1
v26.5.0: 26.5.0Compare Source
Node.js 26.5.0
v26.4.0: 26.4.0Compare Source
Node.js 26.4.0
v26.3.1: 26.3.1Compare Source
Node.js 26.3.1
v26.3.0: 26.3.0Compare Source
Node.js 26.3.0
v26.2.0: 26.2.0Compare Source
Node.js 26.2.0
v26.1.0: 26.1.0Compare Source
Node.js 26.1.0
v26.0.0: 26.0.0Compare Source
Node.js 26.0.0
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate CLI.