Fix update issue for route53.Record #4477
ci.yml
on: pull_request
detect-noop
9s
report-breaking-changes
49s
lint
49m 59s
check-diff
3m 56s
unit-tests
6m 39s
local-deploy
6m 52s
check-examples
1m 55s
Annotations
10 errors and 2 warnings
|
check-diff
could not import github.com/upbound/provider-aws/v2/apis/cluster/ec2/v1beta1 (import cycle: [github.com/upbound/provider-aws/v2/apis/cluster/efs/v1beta1 github.com/upbound/provider-aws/v2/apis/cluster/ec2/v1beta1 github.com/upbound/provider-aws/v2/apis/cluster/ec2/v1beta2])\n"}
|
|
check-diff
could not import github.com/upbound/provider-aws/v2/apis/cluster/ec2/v1beta1 (import cycle: [github.com/upbound/provider-aws/v2/apis/cluster/efs/v1beta1 github.com/upbound/provider-aws/v2/apis/cluster/ec2/v1beta1 github.com/upbound/provider-aws/v2/apis/cluster/ec2/v1beta2 github.com/upbound/provider-aws/v2/apis/cluster/vpclattice/v1beta1])\n"}
|
|
check-diff
could not import github.com/upbound/provider-aws/v2/apis/cluster/ec2/v1beta1 (import cycle: [github.com/upbound/provider-aws/v2/apis/cluster/efs/v1beta1 github.com/upbound/provider-aws/v2/apis/cluster/ec2/v1beta1 github.com/upbound/provider-aws/v2/apis/cluster/ec2/v1beta2 github.com/upbound/provider-aws/v2/apis/cluster/vpclattice/v1beta1 github.com/upbound/provider-aws/v2/apis/cluster/rds/v1beta1])\n"}
|
|
check-diff
could not import github.com/upbound/provider-aws/v2/apis/cluster/rds/v1beta1 (import cycle: [github.com/upbound/provider-aws/v2/apis/cluster/efs/v1beta1 github.com/upbound/provider-aws/v2/apis/cluster/ec2/v1beta1 github.com/upbound/provider-aws/v2/apis/cluster/ec2/v1beta2 github.com/upbound/provider-aws/v2/apis/cluster/vpclattice/v1beta1 github.com/upbound/provider-aws/v2/apis/cluster/rds/v1beta1 github.com/upbound/provider-aws/v2/apis/cluster/rds/v1beta3])\n"}
|
|
check-diff
could not import github.com/upbound/provider-aws/v2/apis/cluster/rds/v1beta1 (import cycle: [github.com/upbound/provider-aws/v2/apis/cluster/efs/v1beta1 github.com/upbound/provider-aws/v2/apis/cluster/ec2/v1beta1 github.com/upbound/provider-aws/v2/apis/cluster/ec2/v1beta2 github.com/upbound/provider-aws/v2/apis/cluster/vpclattice/v1beta1 github.com/upbound/provider-aws/v2/apis/cluster/rds/v1beta1 github.com/upbound/provider-aws/v2/apis/cluster/rds/v1beta2])\n"}
|
|
check-diff
could not import github.com/upbound/provider-aws/v2/apis/cluster/s3/v1beta2 (import cycle: [github.com/upbound/provider-aws/v2/apis/cluster/efs/v1beta1 github.com/upbound/provider-aws/v2/apis/cluster/ec2/v1beta1 github.com/upbound/provider-aws/v2/apis/cluster/elbv2/v1beta2 github.com/upbound/provider-aws/v2/apis/cluster/s3/v1beta2 github.com/upbound/provider-aws/v2/apis/cluster/s3control/v1beta2])\n"}
|
|
check-diff
could not import github.com/upbound/provider-aws/v2/apis/cluster/s3/v1beta2 (import cycle: [github.com/upbound/provider-aws/v2/apis/cluster/efs/v1beta1 github.com/upbound/provider-aws/v2/apis/cluster/ec2/v1beta1 github.com/upbound/provider-aws/v2/apis/cluster/elbv2/v1beta2 github.com/upbound/provider-aws/v2/apis/cluster/s3/v1beta2 github.com/upbound/provider-aws/v2/apis/cluster/s3control/v1beta2 github.com/upbound/provider-aws/v2/apis/cluster/lambda/v1beta2])\n"}
|
|
check-diff
could not import github.com/upbound/provider-aws/v2/apis/cluster/s3/v1beta2 (import cycle: [github.com/upbound/provider-aws/v2/apis/cluster/efs/v1beta1 github.com/upbound/provider-aws/v2/apis/cluster/ec2/v1beta1 github.com/upbound/provider-aws/v2/apis/cluster/elbv2/v1beta2 github.com/upbound/provider-aws/v2/apis/cluster/s3/v1beta2 github.com/upbound/provider-aws/v2/apis/cluster/s3control/v1beta2 github.com/upbound/provider-aws/v2/apis/cluster/lambda/v1beta2 github.com/upbound/provider-aws/v2/apis/cluster/lambda/v1beta1])\n"}
|
|
check-diff
could not import github.com/upbound/provider-aws/v2/apis/cluster/s3/v1beta2 (import cycle: [github.com/upbound/provider-aws/v2/apis/cluster/efs/v1beta1 github.com/upbound/provider-aws/v2/apis/cluster/ec2/v1beta1 github.com/upbound/provider-aws/v2/apis/cluster/elbv2/v1beta2 github.com/upbound/provider-aws/v2/apis/cluster/s3/v1beta2 github.com/upbound/provider-aws/v2/apis/cluster/s3control/v1beta2 github.com/upbound/provider-aws/v2/apis/cluster/lambda/v1beta2 github.com/upbound/provider-aws/v2/apis/cluster/lambda/v1beta1 github.com/upbound/provider-aws/v2/apis/cluster/s3/v1beta1])\n"}
|
|
check-diff
could not import github.com/upbound/provider-aws/v2/apis/cluster/s3control/v1beta2 (import cycle: [github.com/upbound/provider-aws/v2/apis/cluster/efs/v1beta1 github.com/upbound/provider-aws/v2/apis/cluster/ec2/v1beta1 github.com/upbound/provider-aws/v2/apis/cluster/elbv2/v1beta2 github.com/upbound/provider-aws/v2/apis/cluster/s3/v1beta2 github.com/upbound/provider-aws/v2/apis/cluster/s3control/v1beta2 github.com/upbound/provider-aws/v2/apis/cluster/lambda/v1beta2 github.com/upbound/provider-aws/v2/apis/cluster/lambda/v1beta1 github.com/upbound/provider-aws/v2/apis/cluster/s3/v1beta1 github.com/upbound/provider-aws/v2/apis/cluster/s3control/v1beta1])\n"}
|
|
detect-noop
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: fkirc/skip-duplicate-actions@f75f66ce1886f00957d99748a42c724f4330bdcf. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
report-breaking-changes
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: tj-actions/glob@v17.2.5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
skipped_resources
|
5.41 KB |
sha256:7881fe6b03ff830e1966e70ce23507dd2d4cbeabdf969190f6a527c1b2e7f05d
|
|