build(deps): bump dart-lang/setup-dart from 1.3 to 1.4

[dependabot]

Bumps dart-lang/setup-dart from 1.3 to 1.4.

Commits

• a57a6c0 Reusable workflow for publishing. (#64)
• 7b1734b Automatically create OIDC token for pub.dev. (#60)
• 745c09d Update and cleanup README (#63)
• 196f545 Update README.md (#53)
• 5676714 Run tests on a schedule (#54)
• c89375b Bump actions/checkout from 2 to 3 (#51)
• 6dbcbd7 Create dependabot.yaml (#49)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[cpswan]

@dependabot rebase

[dependabot]

Looks like this PR is already up-to-date with trunk! If you'd still like to recreate it from scratch, overwriting any edits, you can request @dependabot recreate.

[cpswan]

@gkc @murali-shris @sitaram-kalluri any ideas why this is happening?

Run flutter analyze
  flutter analyze
  shell: /usr/bin/bash -e {0}
  env:
    PUB_CACHE: /home/runner/.pub-cache
    DART_HOME: /opt/hostedtoolcache/dart-sdk
Analyzing at_client_mobile...                                   

   info • 'syncService' is deprecated and shouldn't be used. Use atClientManager.atClient.syncService • lib/src/at_client_service.dart:348:37 • deprecated_member_use

1 issue found. (ran in 7.[2](https://github.com/atsign-foundation/at_client_sdk/actions/runs/3934825279/jobs/6733881737#step:11:2)s)
Error: Process completed with exit code 1.

[gkc]

I deprecated a method.

[cpswan]

@gkc so do we need to modify the tests so they don't trip up on that?

[gkc]

Yes. We need to be free to deprecate methods. I'll change the check.

[gkc]

FYI see this ticket: flutter/flutter#31918

[gkc]

Anyway ... I'll change the checks, add the --no-fatal-info flag, verify that it works and if it does then I'll make changes in the other repos also.

[gkc]

Interesting that flutter analyze exits with 1, dart analyze exits with 0

gary@gkc2019-2 at_client_mobile % flutter analyze
Analyzing at_client_mobile...                                           

   info • 'syncService' is deprecated and shouldn't be used. Use atClientManager.atClient.syncService • lib/src/at_client_service.dart:348:37 •
          deprecated_member_use

1 issue found. (ran in 0.9s)
gary@gkc2019-2 at_client_mobile % echo $?
1


gary@gkc2019-2 at_client_mobile % dart analyze
Analyzing at_client_mobile...          0.9s

   info • lib/src/at_client_service.dart:348:37 • 'syncService' is deprecated and shouldn't be used. Use atClientManager.atClient.syncService. Try
          replacing the use of the deprecated member with the replacement. • deprecated_member_use

1 issue found.
gary@gkc2019-2 at_client_mobile % echo $?
0

[gkc]

Added --no-fatal-infos flag when running flutter analyze in the github workflow