Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(container)!: Update image docker.io/nodered/node-red ( 3.1.11 → 4.0.0 ) #3876

Merged
merged 1 commit into from
Jun 22, 2024

Conversation

repo-jeeves[bot]
Copy link
Contributor

@repo-jeeves repo-jeeves bot commented Jun 20, 2024

This PR contains the following updates:

Package Update Change
docker.io/nodered/node-red major 3.1.11 -> 4.0.0

Release Notes

node-red/node-red-docker (docker.io/nodered/node-red)

v4.0.0

Compare Source

What's Changed

New Contributors

Full Changelog: node-red/node-red-docker@v2.2.2...v4.0.0

…4.0.0 )

| datasource | package                    | from   | to    |
| ---------- | -------------------------- | ------ | ----- |
| docker     | docker.io/nodered/node-red | 3.1.11 | 4.0.0 |
@repo-jeeves repo-jeeves bot added renovate/container Issue relates to a Renovate container update type/major Issue relates to a major version bump cluster/main Changes made in the main cluster size/XS Marks a PR that changes 0-9 lines, ignoring generated files labels Jun 20, 2024
@repo-jeeves
Copy link
Contributor Author

repo-jeeves bot commented Jun 20, 2024

--- kubernetes/main/apps/home/node-red/app Kustomization: flux-system/home-node-red HelmRelease: home/node-red

+++ kubernetes/main/apps/home/node-red/app Kustomization: flux-system/home-node-red HelmRelease: home/node-red

@@ -43,13 +43,13 @@

             env:
               NODE_RED_ENABLE_PROJECTS: 'true'
               NODE_RED_ENABLE_SAFE_MODE: 'false'
               TZ: America/Toronto
             image:
               repository: docker.io/nodered/node-red
-              tag: 3.1.11@sha256:db8329d3cc6c6d6aa8bf9c558c89a1f0f33813acb73955815b32e34c15bd1df4
+              tag: 4.0.0@sha256:aa2d35ab4cbc1c3bf791a22bbf4de251635c5cbc06b3ec9e6b26a31b1296f7e5
             resources:
               limits:
                 memory: 500Mi
               requests:
                 cpu: 25m
                 memory: 350Mi

@repo-jeeves
Copy link
Contributor Author

repo-jeeves bot commented Jun 20, 2024

--- HelmRelease: home/node-red Deployment: home/node-red

+++ HelmRelease: home/node-red Deployment: home/node-red

@@ -45,13 +45,13 @@

         - name: NODE_RED_ENABLE_PROJECTS
           value: 'true'
         - name: NODE_RED_ENABLE_SAFE_MODE
           value: 'false'
         - name: TZ
           value: America/Toronto
-        image: docker.io/nodered/node-red:3.1.11@sha256:db8329d3cc6c6d6aa8bf9c558c89a1f0f33813acb73955815b32e34c15bd1df4
+        image: docker.io/nodered/node-red:4.0.0@sha256:aa2d35ab4cbc1c3bf791a22bbf4de251635c5cbc06b3ec9e6b26a31b1296f7e5
         name: main
         resources:
           limits:
             memory: 500Mi
           requests:
             cpu: 25m

@repo-jeeves
Copy link
Contributor Author

repo-jeeves bot commented Jun 20, 2024

🦙 MegaLinter status: ✅ SUCCESS

Descriptor Linter Files Fixed Errors Elapsed time
✅ COPYPASTE jscpd yes no 1.01s
✅ REPOSITORY git_diff yes no 0.05s
✅ REPOSITORY secretlint yes no 2.49s
✅ YAML prettier 1 0 0.37s
✅ YAML yamllint 1 0 0.29s

See detailed report in MegaLinter reports
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff

MegaLinter is graciously provided by OX Security

@szinn szinn merged commit 73be0e1 into main Jun 22, 2024
12 checks passed
@szinn szinn deleted the renovate/main-docker.io-nodered-node-red-4.x branch June 22, 2024 23:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cluster/main Changes made in the main cluster renovate/container Issue relates to a Renovate container update size/XS Marks a PR that changes 0-9 lines, ignoring generated files type/major Issue relates to a major version bump
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant