V3#280
Merged
Merged
Conversation
🦋 Changeset detectedLatest commit: 064f7a2 The changes in this PR will be included in the next version bump. This PR includes changesets to release 7 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
removes some incorrect info - features that were going to be added, but don't exist yet :(
…events Implemented the events using decl merging pattern, so that event types can be colocated with their respective packages.
these defeat the point of using neverthrow.
ran npm audit fix
The IPC transport is the only 'required' transport - necessary for the persistent mode to work. It implements the same interface as the future transports.
Allows for checking for running instances based on the existance of a PID file.
Updates 'content' and 'monitor' command to send commands to running controller if one is found, otherwise instantiate ephemeral controller. Updates 'start' command to create persistent controller. Updates 'stop' command to stop persistent controller (in addition to killing pm2). Adds 'status' command to query running controller.
Seems like node will block as long as there's an open server, so the IPC server takes care of this.
bug caused by using a relative path import instead of module path for logmanager
Phase 3 added a statusSnapshot notification that broadcasts on every state patch. Update the three patch-broadcast tests to acknowledge two messages per patch event, and add a positive assertion that statusSnapshot is emitted.
The summarize-on-plugin path is now authoritative. Delete the old StatusRegistry, the three *-status-section.ts files, the StatusHostContext, and all contributeStatusSection() call sites. DashboardContributionManager no longer needs a StatusRegistry. Breaking: plugins using ctx.statusRegistry.contributeStatusSection must migrate to a summarize?(state) => Section | null property on the plugin factory.
claytercek
force-pushed
the
v3
branch
3 times, most recently
from
3393820 to
31a7e21
Compare
Remove the deleted scaffold package upload from the release workflow, align package engine metadata with the Node 23 release baseline, and clean up stale transform documentation/import references. Also normalize release-adjacent JSON and whitespace so the branch passes build, docs, lint, changeset, and packaging checks.
claytercek
force-pushed
the
v3
branch
4 times, most recently
from
9529700 to
e6c2e02
Compare
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
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.
No description provided.