chore: Update node popularity data#1
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
github-actions
Bot
force-pushed
the
update-node-popularity
branch
2 times, most recently
from
January 12, 2026 01:40
a7c4134 to
7df3788
Compare
github-actions
Bot
force-pushed
the
update-node-popularity
branch
from
January 19, 2026 01:41
7df3788 to
9b80cbb
Compare
github-actions
Bot
force-pushed
the
update-node-popularity
branch
from
January 26, 2026 01:45
9b80cbb to
bc182a9
Compare
github-actions
Bot
force-pushed
the
update-node-popularity
branch
from
February 2, 2026 01:58
bc182a9 to
8e5beba
Compare
github-actions
Bot
force-pushed
the
update-node-popularity
branch
2 times, most recently
from
February 16, 2026 01:57
cc5b635 to
8d6ee14
Compare
github-actions
Bot
force-pushed
the
update-node-popularity
branch
2 times, most recently
from
March 2, 2026 01:55
6c220fe to
a81e5fd
Compare
github-actions
Bot
force-pushed
the
update-node-popularity
branch
from
March 9, 2026 01:56
a81e5fd to
a955a16
Compare
github-actions
Bot
force-pushed
the
update-node-popularity
branch
2 times, most recently
from
March 23, 2026 02:01
16c25c8 to
268122a
Compare
github-actions
Bot
force-pushed
the
update-node-popularity
branch
from
March 30, 2026 02:11
268122a to
2753654
Compare
github-actions
Bot
force-pushed
the
update-node-popularity
branch
from
April 6, 2026 02:12
2753654 to
25685b0
Compare
github-actions
Bot
force-pushed
the
update-node-popularity
branch
from
April 13, 2026 02:28
25685b0 to
19012be
Compare
github-actions
Bot
force-pushed
the
update-node-popularity
branch
from
April 20, 2026 02:28
19012be to
45fb56e
Compare
github-actions
Bot
force-pushed
the
update-node-popularity
branch
from
April 27, 2026 02:33
45fb56e to
905a518
Compare
github-actions
Bot
force-pushed
the
update-node-popularity
branch
from
May 4, 2026 02:38
905a518 to
1fffb91
Compare
github-actions
Bot
force-pushed
the
update-node-popularity
branch
from
May 11, 2026 02:53
1fffb91 to
13b0108
Compare
github-actions
Bot
force-pushed
the
update-node-popularity
branch
from
May 18, 2026 03:26
13b0108 to
6874b44
Compare
github-actions
Bot
force-pushed
the
update-node-popularity
branch
from
May 25, 2026 03:34
6874b44 to
e78d331
Compare
github-actions
Bot
force-pushed
the
update-node-popularity
branch
2 times, most recently
from
June 8, 2026 03:42
7f84fed to
00f8389
Compare
github-actions
Bot
force-pushed
the
update-node-popularity
branch
2 times, most recently
from
June 22, 2026 03:56
9e86b85 to
de08ec6
Compare
github-actions
Bot
force-pushed
the
update-node-popularity
branch
2 times, most recently
from
July 6, 2026 02:54
50d2b0b to
eda5cfe
Compare
github-actions
Bot
force-pushed
the
update-node-popularity
branch
from
July 13, 2026 02:30
eda5cfe to
9d71ba0
Compare
github-actions
Bot
force-pushed
the
update-node-popularity
branch
from
July 20, 2026 02:41
9d71ba0 to
b697450
Compare
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 automated PR updates the node popularity data used for sorting nodes in the node creator panel.
The data is fetched weekly from the n8n telemetry endpoint to reflect current usage patterns.
Generated by the weekly node popularity update workflow.