Skip to content

Publishing then checking the same schema no longer can cause a diff #259

Publishing then checking the same schema no longer can cause a diff

Publishing then checking the same schema no longer can cause a diff #259

Triggered via pull request August 11, 2026 22:09
Status Cancelled
Total duration 59s
Artifacts

release.yaml

on: pull_request
stable
stable
snapshot  /  snapshot
55s
snapshot / snapshot
stable-changeset-version  /  changeset-version
stable-changeset-version / changeset-version
publish-stable-docker-cli  /  Build CLI Docker Image
publish-stable-docker-cli / Build CLI Docker Image
snapshot-cli-version
0s
snapshot-cli-version
Matrix: build / build-and-dockerize
Waiting for pending jobs
publish-snapshot-docker-cli  /  Build CLI Docker Image
publish-snapshot-docker-cli / Build CLI Docker Image
build  /  publish multiarch manifest
build / publish multiarch manifest
trigger staging deployment
0s
trigger staging deployment
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 1 warning
snapshot / snapshot
Canceling since a higher priority waiting request for release-8361 exists
snapshot / snapshot
The operation was canceled.
release
Canceling since a higher priority waiting request for release-8361 exists
release
Canceling since a higher priority waiting request for release-8361 exists
snapshot / snapshot
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/github-script@v7, actions/setup-node@v4, styfle/cancel-workflow-action@0.12.1, the-guild-org/changesets-snapshot-action@232ff9af22cfd043528fe2e4c403afd090ba3ed3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/