Orb validation changes?

[excenter]

I have an existing orb
https://circleci.com/orbs/registry/orb/wealthforge/cypress
It’s a fork of the cypress orb, with some extra hooks for our build process.

It’s been working like a champ for months.
As of this morning, the orb is breaking builds with this error:

Awesome, great, let’s just validate the orb file using the cli

>_ circleci orb validate ./wf-cypress.yml 
Error: Error calling job: 'run'
Error calling command: 'install'
Type error for argument build: expected type: steps, actual value: "TEST_STRING" (type string)
Error calling job: 'install'
Error calling command: 'install'
Type error for argument build: expected type: steps, actual value: "TEST_STRING" (type string)

The orb is unchanged since we published months ago, and I cannot for the life of me figure out where TEST_STRING is coming from.

[excenter]

Update: Having changed nothing about the local version of the orb, it is now valid.

Waiting on some form of reason why it broke before I re-implement said orb.

[stella]

@excenter This is likely related to some backend changes on CircleCI’s platform at that time, that have since been undone. You should be able to ignore those validation errors you had encountered. Apologies for the experience!