Update protobufjs lib

[jeanp413]

Description

Summary generated by Copilot

🤖 Generated by Copilot at 8353936

Updated ts-proto dependency to 1.153.0 in ide-service-api and usage-api components. This fixed a bug related to optional and required fields in TypeScript code generated from protobuf definitions.

Related Issue(s)

Fixes #

How to test

Documentation

Preview status

Gitpod was successfully deployed to your preview environment.

• 🏷️ Name - jp-key-jackal
• 🔗 URL - jp-key-jackal.preview.gitpod-dev.com/workspaces.
• 📚 Documentation - See our internal documentation for information on how to interact with your preview environment.
• 📦 Version - jp-key-jackal-gha.16056
• 🗒️ Logs - GCP Logs Explorer

Build Options

Build

• /werft with-werft
  Run the build with werft instead of GHA
• leeway-no-cache
• /werft no-test
  Run Leeway with --dont-test

Publish

• /werft publish-to-npm
• /werft publish-to-jb-marketplace

Installer

• analytics=segment
• with-dedicated-emulation
• workspace-feature-flags
  Add desired feature flags to the end of the line above, space separated

Preview Environment / Integration Tests

• /werft with-local-preview
  If enabled this will build install/preview
• /werft with-preview
• /werft with-large-vm
• /werft with-gce-vm
  If enabled this will create the environment on GCE infra
• with-integration-tests=all
  Valid options are all, workspace, webapp, ide, jetbrains, vscode, ssh. If enabled, with-preview and with-large-vm will be enabled.
• with-monitoring

[socket-security]

Updated dependencies detected. Learn more about Socket for GitHub ↗︎

Packages	Version	New capabilities	Transitives	Size	Publisher
ts-proto	1.125.0...1.156.7	None	+12/-15	106 MB	shaberman

[mustard-mh]

Any test points? Or we can enable integration test to do smoke tests? Good to see this PR that it will close a ton of issues.

It should contains changes on ws-manager-bridge and server? Or we did do it other PRs but I don't notice

[jeanp413]

Any test points?

Not sure, I asked internally

[AlexTugarev]

@jeanp413, I think it would be good to test workspace events in addition to a simple workspace start:

• have two tabs open on /workspaces
• in first you can start and later on close a workspace
• using the second tab, you should be able to monitor updates to the workspace by colors of the status indicator

[AlexTugarev]

/gh run recreate-vm

Comment triggered a workflow run

Started workflow run: 6010847186

• recreate_vm: true

[jeanp413]

/gh run recreate-vm

Comment triggered a workflow run

Started workflow run: 6014207047

• recreate_vm: true

[jeanp413]

@jeanp413, I think it would be good to test workspace events in addition to a simple workspace start:

• have two tabs open on /workspaces
• in first you can start and later on close a workspace
• using the second tab, you should be able to monitor updates to the workspace by colors of the status indicator

Works 👍

[jeanp413]

/unhold