Repository navigation
Version Packages - #709
Open
jumski wants to merge 1 commit into
Open
Version Packages#709jumski wants to merge 1 commit into
jumski wants to merge 1 commit into
Conversation
|
View your CI Pipeline Execution ↗ for commit 2a709fd
💡 Verify your cache is correct by running tasks in a sandbox. Read docs ↗ ☁️ Nx Cloud last updated this comment at |
This branch has not been deployed
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.
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
pgflow@0.17.3
Patch Changes
@pgflow/client@0.17.3
Patch Changes
@pgflow/core@0.17.3
Patch Changes
f67145b: Preserve handler outcomes when worker logging or task settlement fails, and classify interruption from the worker shutdown signal instead of the exception name. Successful handlers get one completion attempt even during shutdown; settlement errors reach the worker error boundary without replay or conversion into handler failures.
Preserve falsy task outputs (
0,false, and"") and store null or undefined outputs as JSON null instead of SQL NULL.@pgflow/edge-worker@0.17.3
Patch Changes
f67145b: Preserve handler outcomes when worker logging or task settlement fails, and classify interruption from the worker shutdown signal instead of the exception name. Successful handlers get one completion attempt even during shutdown; settlement errors reach the worker error boundary without replay or conversion into handler failures.
Preserve falsy task outputs (
0,false, and"") and store null or undefined outputs as JSON null instead of SQL NULL.Updated dependencies [f67145b]
@pgflow/dsl@0.17.3