Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Containers still use node:16 #1852

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.

Sign up for GitHub

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

Jump to bottom
Closed
o1oo11oo opened this issue Aug 7, 2023 · 0 comments · Fixed by #1853
Closed

Containers still use node:16 #1852

o1oo11oo opened this issue Aug 7, 2023 · 0 comments · Fixed by #1853
Assignees
@o1oo11oo
Labels
bug Bugs

Comments

@o1oo11oo
Copy link
Contributor

o1oo11oo commented Aug 7, 2023

🐞 Bug report

Describe the bug

Our containers are still using node:16 even though node:18 is the current LTS.

Steps To Reproduce

Expected behavior

We should probably switch to a more recent version.

System (please complete the following information):

Screenshots / Logs

Additional context
@o1oo11oo o1oo11oo added the bug Bugs label Aug 7, 2023
@o1oo11oo o1oo11oo self-assigned this Aug 7, 2023
@o1oo11oo o1oo11oo moved this from Backlog to In Progress in secureCodeBox v4 Aug 7, 2023
o1oo11oo pushed a commit to o1oo11oo/secureCodeBox that referenced this issue Aug 7, 2023
secureCodeBox#1852 Upgrade node version to current LTS
c70dc83 
Signed-off-by: Lukas Fischer <[email protected]>
o1oo11oo pushed a commit to o1oo11oo/secureCodeBox that referenced this issue Aug 7, 2023
secureCodeBox#1852 Upgrade node version to current LTS
834ac83 
Fixes secureCodeBox#1852

Signed-off-by: Lukas Fischer <[email protected]>
@o1oo11oo o1oo11oo mentioned this issue Aug 7, 2023
Merged
4 tasks
@o1oo11oo o1oo11oo moved this from In Progress to To Review in secureCodeBox v4 Aug 7, 2023
o1oo11oo pushed a commit that referenced this issue Aug 8, 2023
@o1oo11oo
#1852 Upgrade node version to current LTS
7c9aa7e 
Fixes #1852

Signed-off-by: Lukas Fischer <[email protected]>
@github-project-automation github-project-automation bot moved this from To Review to Done in secureCodeBox v4 Aug 8, 2023
o1oo11oo pushed a commit to o1oo11oo/secureCodeBox that referenced this issue Sep 5, 2023
secureCodeBox#1852 Upgrade node to latest LTS in workflows
8406440 
Missed this node version when upgrading to latest LTS in secureCodeBox#1853

Signed-off-by: Lukas Fischer <[email protected]>
@o1oo11oo o1oo11oo mentioned this issue Sep 5, 2023
Merged
4 tasks
o1oo11oo pushed a commit to o1oo11oo/secureCodeBox that referenced this issue Sep 8, 2023
secureCodeBox#1852 Upgrade node to latest LTS in templates
d95c2ab 
Missed this node version as well when upgrading to latest LTS in secureCodeBox#1853

Signed-off-by: Lukas Fischer <[email protected]>
o1oo11oo pushed a commit to o1oo11oo/secureCodeBox that referenced this issue Sep 11, 2023
secureCodeBox#1852 Upgrade node to latest LTS in templates
985b704 
Missed this node version when upgrading to latest LTS in secureCodeBox#1853

Signed-off-by: Lukas Fischer <[email protected]>
Ilyesbdlala pushed a commit to o1oo11oo/secureCodeBox that referenced this issue Sep 12, 2023
@Ilyesbdlala
secureCodeBox#1852 Upgrade node to latest LTS in templates
6161bc9 
Missed this node version when upgrading to latest LTS in secureCodeBox#1853

Signed-off-by: Lukas Fischer <[email protected]>
Ilyesbdlala pushed a commit that referenced this issue Sep 12, 2023
@Ilyesbdlala
#1852 Upgrade node to latest LTS in templates
a18802a 
Missed this node version when upgrading to latest LTS in #1853

Signed-off-by: Lukas Fischer <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@o1oo11oo o1oo11oo

Labels
bug Bugs
Projects
secureCodeBox v4
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Upgrade node version to current LTS o1oo11oo/secureCodeBox
1 participant
@o1oo11oo