# Meshery v0.8.203

2026-02-08 · [Original release notes](https://github.com/meshery/meshery/releases/tag/v0.8.203) · [Full summary](https://ratatosk.io/en/releases/meshery/v0.8.203)

Breaking changes 7 · Important fixes 1 · Enhancements 3 · Dependency updates 2 · Other changes 46

## Breaking changes (7)

### Meshery remote capability-fetch retries now log at DEBUG

- Affects: remote-provider capability fetching with an empty token (Inferred)

When fetching fails, every failed attempt previously logged a WARN saying it would retry in 3 seconds; now the first failure and retry-exhaustion summary log at WARN.

Evidence: “- First failure: log one WARN so operators know something is wrong.” https://github.com/meshery/meshery/pull/17212

> - fix: reduce retry log spam when capability fetch fails @guan404ming (#17212)

### Changed `mesheryctl filter view` output format

- Affects: automation consuming `mesheryctl filter view` output (Inferred)

Previously, `--all` output retained only the `filters` key, and individual filter output used names such as `filter_file` and `user_id`. Now, `--all` includes page and pagination metadata, while YAML uses names such as `filterfile` and `userid`.

Evidence: “+filterfile: []” https://github.com/meshery/meshery/pull/17259

> - refactor: Consolidate --output-format handling in filter command  @shri771 (#17259)

### mesheryctl connection-not-found error code changed

- Affects: automation that inspects the mesheryctl connection-not-found error code (Inferred)

Previously, `ErrConnectionNotFoundCode` was `mesheryctl-1196`, which collided with an error code in meshery-server. It is now `mesheryctl-1197`, so consumers that inspect this error code see a different value.

> - Fix duplicate error code: change mesheryctl ErrConnectionNotFoundCode from "mesheryctl-1196" to "mesheryctl-1197" @PragalvaXFREZ (#17268)

### Fatal error for missing contexts in `mesheryctl system context view`

- Affects: `mesheryctl system context view` usage

Previously, the command logged that the context did not exist and returned nil, so callers could treat it as successful. It now returns `ErrContextNotExists` with code `mesheryctl-1196`.

> - Changed output status for system context @DharunMR (#17187)

### mesheryctl design commands now require exact source type matches

- Affects: `mesheryctl design import` or `mesheryctl design onboard` commands that specify a source type

Previously, a source type that was only a substring of a valid type could be accepted. Such partial values now fail validation, while matching remains case-insensitive.

Evidence: “- Refactored `import` and `onboard` commands to utilize new source type validation logic.” https://github.com/meshery/meshery/pull/17283

> - [mesheryctl] mesheryctl design onboard e2e @lekaf974 (#17283)
> - [mesheryctl] mesheryctl design onboard e2e @lekaf974 (#17283)

### mesheryctl component and relationship templates added; model template renamed

- Affects: mesheryctl workflows using component, relationship, or model template files (Inferred)

The component and relationship template files were previously absent. The renamed model template’s new filename is not specified.

> - template json for missing component and relationship @Jougan-0 (#13872)

### The `yml` alias removed from `mesheryctl exp relationship view` output formats

- Affects: the `--output-format yml` setting for `mesheryctl exp relationship view`

Previously, the command accepted `yml` alongside `yaml` and `json`; now `yml` fails validation with an invalid-argument error.

Evidence: “case "yaml", "yml":” https://github.com/meshery/meshery/pull/17233

> - [mesheryctl]  consolidate --output-format handling in relationships command @shri771 (#17233)

## Important fixes (1)

### `mesheryctl` config initialization no longer risks a nil-pointer crash

- Affects: `mesheryctl` config initialization

When `os.Stat` returned an error with invalid file information during config initialization, accessing `stat.Size()` could crash `mesheryctl`. It now reports that it cannot access the config file and returns; missing or empty config files still trigger default config creation.

> - Fix unsafe os.Stat handling during mesheryctl config initialization @SuryanshGarg04 (#17146)
> - Fix unsafe os.Stat handling during mesheryctl config initialization @SuryanshGarg04 (#17146)
> - Fix unsafe os.Stat handling during mesheryctl config initialization @SuryanshGarg04 (#17146)

## Enhancements (3)

- Save `mesheryctl filter view` output as JSON or YAML (To use: Use the optional `--save` flag or its `-s` shorthand with `mesheryctl filter view`.)
- Save JSON or YAML output from relationship views (To use: `--save` flag (`-s` shorthand))
- Kubernetes Guestbook application added to the Meshery Catalog

## Dependency updates (2)

2 more, none mentioning security

- `- Bump jsonpath from 1.1.1 to 1.2.0 in /install/docker-extension/ui @[dependabot[bot]](https://github.com/apps/dependabot) (#17287)`
- `- chore: upgrade to meshery/schemas v0.8.124 @jamieplu (#17337)`

## Other changes (46)

- Migration of docs.meshery.io from Jekyll to Hugo begins
- Design onboarding E2E tests and nginx fixture resource settings
- End-to-end tests for `mesheryctl exp workspace create` and `mesheryctl exp workspace list`
- E2E test expectation for the `auth.json` provider changed to Layer5
- System-check and performance BATS expectations updated
- Meshery organization handling switches to the schemas `v1beta1` model
- UI end-to-end test login flow updated for token-based authentication
- UI build-and-server workflow stops passing remote-provider test credentials as environment variables
- Token-based authentication for UI end-to-end tests
- End-to-end tests added for `mesheryctl exp workspace create` and `mesheryctl exp workspace list`
- mesheryctl auth.json test expectation changed to `Layer5`
- mesheryctl E2E CI workflow adds TAP-to-Allure conversion
- Custom coding-agent configurations gain the `memory` tool
- mesheryctl E2E CI workflow supplies `GITHUB_TOKEN` from `secrets.GH_ACCESS_TOKEN` to the BATS setup action
- Updated `mesheryctl` BATS end-to-end test expectations
- `attendance_02_06_2026` documentation entry added
- `Ananyacm.md` community documentation file added
- `attendance_06_02_2026` attendance documentation entry added
- Abir Chakraborty introduction added to community documentation
- “About me” community documentation entry added
- Uwagbae Alexander Obayagbona biography added to the newcomers documentation
- Aary Kinge introduction added to community documentation
- Jackson Mwangi introduction added to community documentation
- Raunak's skills and location added to community documentation
- Meetings documentation adds Kavitha Karunakaran's biography
- Meshery Adapters and Meshery Architecture links corrected in adapter-design documentation
- Farhan Saleem's February 5, 2026 attendance added to the documentation
- Newcomers meeting documentation updated for the week of 02-05-2026
- Ajay Bansal's attendance information added to the documentation
- Jay Shaw's introduction added to meeting notes
- Damaris Poppe’s attendance information added to the documentation
- Meshery introduction from Newcomers' Meeting added to community documentation
- Attendance documentation entry for `Krishnav_Bajoria-attendace` added
- Jan 08 meeting notes added
- `mohammad_elshennawy.md` community documentation file added
- Jan. 29, 2026 community meeting attendance added to documentation
- Community documentation entry about introducing yourself added
- Community documentation file `Seo_Yohan.md` added
- Second-week attendance note added to the documentation
- Sathiya Narayanan introduction added to community documentation
- Jan 08 meeting notes added
- Raunak's introduction added to the meeting notes
- Kavitha Karunakaran biography added to meeting notes
- BATS end-to-end test expectations updated
- Newcomers meeting page for the week of 01-29-2026
- Grammar, capitalization, and formatting fixes in the Concepts documentation

---

Summaries are produced by AI, so they can be wrong, and they are provided without warranty.
