[dependabot]

Bumps PiHome/IOT/HC-SR501-Node-Red-Presence-Detector from ec72d3d to 71c81e1.

Commits

• 71c81e1 chore(deps): bump nodered/node-red in /examples/docker
• c997fc7 chore(deps): bump portainer/portainer-ce in /examples/docker
• a5aff12 fix(deps): bump serde_json from 1.0.151 to 1.0.154
• See full diff in compare view

[github-actions]

❌MegaLinter analysis: Error

Descriptor	Linter	Files	Fixed	Errors	Max errors	Warnings	Elapsed time
✅ ACTION	actionlint	3		0		0	0.44s
❌ DOCKERFILE	dclint	14	6	8		0	3.1s
✅ JSON	jsonlint	3		0		0	0.08s
✅ JSON	prettier	3	0	0		0	0.32s
⚠️ MARKDOWN	markdownlint	15	0	11		0	0.64s
✅ MARKDOWN	markdown-table-formatter	15	0	0		0	0.21s
✅ YAML	prettier	23	8	0		0	0.8s
❌ YAML	yamllint	23		18		0	0.92s

Detailed Issues

❌ DOCKERFILE / dclint - 8 errors

PiHall/IOT/docker-compose.yml
  72:1     error  Service "home_power_monitor" is exporting port "${HTTP_PORT:-3000}:${HTTP_PORT:-3000}" without specifying the interface to listen on.  no-unbound-port-interfaces
 100:1     error  Service "home_power_monitor_analytics" is exporting port "${ANALYTICS_HTTP_PORT:-8081}:8080" without specifying the interface to listen on.  no-unbound-port-interfaces
 113:1     error  Service "pgadmin" is exporting port "5050:80" without specifying the interface to listen on.  no-unbound-port-interfaces
 126:1     error  Service "postgres" is exporting port "5432:5432" without specifying the interface to listen on.  no-unbound-port-interfaces
 107:1     error  Service "pgadmin" is using the image "dpage/pgadmin4", which does not have a concrete version tag. Specify a concrete version tag.  service-image-require-explicit-tag

PiHall/docker-compose.yml
  30:1     error  Service "cups" is exporting port "631:631" without specifying the interface to listen on.  no-unbound-port-interfaces

PiHome/IOT/docker-compose.yml
   7:1     error  Service "esphome" is using the image "ghcr.io/esphome/esphome", which does not have a concrete version tag. Specify a concrete version tag.  service-image-require-explicit-tag

PiHome/Security/docker-compose.yml
   6:1     error  Service "frigate" is using the image "ghcr.io/blakeblackshear/frigate:stable", which does not have a concrete version tag. Specify a concrete version tag.  service-image-require-explicit-tag

✖ 8 problems (8 errors, 0 warnings)

❌ YAML / yamllint - 18 errors

.github/dependabot.yaml
  6:1       warning  missing document start "---"  (document-start)

.github/workflows/dependabot.yaml
  1:1       warning  missing document start "---"  (document-start)
  3:1       warning  truthy value should be one of [false, true]  (truthy)

.github/workflows/mega_linter.yaml
  8:1       warning  truthy value should be one of [false, true]  (truthy)

.github/workflows/release_please.yaml
  1:1       warning  missing document start "---"  (document-start)
  1:1       warning  truthy value should be one of [false, true]  (truthy)

PiForwarder/docker/docker-compose.yml
  1:1       warning  missing document start "---"  (document-start)

PiHall/IOT/docker-compose.yml
  3:1       warning  missing document start "---"  (document-start)
  58:8      warning  missing starting space in comment  (comments)
  61:8      warning  missing starting space in comment  (comments)
  131:14    error    too many spaces inside brackets  (brackets)
  131:65    error    too many spaces inside brackets  (brackets)

PiHome/IOT/ESPHome/bedroom.yaml
  2:1       warning  missing document start "---"  (document-start)

PiHome/IOT/ESPHome/detector.yaml
  2:1       warning  missing document start "---"  (document-start)

PiHome/IOT/ESPHome/hallway.yaml
  1:1       warning  missing document start "---"  (document-start)

PiHome/IOT/ESPHome/watering-system.yaml
  1:1       warning  missing document start "---"  (document-start)
  81:3      warning  comment not indented like content  (comments-indentation)

PiHome/IOT/docker-compose.yml
  94:17     warning  missing starting space in comment  (comments)

⚠️ MARKDOWN / markdownlint - 11 errors

CHANGELOG.md:22 error MD024/no-duplicate-heading Multiple headings with the same content [Context: "Bug Fixes"]
CHANGELOG.md:29 error MD024/no-duplicate-heading Multiple headings with the same content [Context: "Features"]
CHANGELOG.md:33 error MD024/no-duplicate-heading Multiple headings with the same content [Context: "Bug Fixes"]
CHANGELOG.md:43 error MD024/no-duplicate-heading Multiple headings with the same content [Context: "Features"]
CHANGELOG.md:50 error MD024/no-duplicate-heading Multiple headings with the same content [Context: "Bug Fixes"]
CHANGELOG.md:60 error MD024/no-duplicate-heading Multiple headings with the same content [Context: "Features"]
CHANGELOG.md:64 error MD024/no-duplicate-heading Multiple headings with the same content [Context: "Bug Fixes"]
CHANGELOG.md:70 error MD024/no-duplicate-heading Multiple headings with the same content [Context: "Features"]
CHANGELOG.md:74 error MD024/no-duplicate-heading Multiple headings with the same content [Context: "Bug Fixes"]
CHANGELOG.md:82 error MD024/no-duplicate-heading Multiple headings with the same content [Context: "Bug Fixes"]
PiHome/IOT/ESPHome/README.md:1 error MD041/first-line-heading/first-line-h1 First line in a file should be a top-level heading [Context: "TODO"]

Notices

⚠️ Your configuration references items that have been removed from MegaLinter and are ignored: MARKDOWN_MARKDOWN_LINK_CHECK. See Removed linters to find their replacements.

See detailed reports in MegaLinter artifacts

Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining FLAVOR_SUGGESTIONS: false)

• Documentation: Custom Flavors
• Command: npx mega-linter-runner@10.2.0 --custom-flavor-setup --custom-flavor-linters ACTION_ACTIONLINT,DOCKERFILE_DCLINT,JSON_JSONLINT,JSON_PRETTIER,MARKDOWN_MARKDOWNLINT,MARKDOWN_MARKDOWN_TABLE_FORMATTER,YAML_PRETTIER,YAML_YAMLLINT

Show us your support by starring ⭐ the repository