chore(deps): update dependency @useoptic/optic to v1

[backstage-goalie]

This PR contains the following updates:

Package	Type	Update	Change
@useoptic/optic	devDependencies	major	^0.55.0 -> ^1.0.0

---

Release Notes

opticdev/optic (@​useoptic/optic)

v1.0.0

Compare Source

Changelog

• Removed deprecated capture commands, this included oas subcommands, optic update, optic new, optic verify and optic setup-tls - use optic capture instead
• Removed connections to optic cloud servers (uploading saved data - e.g. OpenAPI specs, hosted rulesets / rules, loading saved data, etc)
  • optic run is no longer supported - use optic diff-all (example: diff against base tags optic diff-all --compare-from main)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[awanlin]

Hi @BethGriggs, took a look and best I can tell this isn't being used in code anywhere? Could we just delete this dev dependency?

[awanlin]

Hi @jkilzi, can we remove this dev dependency, it does not look to be used best I can tell?

[jkilzi]

Hi @jkilzi, can we remove this dev dependency, it does not look to be used best I can tell?

Unfortunately no. It is declared as a peerDependency of @backstage/repo-tools, which we use to generate a client from an openapi.yaml spec file.

[jkilzi]

@awanlin, BTW, I'm not sure it is going to work the same way it did if you bump it from v0.55.0 to v1.0.0

[awanlin]

Thanks for the follow up @jkilzi, should we close this PR then? That will pin it at this version range until a point where we upgrade this manually.

[backstage-goalie]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 1.x releases. But if you manually upgrade to 1.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.