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

fix(app): update container tag ghcr.io/tyriis/locking-service to v0.0.7 #2352

Merged
merged 1 commit into from
Jan 14, 2024

Conversation

tyriis-automation[bot]
Copy link
Contributor

This PR contains the following updates:

Package Update Change OpenSSF
ghcr.io/tyriis/locking-service patch v0.0.6 -> v0.0.7 OpenSSF Scorecard

Release Notes

tyriis/locking-service (ghcr.io/tyriis/locking-service)

v0.0.7

Compare Source


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@tyriis-automation tyriis-automation bot added renovate/docker renovate docker datasource type/patch a patch for a bug labels Jan 13, 2024
Copy link

Quality Gate Passed Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

@tyriis-automation
Copy link
Contributor Author

--- HelmRelease: home-automation/locking-service Deployment: home-automation/locking-service

+++ HelmRelease: home-automation/locking-service Deployment: home-automation/locking-service

@@ -51,13 +51,13 @@

         - name: CONFIG_PATH
           value: /config/configuration.yaml
         - name: NODE_ENV
           value: production
         - name: TZ
           value: ${SETTING_TZ}
-        image: ghcr.io/tyriis/locking-service:v0.0.6
+        image: ghcr.io/tyriis/locking-service:v0.0.7@sha256:71c232654b83a9c7c43a0f110b1c24d408a217410475234caa89373cc101c5d7
         livenessProbe:
           failureThreshold: 3
           initialDelaySeconds: 0
           periodSeconds: 10
           tcpSocket:
             port: 3000

@tyriis-automation
Copy link
Contributor Author

--- kubernetes/talos-flux/apps/home-automation/locking-service/app Kustomization: flux-system/apps-locking-service HelmRelease: home-automation/locking-service

+++ kubernetes/talos-flux/apps/home-automation/locking-service/app Kustomization: flux-system/apps-locking-service HelmRelease: home-automation/locking-service

@@ -42,13 +42,13 @@

             env:
               CONFIG_PATH: /config/configuration.yaml
               NODE_ENV: production
               TZ: ${SETTING_TZ}
             image:
               repository: ghcr.io/tyriis/locking-service
-              tag: v0.0.6
+              tag: v0.0.7@sha256:71c232654b83a9c7c43a0f110b1c24d408a217410475234caa89373cc101c5d7
             ports:
             - containerPort: 3000
               name: http
               protocol: TCP
             resources:
               requests:

@tyriis-automation
Copy link
Contributor Author

🦙 MegaLinter status: ✅ SUCCESS

Descriptor Linter Files Fixed Errors Elapsed time
✅ EDITORCONFIG editorconfig-checker 1 0 0.01s
✅ REPOSITORY gitleaks yes no 2.0s
✅ YAML prettier 1 0 0.49s
✅ YAML yamllint 1 0 0.31s

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

@tyriis-automation tyriis-automation bot merged commit 506b110 into main Jan 14, 2024
9 checks passed
@tyriis-automation tyriis-automation bot deleted the renovate/ghcr.io-tyriis-locking-service-0.x branch January 14, 2024 00:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants