Google Git
Sign in
dart / external / github.com / flutter / gallery / c591b0570390b767dc6ae039eacaa6328fd17eac
commitc591b0570390b767dc6ae039eacaa6328fd17eac[log] [tgz]
authordependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>Mon Apr 24 14:50:04 2023 +0200
committerGitHub <noreply@github.com>Mon Apr 24 14:50:04 2023 +0200
tree8807e75c9f706ef51b9fdc59c613f0bce673b8bf
parent610003ea5040313c8d3f3f6964a95fa622d8e520 [diff]
Bump github/codeql-action from 2.2.5 to 2.2.9 (#919)

Bumps [github/codeql-action](https://github.com/github/codeql-action)
from 2.2.5 to 2.2.9.
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/github/codeql-action/blob/main/CHANGELOG.md">github/codeql-action's
changelog</a>.</em></p>
<blockquote>
<h1>CodeQL Action Changelog</h1>
<h2>[UNRELEASED]</h2>
<p>No user facing changes.</p>
<h2>2.2.9 - 27 Mar 2023</h2>
<ul>
<li>Customers post-processing the SARIF output of the
<code>analyze</code> Action before uploading it to Code Scanning will
benefit from an improved debugging experience. <a
href="https://redirect.github.com/github/codeql-action/pull/1598">#1598</a>
<ul>
<li>The CodeQL Action will now upload a SARIF file with debugging
information to Code Scanning on failed runs for customers using
<code>upload: false</code>. Previously, this was only available for
customers using the default value of the <code>upload</code> input.</li>
<li>The <code>upload</code> input to the <code>analyze</code> Action now
accepts the following values:
<ul>
<li><code>always</code> is the default value, which uploads the SARIF
file to Code Scanning for successful and failed runs.</li>
<li><code>failure-only</code> is recommended for customers
post-processing the SARIF file before uploading it to Code Scanning.
This option uploads debugging information to Code Scanning for failed
runs to improve the debugging experience.</li>
<li><code>never</code> avoids uploading the SARIF file to Code Scanning
even if the code scanning run fails. This is not recommended for
external users since it complicates debugging.</li>
<li>The legacy <code>true</code> and <code>false</code> options will be
interpreted as <code>always</code> and <code>failure-only</code>
respectively.</li>
</ul>
</li>
</ul>
</li>
</ul>
<h2>2.2.8 - 22 Mar 2023</h2>
<ul>
<li>Update default CodeQL bundle version to 2.12.5. <a
href="https://redirect.github.com/github/codeql-action/pull/1585">#1585</a></li>
</ul>
<h2>2.2.7 - 15 Mar 2023</h2>
<p>No user facing changes.</p>
<h2>2.2.6 - 10 Mar 2023</h2>
<ul>
<li>Update default CodeQL bundle version to 2.12.4. <a
href="https://redirect.github.com/github/codeql-action/pull/1561">#1561</a></li>
</ul>
<h2>2.2.5 - 24 Feb 2023</h2>
<ul>
<li>Update default CodeQL bundle version to 2.12.3. <a
href="https://redirect.github.com/github/codeql-action/pull/1543">#1543</a></li>
</ul>
<h2>2.2.4 - 10 Feb 2023</h2>
<p>No user facing changes.</p>
<h2>2.2.3 - 08 Feb 2023</h2>
<ul>
<li>Update default CodeQL bundle version to 2.12.2. <a
href="https://redirect.github.com/github/codeql-action/pull/1518">#1518</a></li>
</ul>
<h2>2.2.2 - 06 Feb 2023</h2>
<ul>
<li>Fix an issue where customers using the CodeQL Action with the <a
href="https://docs.github.com/en/enterprise-server@3.7/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance#configuring-codeql-analysis-on-a-server-without-internet-access">CodeQL
Action sync tool</a> would not be able to obtain the CodeQL tools. <a
href="https://redirect.github.com/github/codeql-action/pull/1517">#1517</a></li>
</ul>
<h2>2.2.1 - 27 Jan 2023</h2>
<p>No user facing changes.</p>
<h2>2.2.0 - 26 Jan 2023</h2>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/github/codeql-action/commit/04df1262e6247151b5ac09cd2c303ac36ad3f62b"><code>04df126</code></a>
Merge pull request <a
href="https://redirect.github.com/github/codeql-action/issues/1608">#1608</a>
from github/update-v2.2.9-fb32c3fef</li>
<li><a
href="https://github.com/github/codeql-action/commit/f0988cbd79ff403435044fdb9947c1ec20d01f6a"><code>f0988cb</code></a>
Move changelog note to correct section</li>
<li><a
href="https://github.com/github/codeql-action/commit/fef20d6c357cfcd261d53a2d55b0b2132d0f6892"><code>fef20d6</code></a>
Update changelog for v2.2.9</li>
<li><a
href="https://github.com/github/codeql-action/commit/fb32c3fefdc4ffebe80488e4ed5d862348621d72"><code>fb32c3f</code></a>
Merge pull request <a
href="https://redirect.github.com/github/codeql-action/issues/1605">#1605</a>
from github/henrymercer/diagnostics-grouping-workaround</li>
<li><a
href="https://github.com/github/codeql-action/commit/329c022f486ae3deced8c256a11365c7a7799041"><code>329c022</code></a>
Just check the number of locations</li>
<li><a
href="https://github.com/github/codeql-action/commit/c8935d5a9dbe3383438a0f489ca0c6f7fa2743c3"><code>c8935d5</code></a>
Remove duplicate locations from failed run SARIF</li>
<li><a
href="https://github.com/github/codeql-action/commit/ade432fd683e818e4efbc4a803160f5b4f13926e"><code>ade432f</code></a>
Remove duplicate locations from output of <code>database
interpret-results</code></li>
<li><a
href="https://github.com/github/codeql-action/commit/6f852eeb3899f7918bf6f5d7a201a98a18ce5b51"><code>6f852ee</code></a>
Implement removing duplicate locations from a SARIF file</li>
<li><a
href="https://github.com/github/codeql-action/commit/097ab4665fecf3c04acc545d74e40d782046c9e3"><code>097ab46</code></a>
Speed up checks a bit by just running the standard suite</li>
<li><a
href="https://github.com/github/codeql-action/commit/befd804b8b0075fbae00d57bc215f6e0ea6033a5"><code>befd804</code></a>
Extend diagnostics export integration test to capture location bug</li>
<li>Additional commits viewable in <a
href="https://github.com/github/codeql-action/compare/32dc499307d133bb5085bae78498c0ac2cf762d5...04df1262e6247151b5ac09cd2c303ac36ad3f62b">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=github/codeql-action&package-manager=github_actions&previous-version=2.2.5&new-version=2.2.9)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

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-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

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)


</details>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Pierre-Louis <6655696+guidezpl@users.noreply.github.com>
1 file changed
tree: 8807e75c9f706ef51b9fdc59c613f0bce673b8bf
  1. .github/
  2. android/
  3. fonts/
  4. ios/
  5. lib/
  6. linux/
  7. macos/
  8. test/
  9. test_benchmarks/
  10. test_driver/
  11. test_goldens/
  12. tool/
  13. web/
  14. windows/
  15. .firebaserc
  16. .gitignore
  17. .metadata
  18. analysis_options.yaml
  19. CHANGELOG.md
  20. deferred_components_loading_units.yaml
  21. firebase.json
  22. l10n.yaml
  23. LICENSE
  24. pubspec.lock
  25. pubspec.yaml
  26. README.md
  27. screenshots.md
README.md

Flutter Gallery

Flutter Gallery is a resource to help developers evaluate and use Flutter. It is a collection of Material Design & Cupertino widgets, behaviors, and vignettes implemented with Flutter. We often get asked how one can see Flutter in action, and this gallery demonstrates what Flutter provides and how it behaves in the wild.

Flutter Gallery

Features

  • Showcase for material, cupertino, and other widgets
  • Adaptive layout for mobile and desktop
  • State restoration support
  • Settings to text scaling, text direction, locale, theme, and more...
  • Demo for animations
  • Foldable support and demo for dual_screen
  • Deferred loading
  • CI/CD
  • ...and much more!

Supported Platforms

Flutter Gallery has been built to support multiple platforms. These include:

Running

One can run the gallery locally for any of these platforms. For desktop platforms, please see the Flutter docs for the latest requirements.

cd gallery/
flutter pub get
flutter run

Flutter master channel

The Flutter Gallery targets Flutter‘s master channel. As such, it can take advantage of new SDK features that haven’t landed in the stable channel.

If you'd like to run the Flutter Gallery, you may have to switch to the master channel first:

flutter channel master
flutter upgrade

When you're done, use this command to return to the safety of the stable channel:

flutter channel stable
flutter upgrade

Development

If this is the first time building the Flutter Gallery, the localized code will not be present in the project directory. However, after running the application for the first time, a synthetic package will be generated containing the app's localizations through importing package:flutter_gen/gen_l10n/.

flutter pub get
flutter pub run grinder l10n

See separate README for more details.

flutter pub get
flutter pub run grinder update-code-segments

See separate README for more details.

  1. Convert your animation to a .gif file. Ideally, use a background color of 0xFF030303 to ensure the animation blends into the background of the app.

  2. Add your new .gif file to the assets directory under assets/splash_effects. Ensure the name follows the format splash_effect_$num.gif. The number should be the next number after the current largest number in the repository.

  3. Update the map _effectDurations in splash.dart to include the number of the new .gif as well as its estimated duration. The duration is used to determine how long to display the splash animation at launch.

Releasing

The process is largely automated and easy to set in motion.

First things first, bump the pubspec.yaml version number. This can be in a PR making a change or a separate PR. Use semantic versioning to determine which part to increment. The version number after the + should also be incremented. For example 1.2.3+010203 with a patch should become 1.2.4+010204.

Then, use the following workflows. It is strongly recommended to use the staging/beta environments when available, before deploying to production.

  • Deploy to Play Store: Uses Fastlane to create a beta (freely available on the Play Store), promote an existing beta to production, or publish straight to production (Play Store).

    Note Once an .aab is released with a particular version number, it can't be replaced. The version number must be incremented again.

  • Deploy to web: Deploys a web build to the Firebase-hosted staging or production site.
  • Draft GitHub release: Drafts a GitHub release, including automatically generated release notes and packaged builds for Android, macOS, Linux, and Windows.

    Note The release draft is private until published. Upon being published, the specified version tag will be created.

  • Publish on Windows Store: A workflow file for releasing to the Windows Store. This repository is not currently set up to publish new versions of the current Windows Store listing. Requires running msstore init within the repository and setting repository/environment secrets .

    See the instructions in the documentation for more information.

For posterity, information about doing these things locally is available at go/flutter-gallery-manual-deployment.

Tests

The gallery has its own set of unit, golden, and integration tests.

In addition, Flutter itself uses the gallery in tests. To enable breaking changes, the gallery version is pinned in two places: