Skip to content

ci: use dedicated reactotron-npm-context for CircleCI#1602

Merged
joshuayoes merged 1 commit intomasterfrom
fix/circleci-context
Mar 30, 2026
Merged

ci: use dedicated reactotron-npm-context for CircleCI#1602
joshuayoes merged 1 commit intomasterfrom
fix/circleci-context

Conversation

@joshuayoes
Copy link
Copy Markdown
Contributor

@joshuayoes joshuayoes commented Mar 30, 2026

Please verify the following:

  • yarn build-and-test:local passes
  • I have added tests for any new features, if relevant
  • README.md (or relevant documentation) has been updated with your changes

Describe your PR

Switch from the shared infinitered-npm-package CircleCI context to a dedicated reactotron-npm-context, matching the pattern Ignite uses with ignite-npm-context.

The shared context has an expired GITHUB_TOKEN, which is blocking the release_tags job from pushing version commits and tags back to GitHub.

Changes

  • Replace all references to infinitered-npm-package with reactotron-npm-context in .circleci/config.yml

Notes

  • GITHUB_TOKEN is already configured in the new context
  • NPM_TOKEN still needs to be added before npm publishes will work — this can be done in CircleCI settings without another PR

The shared infinitered-npm-package context has an expired GITHUB_TOKEN,
blocking release_tags. Switch to a dedicated reactotron-npm-context
with a fresh token, matching the pattern used by Ignite.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@joshuayoes joshuayoes merged commit 8cebb4f into master Mar 30, 2026
7 checks passed
@joshuayoes joshuayoes deleted the fix/circleci-context branch March 30, 2026 21:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant