The RegistrationAuthorityCode value for the Canadian province of Newfoundland and Labrador was missing an underscore, which made it read CA_NEWFOUNDLANDAND_LABRADOR. It has been corrected to CA_NEWFOUNDLAND_AND_LABRADOR, bringing it in line with every other multi-word value in the enum, such as CA_NEW_BRUNSWICK and CA_PRINCE_EDWARD_ISLAND.
This is a breaking change if you send or match the old value. The affected field is registrationAuthorityCode on:
EntityDetailsInput, used when creating an entityUpdateEntityDetailsInput, used when updating an entityCaseEntity, returned when reading an entity
If you send the old value, the request is rejected because it is no longer part of the enum:
# No longer valid
mutation {
updateEntity(input: {
caseId: "1234"
entityId: "5678"
entity: {
registeredCountry: "CA"
registrationAuthorityCode: CA_NEWFOUNDLANDAND_LABRADOR
}
}) { __typename }
}
# Use this instead
mutation {
updateEntity(input: {
caseId: "1234"
entityId: "5678"
entity: {
registeredCountry: "CA"
registrationAuthorityCode: CA_NEWFOUNDLAND_AND_LABRADOR
}
}) { __typename }
}
If you read registrationAuthorityCode and compare it against a stored string or a local enum, update that value too — entities registered in Newfoundland and Labrador now return CA_NEWFOUNDLAND_AND_LABRADOR.
No other registration authority values have changed, and no data migration is needed: entities already registered in Newfoundland and Labrador keep their registration authority and simply report it under the corrected name.