[gati-app]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

setup-github-token@1.4.2

Patch Changes

• #1715
  5f07ff8
  Thanks @erikburt! - chore: gativ2 bucketed
  rollout - 70% allocation

[erikburt]

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