Skip to content

Enable npm provenance on publish and add CODEOWNERS. - #303

Merged
chiragjn merged 1 commit into
mainfrom
chore/npm-provenance-and-codeowners
Aug 17, 2026
Merged

chiragjn merged 1 commit into
mainfrom
chore/npm-provenance-and-codeowners

Conversation

@chiragjn

@chiragjn chiragjn commented Aug 17, 2026 •

Copy link
Copy Markdown
Member

The repo is public, so publish can attest source repo and commit. Path owners split UI packages from the rest of the tree.


Note

Medium Risk
Provenance changes affect the release publish path; a misconfiguration could break npm publishes until fixed. CODEOWNERS only affects review policy, not runtime behavior.

Overview
Turns on npm provenance for public package publishes now that the repo is public, so npmjs.com can attest source repo and commit alongside existing OIDC trusted publishing.

publishConfig.provenance flips from false to true on @truefoundry/trueforge-core, @truefoundry/trueforge, @truefoundry/trueforge-sdk, and @truefoundry/trueforge-ui, plus the Fern SDK generator config. The Release publish job sets NPM_CONFIG_PROVENANCE: "true" (replacing a TODO that deferred provenance until the repo was public). RELEASING.md documents the provenance behavior.

Adds .github/CODEOWNERS: default reviewers for *, with separate owners for /packages/trueforge-ui/ and /packages/frontend/. Comments note enabling “Require review from Code Owners” on the default branch.

Reviewed by Cursor Bugbot for commit b5eb8d8. Bugbot is set up for automated code reviews on this repo. Configure here.

The repo is public, so publish can attest source repo and commit. Path owners split UI packages from the rest of the tree.

Co-authored-by: Cursor <cursoragent@cursor.com>
@changeset-bot

changeset-bot Bot commented Aug 17, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: b5eb8d8

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@chiragjn
chiragjn merged commit f04cd5a into main Aug 17, 2026
10 checks passed
@chiragjn
chiragjn deleted the chore/npm-provenance-and-codeowners branch August 17, 2026 10:52

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit b5eb8d8. Configure here.

"publishConfig": {
"access": "public",
"provenance": false
"provenance": true

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hand-edited generated SDK package

Low Severity

packages/trueforge-sdk is regenerated in CI from .github/fern/generators.yml, so this hand-edit of publishConfig.provenance violates the no-manual-SDK-edits rule. The matching generators.yml update is the durable source of truth; the Generate SDK workflow is what should rewrite the SDK package.json.

Fix in Cursor Fix in Web

Triggered by project rule: TrueForge review rules

Reviewed by Cursor Bugbot for commit b5eb8d8. Configure here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant