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

Fix left-overs from balena-sdk v13 bump #1742

Merged
3 commits merged into from Jun 29, 2020
Merged

Fix left-overs from balena-sdk v13 bump #1742

3 commits merged into from Jun 29, 2020

Conversation

thgreasi
Copy link
Member

@thgreasi thgreasi commented Apr 21, 2020

Connects-to: #1770 (meta v12 release issue)
Change-type: patch
See: balena-io/open-balena-api#338
See: https://www.flowdock.com/app/rulemotion/i-cli/threads/0Mu_15537VAJ1wxbElpROBA-g5Y
Signed-off-by: Thodoris Greasidis thodoris@balena.io


Please check the CONTRIBUTING.md file for relevant information and some
guidance. Keep in mind that the CLI is a cross-platform application that runs
on Windows, macOS and Linux. Tests will be automatically run by balena CI on
all three operating systems, but this will only help if you have added test
code that exercises the modified or added feature code.

Note that each commit message (currently only the first line) will be
automatically copied to the CHANGELOG.md file, so try writing it in a way
that describes the feature or fix for CLI users.

If there isn't a linked issue or if the linked issue doesn't quite match the
PR, please add a PR description to explain its purpose or the features that it
implements. Adding PR comments to blocks of code that aren't self explanatory
usually helps with the review process.

If the PR introduces security considerations or affects the development, build
or release process, please be sure to highlight this in the PR description.

@thgreasi thgreasi self-assigned this Apr 21, 2020
@thgreasi thgreasi changed the title Update balena sdk 13.2.2 Update balena-sdk to v13.2.2 Apr 21, 2020
thgreasi added a commit that referenced this pull request Apr 21, 2020
Change-type: minor
See: #1742
Signed-off-by: Thodoris Greasidis <thodoris@balena.io>
)
# TODO: combine with the above query once the overall_status field
# is moved to open-balena-api
balena.models.device.get(params.uuid, { $select: 'overall_status' }).get('overall_status').catchReturn(null)
Copy link
Member Author

@thgreasi thgreasi Apr 21, 2020

Choose a reason for hiding this comment

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

I opened the PR just in case that the CLI needs to catch-up with any newer SDK feature before the open-balena-api adds this computed field.
On principle this shouldn't be a blocker for this PR. Moreover the older balenaDeviceStatus implementation wasn't working properly (as I just found out) since not all the required fields were provided.

thgreasi added a commit that referenced this pull request Apr 21, 2020
Change-type: minor
See: #1742
Signed-off-by: Thodoris Greasidis <thodoris@balena.io>
INSTALL.md Outdated
@@ -93,7 +93,7 @@ If you are a Node.js developer, you may wish to install the balena CLI via [npm]
The npm installation involves building native (platform-specific) binary modules, which require
some additional development tools to be installed first:

* [Node.js](https://nodejs.org/) version 8, 10 or 12
* [Node.js](https://nodejs.org/) version 10 or 12
Copy link
Contributor

Choose a reason for hiding this comment

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

I see you've labeled this PR change-type: major, resulting in CLI v12.0.0. We've been collecting breaking changes for v12 in this GDoc: https://docs.google.com/document/d/1uHE-_LLu5gJUQZICQJtlo76EQCm90z0CMAwpkfw6s8w/edit

@srlowe, I think pressure is building to release CLI v12... Node v8 is no longer supported, Node 14 is around the corner, Page wanted to take advantage of Node 10+ features, we need to upgrade balena-sdk too, including testing. I wanted to include issue #1032 in v12, but each week there are new hurdles (the latest being balena CI being unhappy with the MIT licence in the migration from zeit/dockerignore to balena-io-modules/dockerignore). Anyway, we need to put some effort into that GDoc and CLI v12, perhaps with a pause in the oclif/typescript conversion. Maybe something we could also discuss with @odyslam on Thursday's call.

Copy link
Member Author

Choose a reason for hiding this comment

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

@pdcastro is there a v12 release branch that you PR against?
Also heads up that there is a pending arch call item wrt whether we should be using release branches at all or not, so it would be great if you could be there as well.

Copy link
Contributor

Choose a reason for hiding this comment

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

No release branch yet. My thinking is that, when possible, we should release the "breaking changes" behind flags (command-line options) that enable the new behaviour in the current major release. This is possible, for example, for the new gitignore / dockerignore behaviour (but probably not possible for Node 8 → Node 14 support). In this case, it is not really a breaking change, and it also allows users to try the new feature before upgrading the CLI to the next major version. Then, when all this work is done and already released, a release branch is created for the shortest amount of time possible, and what it does is to change the "default behaviour" (without the enabling flags) to be same as the behaviour with the enabling flags, and the enabling flags become a no-op (redundant). I'll look out for the arch call, thanks for the hint! 👍

thgreasi added a commit that referenced this pull request Apr 24, 2020
Change-type: minor
See: #1742
Signed-off-by: Thodoris Greasidis <thodoris@balena.io>
package.json Outdated
@@ -74,7 +74,7 @@
"author": "Juan Cruz Viotti <juan@balena.io>",
"license": "Apache-2.0",
"engines": {
"node": ">=8.0"
"node": ">=10.0"
Copy link
Contributor

Choose a reason for hiding this comment

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

@thgreasi, as discussed in Google chat (balena-io/product), would it be possible to avoid this Node.js bump in this PR, and have this PR's change-type be minor or patch rather than major? And then we merge this PR in CLI v11, and I can add the "balenaCloud backend support/deprecation policy" to the CLI.

Copy link
Member Author

Choose a reason for hiding this comment

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

@pdcastro you mean, even though the SDK's package.json declares that the minimum supported node version is v10?
I haven't tried it, but I think that while doing a fresh npm install on node 8, npm will complain as soon as it sees that the sdk needs node 10.

@thgreasi
Copy link
Member Author

Connects-to: #1770

@thgreasi thgreasi changed the title Update balena-sdk to v13.2.2 Fix left-overs from balena-sdk v13 bump Jun 29, 2020
@thgreasi thgreasi requested a review from pdcastro June 29, 2020 13:09
@thgreasi thgreasi marked this pull request as ready for review June 29, 2020 13:09
Change-type: patch
Signed-off-by: Thodoris Greasidis <thodoris@balena.io>
Change-type: patch
Signed-off-by: Thodoris Greasidis <thodoris@balena.io>
@ghost ghost merged commit d681dac into master Jun 29, 2020
@ghost ghost deleted the update-balena-sdk-13.0.0 branch June 29, 2020 20:52
thgreasi added a commit that referenced this pull request Jul 2, 2020
This allows unauthenticated users to download
unconfigured images. Balena-pine v11 that started
being user by balena-sdk v13 now support
unauthenticated requests.

Change-type: minor
See: #1742
Signed-off-by: Thodoris Greasidis <thodoris@balena.io>
balena-ci pushed a commit that referenced this pull request Jul 3, 2020
This allows unauthenticated users to download
unconfigured images. Balena-pine v11 that started
being user by balena-sdk v13 now support
unauthenticated requests.

Change-type: minor
See: #1742
Signed-off-by: Thodoris Greasidis <thodoris@balena.io>
balena-ci pushed a commit that referenced this pull request Jul 3, 2020
This allows unauthenticated users to download
unconfigured images. Balena-pine v11 that started
being user by balena-sdk v13 now support
unauthenticated requests.

Change-type: minor
See: #1742
Signed-off-by: Thodoris Greasidis <thodoris@balena.io>
balena-ci pushed a commit that referenced this pull request Jul 3, 2020
This allows unauthenticated users to download
unconfigured images. Balena-pine v11 that started
being user by balena-sdk v13 now support
unauthenticated requests.

Change-type: minor
See: #1742
Signed-off-by: Thodoris Greasidis <thodoris@balena.io>
This pull request was closed.
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.

None yet

2 participants