deps: bump typespec packages to 0.68.x / 1.12.x

[raelga]

AROSLSRE-949

What

Bump typespec packages from 0.67.x / 1.11.x to 0.68.x / 1.12.x in /api.

Packages updated:

• @azure-tools/typespec-autorest: 0.67.0 -> 0.68.0
• @azure-tools/typespec-azure-core: 0.67.1 -> 0.68.0
• @azure-tools/typespec-azure-resource-manager: 0.67.1 -> 0.68.0
• @azure-tools/typespec-azure-rulesets: 0.67.0 -> 0.68.0
• @azure-tools/typespec-client-generator-core: 0.67.4 -> 0.68.1
• @typespec/http: 1.11.0 -> 1.12.0
• @typespec/openapi: 1.11.0 -> 1.12.0
• @typespec/openapi3: 1.11.0 -> 1.12.0
• @typespec/rest: 0.81.0 -> 0.82.0
• @typespec/versioning: 0.81.0 -> 0.82.0
• @typespec/compiler: 1.11.0 -> 1.12.0

Why

Dependency update.

Testing

• npm install --package-lock-only passes

Closes #5301

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: raelga

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• api/OWNERS [raelga]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[Copilot]

Pull request overview

Updates /api TypeSpec-related dependencies to the 0.68.x / 1.12.x releases, along with the corresponding package-lock.json refresh.

Changes:

• Bump @azure-tools/typespec-* packages to 0.68.x and @typespec/* packages to 1.12.x / 0.82.x in api/package.json.
• Regenerate api/package-lock.json to reflect the updated dependency graph.

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated 1 comment.

File	Description
api/package.json	Updates TypeSpec dependency versions used for API compilation/emission.
api/package-lock.json	Updates resolved TypeSpec packages and transitive dependencies to match the new versions.

Files not reviewed (1)

• api/package-lock.json: Language not supported

Comments suppressed due to low confidence (2)

api/package.json:17

• The updated TypeSpec dependencies now require Node >=22 (see package-lock entries like @azure-tools/typespec-autorest), but this package still declares an engine of ">=20.12.0". This will mislead contributors and can break installs/runs on Node 20; please bump api/package.json "engines.node" to >=22 (and ensure CI/dev tooling uses Node 22).

  "engines": {
    "node": ">=20.12.0"
  },

api/package-lock.json:28

• package-lock.json still records the root package engine as Node ">=20.12.0", but the newly resolved TypeSpec packages in this lockfile declare engines of ">=22.0.0". Please update the root "packages[""].engines.node" (and keep it consistent with api/package.json) so consumers don’t try to install/run this lockfile on unsupported Node versions.

[openshift-ci]

@raelga: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/api-validation	e66cc49	link	true	/test api-validation

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.