Migrate to Orb Tools 12.x

[MikeMcC399]

What would you like?

Migrate the Cypress CircleCI Orb from the currently used circleci/[email protected] release to use instead the latest Orb Tools 12.x release according to the circleci/orb-tools publication information.

circleci-orb/.circleci/config.yml

Line 4 in d2c7c66

orb-tools: circleci/[email protected]

circleci/[email protected] was released in May 2023. At the time of writing, the latest version is circleci/[email protected], released on Dec 16, 2024.

Why is this needed?

• As noted in Orb publishing does not work for contributor PRs #451 external contributors cannot effectively submit PRs and have them tested.

• According to Major: Orb Tools Version 12 CircleCI-Public/orb-tools-orb#181, the above restriction would be mitigated by a migration to circleci/orb-tools 12.x:

⭐ Dynamic Orb Injection Without Publication

The major goal of this PR is to decrease friction in orb contributions. Currently, in order to contribute to an orb, you must have access to a secured Restricted Context in CircleCI which contains a publishing token, so that a development version of the orb may be tested in the following dynamic workflow. This means, when a contributor opens a PR, they must wait for a maintainer to re-push the code for the proper permissions. This slows down the dev cycle a lot.

With this change, rather than publishing a new development version of the orb, we modify the dynamic config template to inject the orb source as an "internal" orb within the continue job. This has the same net-effect for testing your orbs but not (sic) longer requires access to secrets, eliminating blockers top (sic) the PR process.

[MikeMcC399]

Due to the restrictions noted for external contributors, it would be difficult for an external contributor to carry out this migration.