-
Notifications
You must be signed in to change notification settings - Fork 25
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
chore(deps): update dependency @fluencelabs/cli to v0.13.0 - autoclosed #326
Conversation
DXJ-390 add to cli's ipfsClient dag_upload and dag_upload_string DXJ-400 fluence aqua ignores all files inside subdirectories
DXJ-386 integrate air-beautify-wasm to Fluence CLI DXJ-358 Check for latest version and suggest to update to it
If version is set in fluence.yaml - don't warn about available new version DXJ-384 Add node 18 support in fcli/flox
DXJ-147 Add `FORCE_COLOR=0` to docs
Aqua always outputs color on errors (and maybe in some other palces)
There should be a DXJ-395 `fluence spell new` doesn't add anything to `fluence.yaml`
and
both versions – same behaviour DXJ-382 stabilize deployed workers structure in aqua
currently if you didn't deploy or remove workers - aqua types change and aqua compilation will fail DXJ-380 default dependencies should not be automatically set in config.yaml explicitly DXJ-377 `fluence run` should always return valid json
right now, If function returns nothing, cli returns 'undefined'. instead, it should return nothing. Nothing is a valid json. if there are other cases where flox returns invalid json, they should be fixed as well DXJ-121 Add binary releases for rust dependencies so it installs faster
Discuss with rust team Need to be able to download and install pre-built version of Marine (DX is faster!) DXJ-391 Remove aqua cli from fluence cli DXJ-368 Deploy without building
It should be possible to deploy with forced rebuilding of everything DXJ-369 workers deploy e2e tests DXJ-362 Warn users that they overriden depenendecies
If user set their own versions of dependencies instead of using the recommended compatible versions - add a short warning so it's more transparent and to avoid accidental problems when experimenting DXJ-329 Fluence dependency install should work without a project
expectation: DXJ-363 Add an optional `fluenceVersion` property to fluence.yaml
This will include all the versions from the versions.json file (including rust peer version) so we can be sure our examples are working with local peers and we know which version of local peer to use in order to run the example DXJ-365 VSCode Aqua linter doesn't work with Fluence CLI projects
For some basic directory, the linter works as expected: In a Fluence CLI project, the linter doesn't work: DXJ-120 Add `unstable` matrix versions
This should be a separate Fluence CLI build that uses all unstable versions of all of the dependencies. Stable versions should be used by default and not hardcoded in Fluence CLI itself DXJ-265 Toolchain version mismatch checking should be done in fcli
platform: Ubuntu 18.04.3 LTS rust: stable-x86_64-unknown-linux-gnu example used:
on
valery found that the toolchain versioning were not correct Your active toolchain is Expected behavior: fcli should take care of those mismatches. DXJ-284 Show all fluence cli dependencies
Currently there is a DXJ-335 Show logs of serverless deployments DXJ-361 Add `dependency reset` command to remove all dependency overrides DXJ-379 'deal deploy' e2e tests with local blockchain DXJ-342 Don't allow init in non-empty directory DXJ-168 Remove duplication and useless docs for generated Fluence CLI config docs [Converted to "Fluence CLI config documentation" project]
There is a lot of room for improvement in the generated docs
|
98c74d8
to
29eafa4
Compare
c718d80
to
bd148ad
Compare
bd148ad
to
92c6958
Compare
DXJ-458 Make comments in configs optional
When using CLI for the first time ask the user if he wants to see examples and docs right inside the configs themselves and remember this setting for the user Also bring back the links to the online docs DXJ-373 Return DummyDealId when deploying workers
Right now, after workers are deployed, there is no way to resolve them via Registry. Because no one knows what "deal id" was used to register in Registry! CLI has to provide that information to the user. It may need to retrieve that information from Nox first. |
30ebf97
to
54aca2e
Compare
54aca2e
to
cbfa022
Compare
cbfa022
to
9782d14
Compare
f28c3f3
to
c7fffc4
Compare
754b5bf
to
e3fd585
Compare
596e1ac
to
199e412
Compare
199e412
to
a5efc40
Compare
a5efc40
to
30e58b3
Compare
1f77dd9
to
67e85ab
Compare
67e85ab
to
2edae91
Compare
2edae91
to
84e022e
Compare
4981b91
to
242fca4
Compare
242fca4
to
225ee94
Compare
225ee94
to
1266e19
Compare
This PR contains the following updates:
0.7.2
->0.13.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.