Prepare @workit/core 0.2.0 ownership evidence release#50
Merged
Conversation
…d a more specific package description.
…nderTree(scope.status()), and work().do() fail-fast output.
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.
Summary
Prepare
@workit/core0.2.0 with the core ownership and evidence foundation, npm package discoverability improvements, README contract clarifications, activity result normalization, and OpenTelemetry package-version provenance.What changed
TaskFninvocation,renderTree(scope.status()), andwork().do()fail-fast output.work().do()buffering and the cooperativerun.hedge()cancellation contract for losing branches.0.2.0.Validation
npm run test:coverage- 24 files, 304 tests, 100% coveragenpm run verifynpm run bench:articles- 19/19 passednpm run test:evidence- 14/14 passednpm --workspace @workit/core run check:release- npm publish dry-run completednpm run check:no-network,npm run check:headers,npm run check:testsRelease notes
This is intended as the 0.2.0 release PR. Publishing should happen through the provenance workflow after CI is green and the signed release tag is created.