chore(migrate-sdk): version packages - #16
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
@migrate-sdk/commercetools@0.9.0
Minor Changes
612c3b2: Use destination bulk APIs without giving up per-item migration safety.
migrate-sdknow supportsprocessBatchas an opt-in alternative toprocess.One callback can coordinate all eligible items from a source cursor window,
use a bulk API or inspect sibling items, and return one deferred result (a
settlement) per item. The SDK still saves tracking, success or failure, retry
eligibility, and rollback state independently for every source item. Failed
items can be retried without repeating successful siblings. Journaling and
rollback retain their existing per-item behavior.
Destination helpers can now declare typed journal extensions for durable data
that does not fit the SDK's standard change or diagnostic entries. Each helper
can read, replace, or remove its own named value without overwriting
compensation evidence or another helper's extension. Extensions work in both
processandprocessBatch; they are not batch or attempt records.@migrate-sdk/commercetoolsadds Product Draft imports through thecommercetools Import API. It splits large source windows by the Import API's
count and payload limits, submits requests with bounded concurrency, polls each
Import Operation, correlates it by product key, and journals the operation data
needed to recover interrupted or partially successful imports in a typed,
helper-owned journal extension. The package
includes an inline example and opt-in live tests against a real commercetools
Project.
@migrate-sdk/workflow-sdkaddsdisableWorkflowStepRetriesfor cursor-worksteps. Existing Workflow SDK applications should apply it to their cursor and
orphan-reconciliation page steps so an automatically retried step cannot move
on from an already committed cursor using stale workflow state. Lifecycle and
finalization steps should keep their normal retry policy. This reduces unsafe
automatic replay but does not provide exactly-once delivery.
No public API was removed or renamed. Existing migration definitions that use
processcontinue to work unchanged, and existing journals remain readable. Amigration definition chooses either
processorprocessBatch, never both.migrate-sdk@0.9.0
Minor Changes
612c3b2: Use destination bulk APIs without giving up per-item migration safety.
migrate-sdknow supportsprocessBatchas an opt-in alternative toprocess.One callback can coordinate all eligible items from a source cursor window,
use a bulk API or inspect sibling items, and return one deferred result (a
settlement) per item. The SDK still saves tracking, success or failure, retry
eligibility, and rollback state independently for every source item. Failed
items can be retried without repeating successful siblings. Journaling and
rollback retain their existing per-item behavior.
Destination helpers can now declare typed journal extensions for durable data
that does not fit the SDK's standard change or diagnostic entries. Each helper
can read, replace, or remove its own named value without overwriting
compensation evidence or another helper's extension. Extensions work in both
processandprocessBatch; they are not batch or attempt records.@migrate-sdk/commercetoolsadds Product Draft imports through thecommercetools Import API. It splits large source windows by the Import API's
count and payload limits, submits requests with bounded concurrency, polls each
Import Operation, correlates it by product key, and journals the operation data
needed to recover interrupted or partially successful imports in a typed,
helper-owned journal extension. The package
includes an inline example and opt-in live tests against a real commercetools
Project.
@migrate-sdk/workflow-sdkaddsdisableWorkflowStepRetriesfor cursor-worksteps. Existing Workflow SDK applications should apply it to their cursor and
orphan-reconciliation page steps so an automatically retried step cannot move
on from an already committed cursor using stale workflow state. Lifecycle and
finalization steps should keep their normal retry policy. This reduces unsafe
automatic replay but does not provide exactly-once delivery.
No public API was removed or renamed. Existing migration definitions that use
processcontinue to work unchanged, and existing journals remain readable. Amigration definition chooses either
processorprocessBatch, never both.@migrate-sdk/workflow-sdk@0.9.0
Minor Changes
612c3b2: Use destination bulk APIs without giving up per-item migration safety.
migrate-sdknow supportsprocessBatchas an opt-in alternative toprocess.One callback can coordinate all eligible items from a source cursor window,
use a bulk API or inspect sibling items, and return one deferred result (a
settlement) per item. The SDK still saves tracking, success or failure, retry
eligibility, and rollback state independently for every source item. Failed
items can be retried without repeating successful siblings. Journaling and
rollback retain their existing per-item behavior.
Destination helpers can now declare typed journal extensions for durable data
that does not fit the SDK's standard change or diagnostic entries. Each helper
can read, replace, or remove its own named value without overwriting
compensation evidence or another helper's extension. Extensions work in both
processandprocessBatch; they are not batch or attempt records.@migrate-sdk/commercetoolsadds Product Draft imports through thecommercetools Import API. It splits large source windows by the Import API's
count and payload limits, submits requests with bounded concurrency, polls each
Import Operation, correlates it by product key, and journals the operation data
needed to recover interrupted or partially successful imports in a typed,
helper-owned journal extension. The package
includes an inline example and opt-in live tests against a real commercetools
Project.
@migrate-sdk/workflow-sdkaddsdisableWorkflowStepRetriesfor cursor-worksteps. Existing Workflow SDK applications should apply it to their cursor and
orphan-reconciliation page steps so an automatically retried step cannot move
on from an already committed cursor using stale workflow state. Lifecycle and
finalization steps should keep their normal retry policy. This reduces unsafe
automatic replay but does not provide exactly-once delivery.
No public API was removed or renamed. Existing migration definitions that use
processcontinue to work unchanged, and existing journals remain readable. Amigration definition chooses either
processorprocessBatch, never both.@migrate-sdk/tui@0.9.0
Patch Changes