You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This minor patch updates the node version and libraries to latest to resolve any security fixes. Various code smells have also been fixed. The owning company has also changed.
- Bump Revision
- Change base docker image from node:12-alpine to node:20-alpine
- Change classes with single constructor to a function for maintainability
- Change multiple inline if statements to one per line for readabilty
- Change `var` to `const` or `let` where applicable
- Refactor setInterval to reduce cognitive complexity
- Update docker metadata
- Update mqtt from 4.3.8 to 5.10.1
- Update winston from 3.13.0 to 3.15.0
- Update standard from 14.3.4 to 17.1.2
- Update sonarqube-scanner 2.9.1 to 4.2.3
- Update README
Co-authored-by: Tom Hollingworth <[email protected]>
2020-06-22T03:13:49.817Z | info: Connected to mqtt://broker.hivemq.com:1883
39
39
2020-06-22T03:13:49.819Z | info: Site/Area/Line/Status/UnitModeCurrent : Production
@@ -263,23 +263,23 @@ version: "2.4"
263
263
264
264
services:
265
265
greenville-packaging-line1:
266
-
image: spruiktec/packml-simulator
266
+
image: libremfg/packml-simulator
267
267
environment:
268
268
SITE: Greenville
269
269
AREA: Packaging
270
270
LINE: 'Line 1'
271
271
mem_limit: 30MB
272
272
273
273
greenville-packaging-line2:
274
-
image: spruiktec/packml-simulator
274
+
image: libremfg/packml-simulator
275
275
environment:
276
276
SITE: Greenville
277
277
AREA: Packaging
278
278
LINE: 'Line 2'
279
279
mem_limit: 30MB
280
280
281
281
greenville-cnc-line1:
282
-
image: spruiktec/packml-simulator
282
+
image: libremfg/packml-simulator
283
283
environment:
284
284
SITE: Greenville
285
285
AREA: CNC
@@ -293,12 +293,26 @@ services:
293
293
294
294
For any issue, there are fundamentally three ways an individual can contribute:
295
295
296
-
- By opening the issue for discussion: For instance, if you believe that you have uncovered a bug in, creating a new issue in the [GitHub issue tracker](https://github.com/Spruik/PackML-MQTT-Simulator/issues) is the way to report it.
296
+
- By opening the issue for discussion: For instance, if you believe that you have uncovered a bug in, creating a new issue in the [GitHub issue tracker](https://github.com/libremfg/PackML-MQTT-Simulator/issues) is the way to report it.
297
297
- By helping to triage the issue: This can be done either by providing supporting details (a test case that demonstrates a bug), or providing suggestions on how to address the issue.
298
298
- By helping to resolve the issue: Typically, this is done either in the form of demonstrating that the issue reported is not a problem after all, or more often, by opening a Pull Request that changes some bit of something in the simulator in a concrete and reviewable manner.
299
299
300
300
## Changelog
301
301
302
+
- 2.0.5
303
+
- Bump Revision
304
+
- Change base docker image from node:12-alpine to node:20-alpine
305
+
- Change classes with single constructor to a function for maintainability
306
+
- Change multiple inline if statements to one per line for readabilty
307
+
- Change `var` to `const` or `let` where applicable
308
+
- Refactor setInterval to reduce cognitive complexity
Copy file name to clipboardExpand all lines: SECURITY.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,4 +11,4 @@ These versions are currently being supported with security updates.
11
11
12
12
## Reporting a Vulnerability
13
13
14
-
Minor vulnerabilities can be reported as [issues](https://github.com/Spruik/PackML-MQTT-Simulator/issues). For major or servere vulnerabilities either contact [tomhollingworth](mailto:tom.hollingworth@spuiktec.com) directly, or raise an [issue](https://github.com/Spruik/PackML-MQTT-Simulator/issues). Turn around time for accepted security fixes are up to 2 weeks, with most completed within 3 days of reporting.
14
+
Minor vulnerabilities can be reported as [issues](https://github.com/libremfg/PackML-MQTT-Simulator/issues). For major or servere vulnerabilities either contact [tomhollingworth](mailto:tom@rhize.com) directly, or raise an [issue](https://github.com/libremfg/PackML-MQTT-Simulator/issues). Turn around time for accepted security fixes are up to 2 weeks, with most completed within 3 days of reporting.
0 commit comments