chore: prepare durable-isolates release - #9
Merged
Conversation
…d package LICENSE files)
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
1 participant
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.
What
Prepares the first release of
durable-isolates(0.0.0 → 0.1.0) while holding backdurable-workflows, which is not ready yet..changeset/config.json— adddurable-workflowstoignore:changeset version/publishskip it entirely. Its two pending changesets (engine-runtime,workflow-authoring-surface) stay on disk and are held until it is removed from the ignore list.packages/*/LICENSE— copy the root MIT LICENSE into both packages so the published tarballs actually contain theLICENSEentry already listed in theirfilesarrays.Verified
Dry-ran
changeset versionlocally with the ignore in place: onlydurable-isolatesis bumped to 0.1.0 (consuming its four changesets);durable-workflowsstays at 0.0.0 with its changesets untouched.After merge
The release action will open a "Version Packages" PR bumping only
durable-isolates; merging that publishesdurable-isolates@0.1.0to npm via OIDC trusted publishing. Ensure the Trusted Publisher fordurable-isolatesis configured on npmjs.com (reposchplitt/durable-workflows, workflowrelease.yml) — the pipeline has no token fallback.