[erikburt]

This dials up the allocation to GATI v2 migration from 40% to 70%.

Notes

• Bucketed rollout
• Buckets are determined by the calling repository's name ($GITHUB_REPOSITORY) (deterministic hash)
• If the repository's bucket falls below the allocation percentage, then it's opted in
• Opted in repos will be seamlessly migrated to use gati v2, and the v1 migration profiles
• Previous PRs: chore: setup-github-token gativ2 rollout - 20% allocation #1679, chore: setup-github-token gativ2 rollout - 40% allocation #1710

Rollback Instructions

• devex-cicd or prodsec needed (due to permissions)

1. git fetch --tags --force - ensure your tags are up to date
2. git tag -f setup-github-token/v1 setup-github-token/1.3.0 - retag it to the version with 0% allocation
   • 20% allocation: git tag -f setup-github-token/v1 setup-github-token/1.4.0
   • 40% allocation: git tag -f setup-github-token/v1 setup-github-token/1.4.1
3. git push origin --force setup-github-token/v1 - force push the retag

Repository opt-out

If a single repository experiencing issues:

• Repository can force GATI version 1 by: gati-version: v1 as input
• Or we can update the FORCE_V1_REPOSITORIES field, and add their repository (source)
  • Will require releasing a new version - ideally a patch version

[github-actions]

🦋 Changeset is good to go

Latest commit: 11a3bb5

We got this.

Not sure what this means? Click here to learn what changesets are.

[erikburt]

Tested on chainlink quickly to ensure things don't break. smartcontractkit/chainlink#24040

Looks good.