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

update list of tested OSes accordingly with metadata.json #414

Merged
merged 2 commits into from
Jan 22, 2020
Merged

update list of tested OSes accordingly with metadata.json #414

merged 2 commits into from
Jan 22, 2020

Conversation

mmoll
Copy link
Contributor

@mmoll mmoll commented Jan 18, 2020

Pull Request (PR) description

This Pull Request (PR) fixes the following issues

@mmoll
Copy link
Contributor Author

mmoll commented Jan 18, 2020

rebased version of GH-402

@mmoll
Copy link
Contributor Author

mmoll commented Jan 18, 2020

Debian/buster is already bringing NodeJS 10, so using 8.x as default will not work, as the package is not downgraded, leading to a test fail.

Looking at https://nodejs.org/en/about/releases/ I'd even lean towards setting the default to 12.x.

@@ -11,7 +11,7 @@
$repo_proxy_password = 'absent'
$repo_proxy_username = 'absent'
$repo_release = undef
$repo_url_suffix = '8.x'
$repo_url_suffix = '10.x'
Copy link
Member

Choose a reason for hiding this comment

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

is this change required? If so it qualifies as a backwards-incompatble change?

Copy link
Contributor Author

@mmoll mmoll Jan 18, 2020

Choose a reason for hiding this comment

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

#414 (comment) :)

As a changed default it is breaking, yes.

Should I set it to 12, while at it?

Copy link
Member

Choose a reason for hiding this comment

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

yeah, I'm fine with 12

Copy link
Contributor Author

Choose a reason for hiding this comment

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

There we go... 💚

@juniorsysadmin
Copy link
Member

Also consider updating the repo_url_suffix section of the README

@mmoll
Copy link
Contributor Author

mmoll commented Jan 20, 2020

Also consider updating the repo_url_suffix section of the README

Done.

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

Successfully merging this pull request may close these issues.

5 participants