chore(release): version packages#3814
Closed
github-actions[bot] wants to merge 1 commit into
Closed
Conversation
Collaborator
|
Stale version PR — main and npm are both in sync (2.129.2) with zero unconsumed changesets, so this has nothing to release (orphaned by the version-PR race). The changesets bot will open a fresh one when the next changeset lands. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
nexus-agents@2.129.2
Patch Changes
12608ffThanks @williamzujkowski! - fix(mcp): break theci-health-check-tool↔ci-health-logcircular import (#3756). Importing the MCP tools barrel (or either ci-health module) under tsx ESM evaluation threwReferenceError: Cannot access 'CiHealthStatusSchema' before initialization— the tool defined the shared schema/types AND imported the log's appenders, while the log used the schema at module-eval time, so the cyclic init order left it in the TDZ. ExtractedCiHealthStatusSchema/CiHealthStatus/CiHealthSignalinto a leafci-health-types.ts(imports only zod) that both modules depend on; the tool re-exports them for API compatibility. A structural guard test keeps the cycle edge from returning.