Skip to content
timeline-check

refactor(BA-483): Revamp ContainerRegistryNode API #20109

Sign in to view logs

refactor(BA-483): Revamp ContainerRegistryNode API

refactor(BA-483): Revamp ContainerRegistryNode API #20109

Triggered via pull request February 3, 2025 05:21
@jopemachinejopemachine
synchronize #3424
topic/01-10-refactor_revamp_containerregistrynode_api
Status Skipped
Total duration 2s
Artifacts –

timeline-check.yml

on: pull_request
assign-pr-number  /  update-news-fragments
assign-pr-number / update-news-fragments
towncrier
0s
towncrier
Fit to window
Zoom out
Zoom in

Annotations

25 errors, 2 warnings, and 1 notice
New types must include a description with a version number in the format "Added in XX.XX.X." or "Added in XX.X.X.", Type 'CreateContainerRegistryNodeInput' was added: docs/manager/graphql-reference/schema.graphql#L2609
New types must include a description with a version number in the format "Added in XX.XX.X." or "Added in XX.X.X."
New types must include a description with a version number in the format "Added in XX.XX.X." or "Added in XX.X.X.", Type 'AllowedGroups' was added: docs/manager/graphql-reference/schema.graphql#L2641
New types must include a description with a version number in the format "Added in XX.XX.X." or "Added in XX.X.X."
New types must include a description with a version number in the format "Added in XX.XX.X." or "Added in XX.X.X.", Type 'ModifyContainerRegistryNodeInput' was added: docs/manager/graphql-reference/schema.graphql#L2654
New types must include a description with a version number in the format "Added in XX.XX.X." or "Added in XX.X.X."
Type 'AssociateContainerRegistryWithGroup' was removed: docs/manager/graphql-reference/schema.graphql#L1
Type 'AssociateContainerRegistryWithGroup' was removed
Type 'DisassociateContainerRegistryWithGroup' was removed: docs/manager/graphql-reference/schema.graphql#L1
Type 'DisassociateContainerRegistryWithGroup' was removed
Field 'associate_container_registry_with_group' was removed from object type 'Mutations': docs/manager/graphql-reference/schema.graphql#L1723
Removing a field is a breaking change. It is preferable to deprecate the field before removing it.
Field 'disassociate_container_registry_with_group' was removed from object type 'Mutations': docs/manager/graphql-reference/schema.graphql#L1723
Removing a field is a breaking change. It is preferable to deprecate the field before removing it.
Argument 'extra: JSONString' was removed from field 'Mutations.create_container_registry_node': docs/manager/graphql-reference/schema.graphql#L1852
Removing a field argument is a breaking change because it will cause existing queries that use this argument to error.
Argument 'is_global: Boolean' was removed from field 'Mutations.create_container_registry_node': docs/manager/graphql-reference/schema.graphql#L1852
Removing a field argument is a breaking change because it will cause existing queries that use this argument to error.
Argument 'password: String' was removed from field 'Mutations.create_container_registry_node': docs/manager/graphql-reference/schema.graphql#L1852
Removing a field argument is a breaking change because it will cause existing queries that use this argument to error.
Argument 'project: String' was removed from field 'Mutations.create_container_registry_node': docs/manager/graphql-reference/schema.graphql#L1852
Removing a field argument is a breaking change because it will cause existing queries that use this argument to error.
Argument 'registry_name: String!' was removed from field 'Mutations.create_container_registry_node': docs/manager/graphql-reference/schema.graphql#L1852
Removing a field argument is a breaking change because it will cause existing queries that use this argument to error.
Argument 'ssl_verify: Boolean' was removed from field 'Mutations.create_container_registry_node': docs/manager/graphql-reference/schema.graphql#L1852
Removing a field argument is a breaking change because it will cause existing queries that use this argument to error.
Argument 'type: ContainerRegistryTypeField!' was removed from field 'Mutations.create_container_registry_node': docs/manager/graphql-reference/schema.graphql#L1852
Removing a field argument is a breaking change because it will cause existing queries that use this argument to error.
Argument 'url: String!' was removed from field 'Mutations.create_container_registry_node': docs/manager/graphql-reference/schema.graphql#L1852
Removing a field argument is a breaking change because it will cause existing queries that use this argument to error.
Argument 'username: String' was removed from field 'Mutations.create_container_registry_node': docs/manager/graphql-reference/schema.graphql#L1852
Removing a field argument is a breaking change because it will cause existing queries that use this argument to error.
Argument 'extra: JSONString' was removed from field 'Mutations.modify_container_registry_node': docs/manager/graphql-reference/schema.graphql#L1858
Removing a field argument is a breaking change because it will cause existing queries that use this argument to error.
Argument 'is_global: Boolean' was removed from field 'Mutations.modify_container_registry_node': docs/manager/graphql-reference/schema.graphql#L1858
Removing a field argument is a breaking change because it will cause existing queries that use this argument to error.
Argument 'password: String' was removed from field 'Mutations.modify_container_registry_node': docs/manager/graphql-reference/schema.graphql#L1858
Removing a field argument is a breaking change because it will cause existing queries that use this argument to error.
Argument 'project: String' was removed from field 'Mutations.modify_container_registry_node': docs/manager/graphql-reference/schema.graphql#L1858
Removing a field argument is a breaking change because it will cause existing queries that use this argument to error.
Argument 'registry_name: String' was removed from field 'Mutations.modify_container_registry_node': docs/manager/graphql-reference/schema.graphql#L1858
Removing a field argument is a breaking change because it will cause existing queries that use this argument to error.
Argument 'ssl_verify: Boolean' was removed from field 'Mutations.modify_container_registry_node': docs/manager/graphql-reference/schema.graphql#L1858
Removing a field argument is a breaking change because it will cause existing queries that use this argument to error.
Argument 'type: ContainerRegistryTypeField' was removed from field 'Mutations.modify_container_registry_node': docs/manager/graphql-reference/schema.graphql#L1858
Removing a field argument is a breaking change because it will cause existing queries that use this argument to error.
Argument 'url: String' was removed from field 'Mutations.modify_container_registry_node': docs/manager/graphql-reference/schema.graphql#L1858
Removing a field argument is a breaking change because it will cause existing queries that use this argument to error.
Argument 'username: String' was removed from field 'Mutations.modify_container_registry_node': docs/manager/graphql-reference/schema.graphql#L1858
Removing a field argument is a breaking change because it will cause existing queries that use this argument to error.
Argument 'props: CreateContainerRegistryNodeInput!' added to field 'Mutations.create_container_registry_node': docs/manager/graphql-reference/schema.graphql#L1854
Adding a required argument to an existing field is a breaking change because it will cause existing uses of this field to error.
Argument 'props: ModifyContainerRegistryNodeInput!' added to field 'Mutations.modify_container_registry_node': docs/manager/graphql-reference/schema.graphql#L1863
Adding a required argument to an existing field is a breaking change because it will cause existing uses of this field to error.
Field 'allowed_groups' was added to object type 'ContainerRegistryNode': docs/manager/graphql-reference/schema.graphql#L1538
Field 'allowed_groups' was added to object type 'ContainerRegistryNode'