build: add publishConfig for public access#8
Merged
brian-smith-tcril merged 1 commit intoopenedx:mainfrom Feb 13, 2026
Merged
Conversation
Scoped packages default to private on npm. Add publishConfig.access so semantic-release can publish publicly. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
arbrandes
approved these changes
Feb 13, 2026
1 task
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
2 participants
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
publishConfig.access: "public"topackage.jsonso semantic-release can publish the scoped package publiclyScoped packages default to private on npm. Without this, semantic-release will hit a 402 error when attempting to publish.
Test plan
Log
frontend-dev-utils Add Public Publish Config - Work Log
Date: 2026-02-13
Objective
Ensure
@openedx/frontend-dev-utilspublishes as a public package on npm, both for manual and automated releases.Problem
Scoped packages (
@openedx/...) default to private on npm. Publishing without--access publicfails with:The initial version was published manually using
npm publish --tag prerelease --access public, but semantic-release won't know to pass that flag.Fix
Add
publishConfig.access: "public"topackage.jsonso both manual and semantic-release publishes work without needing the--access publicflag.Status
add-public-publish-config0f9a646—build: add publishConfig for public access🤖 Generated with Claude Code