Implement Slice Twelve 0.3.0 release and GitHub npm publishing - #15
Merged
Merged
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
This branch was successfully 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
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.
Release 0.3.0 combines structured PERSON support (#12), faster finding selection (#13), and text-offset/record optimizations (#14). This aligns all package versions and lockfiles, adds public release notes, and updates release-status documentation.
npm publishing moves to GitHub trusted publishing (OIDC), resolving the interactive 2FA failure in the previous CI releases. The Node workflow now transfers the generated loader/types as well as native binaries, verifies the assembled package with its platform dependency, and offers a safe dry-run mode. WASM runs its installed browser suite before publishing. All release workflows reject mismatched package versions and tags.
Validation: Rust formatting, Clippy, and 84 tests passed; installed Python, Node, and browser/WASM suites passed locally; actionlint and Mintlify validation/link checks passed; all four matching release tags were accepted and mismatched tags rejected. All GitHub PR checks and publishing dry runs passed, including five native builds, assembled Node package tests, and browser WASM tests. The Publish steps were confirmed skipped in both dry runs.
npm trusted publishers are configured for @datafog/node, its five native packages, and @datafog/wasm using DataFog/datafog-core, environment npm, and publish-node.yml / publish-wasm.yml. All seven npm settings changes were confirmed successful. Actual publication will run from the release tags on GitHub Actions.