Update registry.access.redhat.com/ubi8/nodejs-16 Docker tag to v1-129.1695740971

[platform-engineering-bot]

This PR contains the following updates:

Package	Update	Change
registry.access.redhat.com/ubi8/nodejs-16	patch	1-105.1684740145 -> 1-129.1695740971

---

⚠ Dependency Lookup Warnings ⚠

Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.

---

Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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.

[michael-valdron]

@thepetk This one is still having DCO problems, would closing the PR trigger it to be re-opened? Or would we need to take a more direct approach in amending the commit?

[michael-valdron]

@thepetk This one is still having DCO problems, would closing the PR trigger it to be re-opened? Or would we need to take a more direct approach in amending the commit?

Looks like you did a direct amend for this one: #213

[michael-valdron]

@thepetk This one is still having DCO problems, would closing the PR trigger it to be re-opened? Or would we need to take a more direct approach in amending the commit?

Looks like you did a direct amend for this one: #213

Fixed

[thepetk]

Looks like you did a direct amend for this one: #213

@michael-valdron Yes indeed I did it manually to see any other issues that might occur. But in general we need to add a solution to our configuration for this issue.

[michael-valdron]

Looks like you did a direct amend for this one: #213

@michael-valdron Yes indeed I did it manually to see any other issues that might occur. But in general we need to add a solution to our configuration for this issue.

Is there an issue open to implement a solution to this?

[thepetk]

Looks like you did a direct amend for this one: #213

@michael-valdron Yes indeed I did it manually to see any other issues that might occur. But in general we need to add a solution to our configuration for this issue.

Is there an issue open to implement a solution to this?

@michael-valdron atm I am in the process of monitoring the behaviour. Ill create an issue with all fixes needed tomorrow

[thepetk]

Looks like you did a direct amend for this one: #213

@michael-valdron Yes indeed I did it manually to see any other issues that might occur. But in general we need to add a solution to our configuration for this issue.

Is there an issue open to implement a solution to this?

@michael-valdron atm I am in the process of monitoring the behaviour. Ill create an issue with all fixes needed tomorrow

@michael-valdron Created devfile/api#1280

[thepetk]

/lgtm
I've tested all updated stacks with odo dev locally and they were working after the update of the image

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: michael-valdron, platform-engineering-bot, thepetk

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• stacks/OWNERS [michael-valdron,thepetk]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment