Skip to content

Commit 7be00d7

Browse files
knollearyknolleary
authored
Merge pull request #549 from node-red/rel4117
Update for 4.1.17 release
2 parents 2867348 + 9c342b1 commit 7be00d7

3 files changed

Lines changed: 23 additions & 23 deletions

File tree

‎README.md‎

Lines changed: 19 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ Let's dissect that command:
2828
-p 1880:1880 - connect local port 1880 to the exposed internal port 1880
2929
-v node_red_data:/data - mount the host node_red_data directory to the container /data directory so any changes made to flows are persisted
3030
--name mynodered - give this machine a friendly local name
31-
nodered/node-red - the image to base it on - currently Node-RED v4.1.16
31+
nodered/node-red - the image to base it on - currently Node-RED v4.1.17
3232

3333

3434

@@ -37,7 +37,7 @@ Running that command should give a terminal window with a running instance of No
3737
Welcome to Node-RED
3838
===================
3939

40-
10 Oct 12:57:10 - [info] Node-RED version: v4.1.16
40+
10 Oct 12:57:10 - [info] Node-RED version: v4.1.17
4141
10 Oct 12:57:10 - [info] Node.js version: v18.19.0
4242
10 Oct 12:57:10 - [info] Linux 6.6.13-100.fc38.x86_64 x64 LE
4343
10 Oct 12:57:11 - [info] Loading palette nodes
@@ -116,35 +116,35 @@ The following table shows the variety of provided Node-RED images.
116116

117117
| **Tag** |**Node**| **Arch** | **Python** |**Dev**| **Base Image** |
118118
|----------------------------|--------|----------|------------|-------|----------------------------|
119-
| 4.1.16-18 | 18 | amd64 | 3.x | yes | amd64/node:18-alpine |
119+
| 4.1.17-18 | 18 | amd64 | 3.x | yes | amd64/node:18-alpine |
120120
| | 18 | arm32v7 | 3.x | yes | arm32v7/node:18-alpine |
121121
| | 18 | arm64v8 | 3.x | yes | arm64v8/node:18-alpine |
122122
| | | | | | |
123-
| 4.1.16-18-minimal | 18 | amd64 | no | no | amd64/node:18-alpine |
123+
| 4.1.17-18-minimal | 18 | amd64 | no | no | amd64/node:18-alpine |
124124
| | 18 | arm32v7 | no | no | arm32v7/node:18-alpine |
125125
| | 18 | arm64v8 | no | no | arm64v8/node:18-alpine |
126126

127127
| **Tag** |**Node**| **Arch** | **Python** |**Dev**| **Base Image** |
128128
|----------------------------|--------|----------|------------|-------|----------------------------|
129-
| 4.1.16-20 | 20 | amd64 | 3.x | yes | amd64/node:20-alpine |
129+
| 4.1.17-20 | 20 | amd64 | 3.x | yes | amd64/node:20-alpine |
130130
| | 20 | arm32v7 | 3.x | yes | arm32v7/node:20-alpine |
131131
| | 20 | arm64v8 | 3.x | yes | arm64v8/node:20-alpine |
132132
| | | | | | |
133-
| 4.1.16-20-minimal | 20 | amd64 | no | no | amd64/node:20-alpine |
133+
| 4.1.17-20-minimal | 20 | amd64 | no | no | amd64/node:20-alpine |
134134
| | 20 | arm32v7 | no | no | arm32v7/node:20-alpine |
135135
| | 20 | arm64v8 | no | no | arm64v8/node:20-alpine |
136136
| | | | | | |
137-
| 4.1.16-debian | 20 | amd64 | 3.x | yes | amd64/node:20-buster-slim |
137+
| 4.1.17-debian | 20 | amd64 | 3.x | yes | amd64/node:20-buster-slim |
138138
| | 20 | arm32v7 | 3.x | yes | amd64/node:20-buster-slim |
139139
| | 20 | arm64v8 | 3.x | yes | amd64/node:20-buster-slim |
140140

141141
| **Tag** |**Node**| **Arch** | **Python** |**Dev**| **Base Image** |
142142
|----------------------------|--------|----------|------------|-------|----------------------------|
143-
| 4.1.16-22 | 22 | amd64 | 3.x | yes | amd64/node:22-alpine |
143+
| 4.1.17-22 | 22 | amd64 | 3.x | yes | amd64/node:22-alpine |
144144
| | 22 | arm32v7 | 3.x | yes | arm32v7/node:22-alpine |
145145
| | 22 | arm64v8 | 3.x | yes | arm64v8/node:22-alpine |
146146
| | | | | | |
147-
| 4.1.16-22-minimal | 22 | amd64 | no | no | amd64/node:22-alpine |
147+
| 4.1.17-22-minimal | 22 | amd64 | no | no | amd64/node:22-alpine |
148148
| | 22 | arm32v7 | no | no | arm32v7/node:22-alpine |
149149
| | 22 | arm64v8 | no | no | arm64v8/node:22-alpine |
150150

@@ -156,36 +156,36 @@ The following table shows the provided Manifest Lists.
156156

157157
| **Tag** | **Node-RED Base Image** |
158158
|----------------------------------------|--------------------------------------------|
159-
| latest, 4.1.16, | nodered/node-red:4.1.16-20 |
160-
| latest-20, 4.1.16-20 | |
159+
| latest, 4.1.17, | nodered/node-red:4.1.17-20 |
160+
| latest-20, 4.1.17-20 | |
161161
| | |
162162
| | |
163-
| latest-minimal, 4.1.16-minimal, | nodered/node-red:4.1.16-20-minimal |
164-
| latest-20-minimal, 4.1.16-20-minimal | |
163+
| latest-minimal, 4.1.17-minimal, | nodered/node-red:4.1.17-20-minimal |
164+
| latest-20-minimal, 4.1.17-20-minimal | |
165165
| | |
166166
| latest-debian | nodered/node-red:latest-debian |
167167

168168

169169
| **Tag** | **Node-RED Base Image** |
170170
|----------------------------------------|--------------------------------------------|
171-
| latest-18, 4.1.16-18 | nodered/node-red:4.1.16-18 |
171+
| latest-18, 4.1.17-18 | nodered/node-red:4.1.17-18 |
172172
| | |
173-
| latest-18-minimal, 4.1.16-18-minimal | nodered/node-red:4.1.16-18-minimal |
173+
| latest-18-minimal, 4.1.17-18-minimal | nodered/node-red:4.1.17-18-minimal |
174174

175175

176176
| **Tag** | **Node-RED Base Image** |
177177
|----------------------------------------|--------------------------------------------|
178-
| latest-22, 4.1.16-22 | nodered/node-red:4.1.16-22 |
178+
| latest-22, 4.1.17-22 | nodered/node-red:4.1.17-22 |
179179
| | |
180-
| latest-22-minimal, 4.1.16-22-minimal | nodered/node-red:4.1.16-22-minimal
180+
| latest-22-minimal, 4.1.17-22-minimal | nodered/node-red:4.1.17-22-minimal
181181

182182

183183
With the support of Docker manifest list, there is no need to explicitly add the tag for the architecture to use.
184184
When a docker run command or docker service command or docker stack command is executed, docker checks which architecture is required and verifies if it is available in the docker repository. If it does, docker pulls the matching image for it.
185185

186186
Therefore all tags regarding Raspberry PI's are dropped.
187187

188-
For example: suppose you are running on a Raspberry PI 3B, which has `arm32v7` as architecture. Then just run the following command to pull the image (tagged by `4.1.16-20`), and run the container.
188+
For example: suppose you are running on a Raspberry PI 3B, which has `arm32v7` as architecture. Then just run the following command to pull the image (tagged by `4.1.17-20`), and run the container.
189189

190190

191191
```
@@ -325,7 +325,7 @@ Docker build process, the dependencies are installed under `/usr/src/node-red`.
325325
The main sections to modify are
326326

327327
"dependencies": {
328-
"node-red": "^4.1.16", <-- set the version of Node-RED here
328+
"node-red": "^4.1.17", <-- set the version of Node-RED here
329329
"node-red-dashboard": "*" <-- add any extra npm packages here
330330
},
331331

‎docker-custom/package.json‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
{
22
"name": "node-red-docker",
3-
"version": "4.1.16",
3+
"version": "4.1.17",
44
"description": "Low-code programming for event-driven applications",
55
"homepage": "http://nodered.org",
66
"license": "Apache-2.0",
@@ -29,7 +29,7 @@
2929
}
3030
],
3131
"dependencies": {
32-
"node-red": "4.1.16"
32+
"node-red": "4.1.17"
3333
},
3434
"engines": {
3535
"node": ">=18"

‎package.json‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
{
22
"name": "node-red-docker",
3-
"version": "4.1.16",
3+
"version": "4.1.17",
44
"description": "Low-code programming for event-driven applications",
55
"homepage": "http://nodered.org",
66
"license": "Apache-2.0",
@@ -29,7 +29,7 @@
2929
}
3030
],
3131
"dependencies": {
32-
"node-red": "4.1.16"
32+
"node-red": "4.1.17"
3333
},
3434
"engines": {
3535
"node": ">=18"

0 commit comments

Comments
 (0)