diff --git a/.github/actions/clean-runner-disk-windows/action.yml b/.github/actions/clean-runner-disk-windows/action.yml new file mode 100644 index 0000000..d11df1f --- /dev/null +++ b/.github/actions/clean-runner-disk-windows/action.yml @@ -0,0 +1,68 @@ +name: 'Clean Runner Disk (Windows)' +description: 'Cleans the GitHub Actions Windows runner disk by removing unused toolchains and SDKs to free up space on C:.' +runs: + using: composite + steps: + - name: Show disk usage before cleaning + run: Get-PSDrive -PSProvider FileSystem | Format-Table -AutoSize + shell: pwsh + - name: 'Top-level directories on C: before cleaning' + run: | + Get-ChildItem -Path C:\ -Directory -Force -ErrorAction SilentlyContinue | + ForEach-Object { + $size = (Get-ChildItem -Path $_.FullName -Recurse -Force -ErrorAction SilentlyContinue | + Measure-Object -Property Length -Sum).Sum + [PSCustomObject]@{ + Path = $_.FullName + SizeGB = [math]::Round($size / 1GB, 2) + } + } | Sort-Object SizeGB -Descending | Format-Table -AutoSize + shell: pwsh + - name: Clean runner disk + run: | + $paths = @( + 'C:\Android', + 'C:\hostedtoolcache', + 'C:\Program Files\dotnet', + 'C:\Program Files (x86)\dotnet', + 'C:\ghcup', + 'C:\Program Files\Haskell', + 'C:\Program Files\Haskell Platform', + 'C:\Strawberry', + 'C:\msys64', + 'C:\Miniconda', + 'C:\Program Files\MongoDB', + 'C:\Program Files\PostgreSQL', + 'C:\PostgreSQL', + 'C:\Program Files\Google\Chrome', + 'C:\Program Files (x86)\Google\Chrome', + 'C:\Program Files\Mozilla Firefox', + 'C:\selenium', + 'C:\SeleniumWebDrivers', + 'C:\vcpkg', + 'C:\tools' + ) + foreach ($p in $paths) { + if (Test-Path -LiteralPath $p) { + Write-Host "Removing $p" + Remove-Item -LiteralPath $p -Recurse -Force -ErrorAction Continue + } else { + Write-Host "Skipping $p (not found)" + } + } + shell: pwsh + - name: Show disk usage after cleaning + run: Get-PSDrive -PSProvider FileSystem | Format-Table -AutoSize + shell: pwsh + - name: 'Top-level directories on C: after cleaning' + run: | + Get-ChildItem -Path C:\ -Directory -Force -ErrorAction SilentlyContinue | + ForEach-Object { + $size = (Get-ChildItem -Path $_.FullName -Recurse -Force -ErrorAction SilentlyContinue | + Measure-Object -Property Length -Sum).Sum + [PSCustomObject]@{ + Path = $_.FullName + SizeGB = [math]::Round($size / 1GB, 2) + } + } | Sort-Object SizeGB -Descending | Format-Table -AutoSize + shell: pwsh diff --git a/.github/gx.toml b/.github/gx.toml index 8b47d33..49c1a9b 100644 --- a/.github/gx.toml +++ b/.github/gx.toml @@ -19,4 +19,4 @@ "plexsystems/container-structure-test-action" = "~0.3.0" [actions.overrides] -"docker/metadata-action" = [{ workflow = ".github/workflows/build.yml", job = "test_image", step = 5, version = "~5.10.0" }, { workflow = ".github/workflows/ci.yml", job = "test_image", step = 5, version = "~5.10.0" }, { workflow = ".github/workflows/release.yml", job = "release_android", step = 2, version = "~5.10.0" }, { workflow = ".github/workflows/windows.yml", job = "test_windows", step = 3, version = "~5.7.0" }] +"docker/metadata-action" = [{ workflow = ".github/workflows/build.yml", job = "test_image", step = 5, version = "~5.10.0" }, { workflow = ".github/workflows/ci.yml", job = "test_image", step = 5, version = "~5.10.0" }, { workflow = ".github/workflows/release.yml", job = "release_android", step = 2, version = "~5.10.0" }, { workflow = ".github/workflows/windows.yml", job = "test_windows", step = 3, version = "~5.7.0" }, { workflow = ".github/workflows/windows.yml", job = "test_windows", step = 4, version = "~5.7.0" }] diff --git a/.github/workflows/windows.yml b/.github/workflows/windows.yml index 58e3263..98c9d2b 100644 --- a/.github/workflows/windows.yml +++ b/.github/workflows/windows.yml @@ -20,6 +20,9 @@ jobs: - name: Checkout repository uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1 + - name: Clean runner disk + uses: ./.github/actions/clean-runner-disk-windows + - name: Login to Docker Hub uses: docker/login-action@5e57cd118135c172c3672efd75eb46360885c0ef # v3.6.0 with: diff --git a/docs/contributing.md b/docs/contributing.md index 1720653..1efb4fb 100644 --- a/docs/contributing.md +++ b/docs/contributing.md @@ -2,6 +2,12 @@ # Contributing +## Repository wiki + +An AI-generated wiki for this repository is available at [deepwiki.com/gmeligio/flutter-docker-image](https://deepwiki.com/gmeligio/flutter-docker-image). It covers architecture, Dockerfile stages, the CI/release pipeline, and more. + +The wiki is kept current automatically: DeepWiki re-indexes the repository whenever it detects the DeepWiki badge in `readme.md`. No manual action is required after merging to `main`. + ## Editing GitHub Actions workflows GitHub Actions versions are tracked with [gx](https://github.com/gmeligio/gx). The manifest at `.github/gx.toml` is the source of truth for version constraints, and `.github/gx.lock` records the resolved SHAs. Workflows must use SHA pins with a `# vX.Y.Z` comment. diff --git a/docs/src/badges.mdx b/docs/src/badges.mdx index 6969f51..05d952d 100644 --- a/docs/src/badges.mdx +++ b/docs/src/badges.mdx @@ -8,6 +8,6 @@ export const channelColor = { export const channelUrl = 'https://docs.flutter.dev/release/archive?tab=linux'; export const channelBadgeUrl = `https://img.shields.io/static/v1?label=${encodeURIComponent('channel')}&message=${encodeURIComponent(flutterChannel)}&color=${encodeURIComponent(channelColor[flutterChannel])}`; -[![openssf scorecard](https://api.scorecard.dev/projects/github.com/gmeligio/flutter-docker-image/badge)](https://scorecard.dev/viewer/?uri=github.com/gmeligio/flutter-docker-image) +[![openssf scorecard](https://api.scorecard.dev/projects/github.com/gmeligio/flutter-docker-image/badge)](https://scorecard.dev/viewer/?uri=github.com/gmeligio/flutter-docker-image) [![Ask DeepWiki](https://deepwiki.com/badge.svg)](https://deepwiki.com/gmeligio/flutter-docker-image) channel [![flutter-android version](https://img.shields.io/docker/v/gmeligio/flutter-android?label=flutter-android%20version)](https://hub.docker.com/r/gmeligio/flutter-android/tags) [![flutter-android pulls](https://img.shields.io/docker/pulls/gmeligio/flutter-android?label=flutter-android%20pulls)](https://hub.docker.com/r/gmeligio/flutter-android/tags) diff --git a/docs/src/contributing.mdx b/docs/src/contributing.mdx index 2f276d8..6eeda36 100644 --- a/docs/src/contributing.mdx +++ b/docs/src/contributing.mdx @@ -1,5 +1,11 @@ # Contributing +## Repository wiki + +An AI-generated wiki for this repository is available at [deepwiki.com/gmeligio/flutter-docker-image](https://deepwiki.com/gmeligio/flutter-docker-image). It covers architecture, Dockerfile stages, the CI/release pipeline, and more. + +The wiki is kept current automatically: DeepWiki re-indexes the repository whenever it detects the DeepWiki badge in `readme.md`. No manual action is required after merging to `main`. + ## Editing GitHub Actions workflows GitHub Actions versions are tracked with [`gx`](https://github.com/gmeligio/gx). The manifest at `.github/gx.toml` is the source of truth for version constraints, and `.github/gx.lock` records the resolved SHAs. Workflows must use SHA pins with a `# vX.Y.Z` comment. diff --git a/openspec/changes/archive/2026-05-10-add-deepwiki-integration/.openspec.yaml b/openspec/changes/archive/2026-05-10-add-deepwiki-integration/.openspec.yaml new file mode 100644 index 0000000..ac20efa --- /dev/null +++ b/openspec/changes/archive/2026-05-10-add-deepwiki-integration/.openspec.yaml @@ -0,0 +1,2 @@ +schema: spec-driven +created: 2026-05-10 diff --git a/openspec/changes/archive/2026-05-10-add-deepwiki-integration/.verify-passed b/openspec/changes/archive/2026-05-10-add-deepwiki-integration/.verify-passed new file mode 100644 index 0000000..b0aad4d --- /dev/null +++ b/openspec/changes/archive/2026-05-10-add-deepwiki-integration/.verify-passed @@ -0,0 +1 @@ +passed diff --git a/openspec/changes/archive/2026-05-10-add-deepwiki-integration/design.md b/openspec/changes/archive/2026-05-10-add-deepwiki-integration/design.md new file mode 100644 index 0000000..2ebaea9 --- /dev/null +++ b/openspec/changes/archive/2026-05-10-add-deepwiki-integration/design.md @@ -0,0 +1,81 @@ +## Context + +The repo's user-facing docs are limited to `readme.md` (compiled from `docs/src/readme.mdx` via `docs/src/compile.js`) plus `docs/contributing.md` and `docs/windows.md`. There is no architectural overview, no Q&A surface, and no auto-update story. Cognition AI's hosted DeepWiki indexes any public GitHub repo for free, generates an architecture-aware wiki with diagrams and a chat interface, and — when the repo carries a DeepWiki badge — re-indexes automatically as `main` evolves. The wiki is reached by replacing `github.com` with `deepwiki.com` in the repo URL. + +This proposal opts the repo into that hosted service. It does not stand up a docs site, replace the existing MDX pipeline, or send any code to a third party that doesn't already read it from public GitHub. + +## Goals / Non-Goals + +**Goals:** +- Give README readers a one-click path to an AI-generated wiki for the repo. +- Keep the wiki current without any maintainer action after merge. +- Keep the existing MDX→MD docs pipeline intact and authoritative for committed markdown. + +**Non-Goals:** +- Self-hosting DeepWiki or any OSS variant (deepwiki-open, OpenDeepWiki, RepoWiki). The hosted free tier is sufficient for a public repo of this size. +- Replacing the MDX docs pipeline or migrating to Mintlify/Docusaurus/MkDocs. +- Wiring the DeepWiki MCP server into shared tooling. Individual contributors can register `https://mcp.deepwiki.com/mcp` in their own Claude Code config; that is out of scope for this repo change. +- Authoring a `.devin/wiki.json` outline up front. The default DeepWiki outline is the baseline; a steering file is a follow-up that should be motivated by an observed gap, not by speculation. +- Generating reference docs from Dockerfiles or scripts. + +## Decisions + +### Use hosted DeepWiki, not a self-hosted alternative + +DeepWiki hosted (`deepwiki.com`) is free for public repos, is already operating against this repo's public GitHub URL, and requires zero infra. Self-hosted alternatives (deepwiki-open, OpenDeepWiki, RepoWiki) would require provisioning a server, paying for LLM tokens, and maintaining another service — all to reproduce a free capability. The trade is vendor lock-in to Cognition AI's roadmap, which is acceptable because the integration surface is one badge URL that any replacement could honor or be re-pointed away from. + +Source: , . + +### Source the badge in `docs/src/badges.mdx`, not directly in `readme.md` + +`readme.md` is auto-generated and carries the comment ``. Editing it directly would be undone by the next compile. The MDX source for the badge row already lives at `docs/src/badges.mdx`. Adding the DeepWiki badge there flows it into the recompiled README and keeps the existing pipeline as the single source of truth. + +### Defer `.devin/wiki.json` until a real gap is observed + +DeepWiki accepts a `.devin/wiki.json` with `repo_notes` and a `pages` outline that overrides the default page structure. For a repo this small with self-evident structure (clearly named Dockerfiles, scripts, workflows, MDX docs), the default outline is expected to be adequate. Authoring a `pages` list before seeing what DeepWiki produces is speculative, adds a `.devin/` directory contributors must understand, and creates a config that can drift from the codebase. The cheaper path is: ship the badge, observe the generated wiki, then add steering only for the specific gaps that materialize. Adding the file later is a one-PR follow-up with no rework cost. + +### Trust badge-presence as the auto-refresh trigger + +DeepWiki refreshes wikis automatically for repos that carry a DeepWiki badge in their README. The repo already gets DeepWiki-generated content because it's public; the badge is what unlocks the auto-refresh path. No CI hook, no webhook, no scheduled workflow is needed. + +Source: badge generator and behavior described at and the DeepWiki dev guide. + +### Use the standard Shields-style badge + +The DeepWiki badge format used widely in the ecosystem is `https://deepwiki.com/badge.svg` linking to `https://deepwiki.com//`. This matches the visual style of the other badges already in the README (OpenSSF Scorecard, channel, Docker version, Docker pulls) and avoids inventing a custom badge. + +## Automated Test Strategy + +This change has no runtime code path, so the verification surface is small and document-shaped. The critical path is: (1) the badge ends up in the regenerated `readme.md`, (2) the contributing doc gains the new section. + +- **Build verification**: run the existing `npm run build` (or `npm run readme` + `npm run contributing`) inside `docs/src/` and confirm both regenerated files reflect the source changes. This is the same pipeline contributors already use; no new infrastructure. +- **Manual smoke check**: open `https://deepwiki.com/gmeligio/flutter-docker-image` after merge and confirm the wiki renders. This is the user-visible outcome and cannot be automated against a third-party service. +- **No new test infrastructure** is introduced. + +## Observability + +Failures are loud and shallow: +- A broken badge URL would render as a broken-image icon in `readme.md` — visible immediately on GitHub. +- A stale wiki (auto-refresh not firing) would surface to readers as out-of-date page content. Detection: spot-check after notable merges. + +There is no silent-failure path that affects image users (the Docker images themselves are untouched). No new logs, metrics, or alerts are warranted. + +## Risks / Trade-offs + +- **[Vendor dependency on Cognition AI]** → Mitigation: integration surface is one badge URL. If Cognition discontinues the free tier we can remove the badge with no functional regression beyond the wiki page itself, or point the same badge URL at a self-hosted deepwiki-open deployment. +- **[Generated content quality is outside maintainer control]** → Mitigation: the wiki is supplementary to the README, not load-bearing for image users. If the default outline is materially wrong, add `.devin/wiki.json` as a follow-up. +- **[Auto-refresh cadence is undocumented]** → Mitigation: stale-by-a-few-hours is acceptable for a docs surface; no SLA is being promised to readers. + +## Migration Plan + +Single-PR rollout, no data migration: +1. Add the badge to `docs/src/badges.mdx` and recompile docs. +2. Add the contributing section. +3. Merge. +4. Within DeepWiki's refresh window, the wiki at `deepwiki.com/gmeligio/flutter-docker-image` reflects the latest `main`. + +Rollback: revert the PR. The wiki itself remains accessible (DeepWiki indexes public repos regardless), but auto-refresh stops and the badge disappears from the README. No image, CI, or release impact. + +## Open Questions + +None blocking. The DeepWiki refresh cadence is not publicly documented as a hard SLA, but that is an acceptable unknown for a supplementary docs surface. diff --git a/openspec/changes/archive/2026-05-10-add-deepwiki-integration/proposal.md b/openspec/changes/archive/2026-05-10-add-deepwiki-integration/proposal.md new file mode 100644 index 0000000..0ae2c8d --- /dev/null +++ b/openspec/changes/archive/2026-05-10-add-deepwiki-integration/proposal.md @@ -0,0 +1,26 @@ +## Why + +CI engineers landing on the repo today only get a static README and two short markdown files. There is no way to ask "how does the windows pipeline cache the SDK?" or "what changed in the android Dockerfile recently?" without grepping the source. Hosted DeepWiki indexes any public GitHub repo for free, generates an architecture-aware wiki, and auto-refreshes when the repo carries a DeepWiki badge — so a one-time integration gives users a queryable, always-current doc surface at zero infra cost. + +This passes the relevance gate: the badge and the linked wiki are visible to anyone reading the README, and the wiki itself is the experience the CI engineer notices when they click through. + +## What Changes + +- Add a DeepWiki badge to the README header so users can reach `deepwiki.com/gmeligio/flutter-docker-image` in one click. Source the badge in `docs/src/badges.mdx` so the existing MDX→MD compile carries it into `readme.md`. +- Document the integration in `docs/src/contributing.mdx` (recompiled into `docs/contributing.md`) so contributors know the wiki exists and that the badge in the README is what keeps it auto-refreshing. +- Defer page-outline steering (`.devin/wiki.json`) until DeepWiki's default outline is observed — add it as a follow-up only if a load-bearing gap appears. +- No CI changes, no new dependencies in the Dockerfiles, no changes to image contents. + +## Capabilities + +### New Capabilities +- `repository-wiki`: An always-current, AI-generated knowledge base for the repository, reachable from the README via a badge and refreshed automatically when the repo changes. + +### Modified Capabilities + + +## Impact + +- **Files modified**: `docs/src/badges.mdx`, `docs/src/contributing.mdx`, regenerated `readme.md` and `docs/contributing.md` via `docs/src/compile.js` +- **External dependency**: Hosted DeepWiki service (`deepwiki.com`) — free for public repos, owned by Cognition AI. No code or secrets sent; DeepWiki reads the public repo directly. +- **No impact on**: Docker images, CI workflows, release pipeline, version bump scripts, end-user `docker run` UX. diff --git a/openspec/changes/archive/2026-05-10-add-deepwiki-integration/specs/repository-wiki/spec.md b/openspec/changes/archive/2026-05-10-add-deepwiki-integration/specs/repository-wiki/spec.md new file mode 100644 index 0000000..02d65b0 --- /dev/null +++ b/openspec/changes/archive/2026-05-10-add-deepwiki-integration/specs/repository-wiki/spec.md @@ -0,0 +1,42 @@ +## ADDED Requirements + +### Requirement: README exposes a DeepWiki entry point + +The README SHALL display a DeepWiki badge in the header badge row that links to `https://deepwiki.com/gmeligio/flutter-docker-image`, so a CI engineer reading the repo on GitHub or Docker Hub can reach the AI-generated wiki in one click. + +The badge SHALL be authored in `docs/src/badges.mdx` (the source for the existing MDX→MD pipeline) so a recompile keeps `readme.md` in sync. + +#### Scenario: Reader on GitHub clicks through to the wiki + +- **GIVEN** a CI engineer is reading `readme.md` on GitHub +- **WHEN** they click the DeepWiki badge in the header +- **THEN** the browser navigates to the project's DeepWiki page +- **AND** the page renders the auto-generated wiki for this repository + +#### Scenario: Recompiling docs preserves the badge + +- **GIVEN** the maintainer edits any source file under `docs/src/` +- **WHEN** they run the docs compile script +- **THEN** the regenerated `readme.md` still contains the DeepWiki badge in the header badge row + +### Requirement: Wiki refreshes automatically when the repository changes + +The repository SHALL opt into DeepWiki's badge-driven auto-refresh behavior so that the wiki a reader sees stays in step with the current state of `main` without any manual maintainer action. + +The opt-in mechanism SHALL be the presence of the DeepWiki badge in `readme.md` (the same badge required above). + +#### Scenario: Reader after a merge sees current content + +- **GIVEN** a change has been merged to `main` that modifies `android.Dockerfile` or `windows.Dockerfile` +- **WHEN** a reader visits the project's DeepWiki page after the next refresh cycle +- **THEN** the wiki content reflects the merged change (no manual rebuild step required from the maintainer) + +### Requirement: Contributors are told how the wiki works + +`docs/contributing.md` (compiled from `docs/src/contributing.mdx`) SHALL include a short section pointing contributors at the DeepWiki and explaining that the badge in the README is what keeps the wiki fresh. + +#### Scenario: New contributor opens contributing.md + +- **GIVEN** a new contributor opens `docs/contributing.md` +- **WHEN** they read through the document +- **THEN** they find a section that names DeepWiki, links to the wiki URL, and explains that the README badge enables auto-refresh diff --git a/openspec/changes/archive/2026-05-10-add-deepwiki-integration/tasks.md b/openspec/changes/archive/2026-05-10-add-deepwiki-integration/tasks.md new file mode 100644 index 0000000..6108ffb --- /dev/null +++ b/openspec/changes/archive/2026-05-10-add-deepwiki-integration/tasks.md @@ -0,0 +1,17 @@ +## 1. README badge + +- [x] 1.1 Add a DeepWiki badge to `docs/src/badges.mdx` linking to `https://deepwiki.com/gmeligio/flutter-docker-image`, using the same Shields-style markup as the surrounding badges +- [x] 1.2 Run `npm run readme` (or `npm run build`) inside `docs/src/` to regenerate `readme.md` +- [x] 1.3 Confirm the regenerated `readme.md` carries the DeepWiki badge in the header badge row and commit both files + +## 2. Contributing docs + +- [x] 2.1 Add a "Repository wiki" section to `docs/src/contributing.mdx` that names DeepWiki, links to `https://deepwiki.com/gmeligio/flutter-docker-image`, and explains that the README badge is what enables auto-refresh +- [x] 2.2 Run `npm run contributing` to regenerate `docs/contributing.md` +- [x] 2.3 Commit `docs/src/contributing.mdx` and `docs/contributing.md` together + +## 3. Verification + +- [ ] 3.1 Re-read the regenerated `readme.md` on GitHub's preview and confirm the DeepWiki badge renders and links correctly +- [ ] 3.2 After merge to `main`, open `https://deepwiki.com/gmeligio/flutter-docker-image` and confirm the wiki renders +- [ ] 3.3 Note any material gaps in the default outline; if found, file a follow-up to add `.devin/wiki.json` diff --git a/openspec/specs/repository-wiki/spec.md b/openspec/specs/repository-wiki/spec.md new file mode 100644 index 0000000..d246bfe --- /dev/null +++ b/openspec/specs/repository-wiki/spec.md @@ -0,0 +1,44 @@ +# repository-wiki Specification + +## Requirements + +### Requirement: README exposes a DeepWiki entry point + +The README SHALL display a DeepWiki badge in the header badge row that links to `https://deepwiki.com/gmeligio/flutter-docker-image`, so a CI engineer reading the repo on GitHub or Docker Hub can reach the AI-generated wiki in one click. + +The badge SHALL be authored in `docs/src/badges.mdx` (the source for the existing MDX→MD pipeline) so a recompile keeps `readme.md` in sync. + +#### Scenario: Reader on GitHub clicks through to the wiki + +- **GIVEN** a CI engineer is reading `readme.md` on GitHub +- **WHEN** they click the DeepWiki badge in the header +- **THEN** the browser navigates to the project's DeepWiki page +- **AND** the page renders the auto-generated wiki for this repository + +#### Scenario: Recompiling docs preserves the badge + +- **GIVEN** the maintainer edits any source file under `docs/src/` +- **WHEN** they run the docs compile script +- **THEN** the regenerated `readme.md` still contains the DeepWiki badge in the header badge row + +### Requirement: Wiki refreshes automatically when the repository changes + +The repository SHALL opt into DeepWiki's badge-driven auto-refresh behavior so that the wiki a reader sees stays in step with the current state of `main` without any manual maintainer action. + +The opt-in mechanism SHALL be the presence of the DeepWiki badge in `readme.md` (the same badge required above). + +#### Scenario: Reader after a merge sees current content + +- **GIVEN** a change has been merged to `main` that modifies `android.Dockerfile` or `windows.Dockerfile` +- **WHEN** a reader visits the project's DeepWiki page after the next refresh cycle +- **THEN** the wiki content reflects the merged change (no manual rebuild step required from the maintainer) + +### Requirement: Contributors are told how the wiki works + +`docs/contributing.md` (compiled from `docs/src/contributing.mdx`) SHALL include a short section pointing contributors at the DeepWiki and explaining that the badge in the README is what keeps the wiki fresh. + +#### Scenario: New contributor opens contributing.md + +- **GIVEN** a new contributor opens `docs/contributing.md` +- **WHEN** they read through the document +- **THEN** they find a section that names DeepWiki, links to the wiki URL, and explains that the README badge enables auto-refresh diff --git a/readme.md b/readme.md index f59bbee..60d446e 100644 --- a/readme.md +++ b/readme.md @@ -1,6 +1,6 @@ -[![openssf scorecard](https://api.scorecard.dev/projects/github.com/gmeligio/flutter-docker-image/badge)](https://scorecard.dev/viewer/?uri=github.com/gmeligio/flutter-docker-image) [![channel](https://img.shields.io/static/v1?label=channel&message=stable&color=blue)](https://docs.flutter.dev/release/archive?tab=linux) [![flutter-android version](https://img.shields.io/docker/v/gmeligio/flutter-android?label=flutter-android%20version)](https://hub.docker.com/r/gmeligio/flutter-android/tags) [![flutter-android pulls](https://img.shields.io/docker/pulls/gmeligio/flutter-android?label=flutter-android%20pulls)](https://hub.docker.com/r/gmeligio/flutter-android/tags) +[![openssf scorecard](https://api.scorecard.dev/projects/github.com/gmeligio/flutter-docker-image/badge)](https://scorecard.dev/viewer/?uri=github.com/gmeligio/flutter-docker-image) [![Ask DeepWiki](https://deepwiki.com/badge.svg)](https://deepwiki.com/gmeligio/flutter-docker-image) [![channel](https://img.shields.io/static/v1?label=channel&message=stable&color=blue)](https://docs.flutter.dev/release/archive?tab=linux) [![flutter-android version](https://img.shields.io/docker/v/gmeligio/flutter-android?label=flutter-android%20version)](https://hub.docker.com/r/gmeligio/flutter-android/tags) [![flutter-android pulls](https://img.shields.io/docker/pulls/gmeligio/flutter-android?label=flutter-android%20pulls)](https://hub.docker.com/r/gmeligio/flutter-android/tags) # Flutter Docker Image