Repository navigation
chore: release 0.30.2 - #985
Merged
Merged
Conversation
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.
Release v0.30.2
Bump
@fastagent-sh/fastagentfrom 0.30.1 to 0.30.2.Fixed
login,channels setup,deploy's sign-in) still ran was asked with signal 0, which a zombie answers too: in a container whose PID 1 does not reap orphans, a step that had exited stayed a zombie, so--checknever saw it gone and a stop waited its full 5 s. Where/procbelongs to the process's own PID namespace (Linux), a process that has exited is now taken for stopped; where it does not (a sandbox that leaves a process the host's/proc), signal 0 alone decides, as before.Dependencies
effect,@effect/platform-nodeand@effect/platform-bun4.0.7 → 4.1.2 (chore(deps): bump the npm-dependencies group with 8 updates #937). The breaking changes of Effect 4.1 (effect/Crypto, Bun's default idle timeout,MaxBodySizeon buffered body reads) do not touch the APIs FastAgent uses, as it sets the Bun idle timeout and the Agent API's body limit itself.effectwas already^4.0.7, so an install of 0.30.1 already resolved 4.1.x; this release is built and tested with it.@smithy/signature-v4,@hono/node-server,fastify,knip, andvitest5.1.0.Verification
npm run lint,npm run typecheck,npm test(195 files, 2383 passed, 3 skipped),npm pack --dry-run --json.test/bun/*.ts) on Bun 1.4.0 and 1.4.4.After merge
Create and publish the GitHub Release
v0.30.2from the merged commit, with the sections above as its notes. The protected publish workflow verifies and publishes the package to npm via Trusted Publishing. This PR itself does not tag or publish.