what stackpulse tracks
Effect releases from GitHub
StackPulse watches Effect release notes and keeps the original source link close to every summary.
A fully-fledged functional effect system for TypeScript StackPulse turns upstream changelogs into scannable summaries with risky changes, deprecations, migration notes, and source links.
what stackpulse tracks
StackPulse watches Effect release notes and keeps the original source link close to every summary.
upgrade risk
Risky changes are separated from normal feature notes so you can scan upgrade impact before changing production dependencies.
migration notes
Migration steps and recommended actions are only shown when the upstream release notes support them.
This release focuses on bug fixes and improvements, including terminating multipart file streams, fixing `Duration`'s hash implementation, and enhancing `Migrator.fromFileSystem` for Windows paths.
Developers using `Migrator.fromFileSystem` on Windows or working with `Duration` hashing are affected.
Update dependencies and ensure `Path` layer is provided for `Migrator.fromFileSystem` on Windows.
This release primarily updates dependencies to align with the latest changes in the Effect ecosystem.
Users of @effect/sql-sqlite-react-native may need to update their dependencies to maintain compatibility.
Update dependencies to match the versions specified in this release.
This release focuses on bug fixes, performance improvements, and minor feature additions across various components, including resource management, SQL resolvers, and schema handling.
Developers using encrypted event logs and those relying on specific resource management or SQL resolver functionalities may be affected.
Upgrade both encrypted event log clients and servers together to ensure compatibility.
This release introduces several improvements and new features, including enhanced error handling for Config and RPC errors, bounded retries for HTTP rate limiting, and new schema parsing options. It also includes updates to the `Cron` module and changes to how schema issues are formatted and handled.
Developers using schema parsing, HTTP rate limiting, or the `Cron` module are affected by these changes.
Update code to handle schema issues explicitly and adapt to new `Cron` and HTTP rate limiting features.