Forward-merge release/0.2 into main#115
Merged
Merged
Conversation
#### Overview Fix the OpenClaw npm publish failure by declaring repository metadata that matches GitHub Actions provenance for the `nemo-flow-openclaw` package. - [x] I confirm this contribution is my own work, or I have the right to submit it under this project's license. - [x] I searched existing issues and open pull requests, and this does not duplicate existing work. #### Details - Added `repository` metadata to `integrations/openclaw/package.json` with the NVIDIA/NeMo-Flow source repository and OpenClaw workspace directory. - Extended the OpenClaw pack payload check to require the provenance-sensitive repository URL and package directory before publish. - Validated with `npm run pack:check --workspace=nemo-flow-openclaw`, `uv run pre-commit run --files integrations/openclaw/package.json integrations/openclaw/scripts/check-pack-payload.mjs`, and `just --set ci true test-openclaw`. - `uv run pre-commit run --all-files` completed all remaining hooks except the unrelated local `ty` unresolved imports for `deepagents.create_deep_agent` and `deepagents.backends` in `python/tests/integrations/deepagents/test_deepagents_integration.py`. #### Where should the reviewer start? Start with `integrations/openclaw/package.json`, then check the new guard in `integrations/openclaw/scripts/check-pack-payload.mjs`. #### Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to) - Relates to: https://github.com/NVIDIA/NeMo-Flow/actions/runs/25895241662/job/76109056996 ## Summary by CodeRabbit * **Chores** * Updated package metadata to properly reference the repository location. * Strengthened build validation to ensure package configuration consistency. [](https://app.coderabbit.ai/change-stack/NVIDIA/NeMo-Flow/pull/114) Authors: - Will Killian (https://github.com/willkill07) Approvers: - https://github.com/Salonijain27 URL: #114
Author
|
FAILURE - Unable to forward-merge due to an error, manual merge is necessary. Do not use the IMPORTANT: When merging this PR, do not use the auto-merger (i.e. the |
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.
Forward-merge triggered by push to release/0.2 that creates a PR to keep main up-to-date. If this PR is unable to be immediately merged due to conflicts, it will remain open for the team to manually merge. See forward-merger docs for more info.