chore(deps-dev): bump @meshery/schemas from 1.2.22 to 1.3.0

[dependabot]

Bumps @meshery/schemas from 1.2.22 to 1.3.0.

Release notes

Sourced from @​meshery/schemas's releases.

v1.3.0 — Performance Profile runtime test-config schemas

Adds Meshery-native runtime test-config schemas to the v1beta3/performance_profile construct so that downstream consumers (notably meshery/meshery) can drop the deprecated github.com/layer5io/service-mesh-performance/spec dependency entirely.

New schemas

• PerformanceTestConfig — runtime configuration for a single performance (load) test run (smpVersion, id, name, labels, clients, duration). Direct replacement for SMP PerformanceTestConfig.
• PerformanceTestClient — a single load-generation client within a PerformanceTestConfig (internal, loadGenerator, protocol, connections, rps, headers, cookies, body, contentType, endpointUrls, sslCertificate, additionalOptions). Direct replacement for SMP PerformanceTestConfig_Client.

Both types live under the existing performance_profile construct and are generated into the performance_profile Go package and the @meshery/schemas TypeScript distribution.

Design notes

• Property names follow the canonical camelCase wire contract.
• protocol is a free-form string (e.g. `http`, `tcp`, `udp`, `grpc`) rather than the constraining SMP protocol enum.
• Service-mesh identity carried alongside a test is now expressed as a Meshery Registry model name string rather than the fixed SMP `ServiceMesh_Type` enum — more flexible and not limited to service-mesh technologies.
• The existing `PerformanceProfile` (saved profile) schema is unchanged.

Companion PR: meshery/schemas#907.

Meshery Schemas v1.2.23

What's New

🔤 General

• chore: fix blocked dependabot npm security update @​copilot-swe-agent (#762)
• feat(system): document Meshery-only operational endpoints under /api/system/ @​leecalcote (#897)

👨🏽‍💻 Contributors

Thank you to our contributors for making this release possible: @​PragalvaXFREZ, @​copilot-swe-agent, @​leecalcote and @​pontusringblom

Changelog

Sourced from @​meshery/schemas's changelog.

v1.3.0 — Performance Profile runtime test-config schemas

Adds Meshery-native replacements for the deprecated github.com/layer5io/service-mesh-performance/spec types, so downstream consumers (notably meshery/meshery) can drop the SMP dependency entirely.

• PerformanceTestConfig — runtime configuration for a single performance (load) test run (smpVersion, id, name, labels, clients, duration). Direct replacement for SMP PerformanceTestConfig.
• PerformanceTestClient — a single load-generation client within a PerformanceTestConfig (internal, loadGenerator, protocol, connections, rps, headers, cookies, body, contentType, endpointUrls, sslCertificate, additionalOptions). Direct replacement for SMP PerformanceTestConfig_Client.

Both are defined under the existing v1beta3/performance_profile construct and generated into the performance_profile Go package and @meshery/schemas TypeScript distribution. Property names follow the canonical camelCase wire contract. The protocol field is a free-form string (e.g. http, tcp, udp, grpc) rather than the constraining SMP enum, and the service-mesh identity carried alongside a test is now a Meshery Registry model name string rather than the fixed SMP ServiceMesh_Type enum.

v1.1.0 — Phase 1 of the identifier-naming migration

Marks the completion of Phase 1 of the identifier-naming migration. Phase 1 is governance- and tooling-only: no wire-format changes are made in this release. The validator, advisory baseline, CI jobs, and docs have been realigned so that every subsequent per-resource rollout (Phase 2 non-breaking alignment, Phase 3 versioned migrations) has a single source of truth and a single rule surface to reason against.

The canonical-casing contract

In one sentence: wire is camelCase everywhere; DB is snake_case; Go fields follow Go idiom; the ORM layer is the sole translation boundary. Concretely, every JSON tag and every OpenAPI schema property — DB-backed or not — is camelCase; the snake_case DB column name lives only in x-oapi-codegen-extra-tags.db. URL path and query parameters are camelCase with an Id suffix ({orgId}, ?userId=...). The earlier conditional rule "JSON tag matches db: tag when the field is DB-backed" has been retired. Legacy resources retain their published wire casing until their next API-version bump; new API versions adopt the canonical contract uniformly.

See https://github.com/meshery/schemas/blob/v1.3.0/docs/identifier-naming-migration.md §1 for the full contract table and https://github.com/meshery/schemas/blob/v1.3.0/AGENTS.md § Casing rules at a glance for the per-layer rules enforced by the validator.

Phase 1 landings

• 1.A — AGENTS.md identifier-naming amendment (#788): Replaced the "DB-backed = snake on the wire" rule with the canonical camelCase-on-wire contract; converted page_size / total_count from a perpetual exception to a deprecation list; added § Identifier-naming migration pointing at the executable plan.
• 1.B — Rule 6 inversion / Rule 32 retirement (#791): Rewrote the schema-property casing rule to require camelCase unconditionally; removed the DB-backing exception path and retired the superseded rule that enforced snake-on-DB-backed tags.
• 1.C — "Partial casing migrations forbidden" rule (Rule 45) (#792): New rule walks every components/schemas/<Entity> and fails any struct that mixes JSON-tag conventions across its properties (camel + snake + ID). Catches the OrgID/workspace_id/user_id drift class on a single struct.
• 1.D — "Sibling-endpoint parameter parity" rule (Rule 46) (#793): New rule flags GET /api/<entity> siblings that omit orgIdQuery when their peers declare it — the class of drift that produced the workspaces-400 incident.
• 1.E — Query-parameter casing (Rule 4 extension) (#794): Extended the path-param casing rule to query parameters so user_id, organizationId, and any orgID that

... (truncated)

Commits

• c896b3f fix(performance_profile): align required-field tags and lockfile version
• 7f513e1 feat(performance_profile): add PerformanceTestConfig and PerformanceTestClien...
• b703cf1 Generate build artifacts from schemas
• c4e2462 Update published schema versions
• e6c4ae6 Merge pull request #762 from meshery/copilot/fix-dependabot-configuration-fai...
• 7e1295a Generate build artifacts from schemas
• 5843b12 Merge pull request #897 from meshery/claude/add-reset-endpoint-docs-Zscj8
• a7b7375 Merge branch 'master' into claude/add-reset-endpoint-docs-Zscj8
• f487eae update description
• a1443a7 marked name and type as required in schemas/constructs/v1beta1/system/api.yml
• Additional commits viewable 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)