Conversation
Point semantic-release at this fork instead of upstream openedx: - .releaserc: replace upstream's stable/N.x branch set with a single `release` branch on the `latest` channel; `main` stays alpha. - release.yml: trigger on main and release, and release with the edX org's SEMANTIC_RELEASE_NPM_TOKEN plus the default GITHUB_TOKEN instead of OPENEDX_SEMANTIC_RELEASE_GITHUB_TOKEN. Drop id-token, since npm provenance is unavailable for restricted packages. - package.json: rename to @edx/frontend-app-notifications, publish restricted, and repoint repository/homepage/bugs at the fork. - README: fork identity, badges, and install/import instructions.
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.
Description
Include a description of your changes here, along with a link to any relevant Jira tickets and/or GitHub issues.
How Has This Been Tested?
Please describe in detail how you tested your changes.
Screenshots/sandbox (optional):
Include a link to the sandbox for design changes or screenshot for before and after. Remove this section if it's not applicable.
Merge Checklist
Post-merge Checklist