Skip to content

Replace obsolete ENV VAR VALUE with ENV VAR=VALUE #2254

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

orgads
Copy link
Contributor

@orgads orgads commented Jul 8, 2025

Description

Fixes these warnings:

- LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format

Testing Details

Build passed.

Types of changes

  • Documentation
  • Version change (Update, remove or add more Node.js versions)
  • Variant change (Update, remove or add more variants, or versions of variants)
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Other (none of the above)

Checklist

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING.md document.
  • All new and existing tests passed.

@orgads orgads mentioned this pull request Jul 8, 2025
12 tasks
@PeterDaveHello PeterDaveHello requested a review from Copilot July 10, 2025 18:05
Copilot

This comment was marked as outdated.

Copy link
Member

@PeterDaveHello PeterDaveHello left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Need to fix update.sh & functions.sh

@orgads

This comment was marked as resolved.

@orgads

This comment was marked as outdated.

@orgads orgads requested review from PeterDaveHello and Copilot July 10, 2025 19:45
Copilot

This comment was marked as outdated.

Copilot

This comment was marked as outdated.

@PeterDaveHello
Copy link
Member

Why should this one depend on #2258?

Fixed. This PR now depends on:

The failing test is because https://news.ycombinator.com is down. I reported it, hope they'll fix it soon.

@orgads
Copy link
Contributor Author

orgads commented Jul 10, 2025

Why should this one depend on #2258?

Because they touch the same line in update.sh.

@PeterDaveHello
Copy link
Member

That's something should be prevented.

I don't want to mix different topic in the same pull request.

Why should this one depend on #2258?

Because they touch the same line in update.sh.

@orgads
Copy link
Contributor Author

orgads commented Jul 10, 2025

I agree. So which one of them do you want to accept first? You can either merge the other one and then I'll rebase this one, or I can swap them.

Copy link
Member

@PeterDaveHello PeterDaveHello left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please remove unrelated commit changes that are not relevant to the topic.

@PeterDaveHello
Copy link
Member

I agree. So which one of them do you want to accept first? You can either merge the other one and then I'll rebase this one, or I can swap them.

Maybe this one as it was sent earlier.

@orgads
Copy link
Contributor Author

orgads commented Jul 10, 2025

Done

Copilot

This comment was marked as outdated.

Copilot

This comment was marked as spam.

@orgads
Copy link
Contributor Author

orgads commented Jul 16, 2025

Rebased. Please review.

Copy link
Member

@SimenB SimenB left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Needs another rebase, but LGTM 👍

Copy link
Member

@nschonni nschonni left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As @tianon mentions in #2252 (comment), this advice might not actually be great

Fixes these warnings:
- LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy
  "ENV key value" format
@orgads
Copy link
Contributor Author

orgads commented Jul 17, 2025

Rebased. As for the warnings, whether we like them or not - they currently appear on every build, and it is annoying. It doesn't look like it's going to change anytime soon.

So we can either ignore them and hope that upstream docker will remove them, or change to the new syntax.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants