## 🐞 Bug report <!-- Thank you for reporting an issue in our project 🙌 Before opening a new issue, please make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead. --> ### Describe the bug <!-- A clear and concise description of what the bug is. --> Our containers are still using node:16 even though node:18 is the current LTS. ### Steps To Reproduce <!-- Steps to reproduce the behavior: 1. Go to '...' 2. Click on '....' 3. Scroll down to '....' 4. See error --> ### Expected behavior <!-- A clear and concise description of what you expected to happen. --> We should probably switch to a more recent version. ### System (please complete the following information): <!-- - secureCodeBox Version/Release - OS: [e.g. iOS] - Kubernetes Version [command: `kubectl version`] - Docker Version [command: `docker -v`] - Browser [e.g. chrome, safari, firefox,...] --> ### Screenshots / Logs <!-- If applicable, add screenshots to help explain your problem. --> ### Additional context <!-- Add any other context about the problem here. -->
Activity
secureCodeBox#1852 Upgrade node version to current LTS
secureCodeBox#1852 Upgrade node version to current LTS
#1852 Upgrade node version to current LTS
secureCodeBox#1852 Upgrade node to latest LTS in workflows
secureCodeBox#1852 Upgrade node to latest LTS in templates
secureCodeBox#1852 Upgrade node to latest LTS in templates
secureCodeBox#1852 Upgrade node to latest LTS in templates
#1852 Upgrade node to latest LTS in templates