Skip to content

Comments

fix: package.json conflicts#391

Merged
jaieds merged 13 commits intostagingfrom
fix-conflicts
Feb 10, 2026
Merged

fix: package.json conflicts#391
jaieds merged 13 commits intostagingfrom
fix-conflicts

Conversation

@jaieds
Copy link
Contributor

@jaieds jaieds commented Feb 10, 2026

Description

Screenshots | Video with voice-over

Link to Figma (If applicable)

How has this been tested?

Checklist:

  • My code is tested
  • Screenshot added in PR
  • Figma design linked
  • My code follows accessibility standards
  • My code has proper inline documentation
  • I have resolved all lint issues
  • My templates are responsive
  • I've added conditional class names use cn()
  • I've followed theme color usage
  • I have used clear and relevant file paths

vrundakansara and others added 13 commits September 12, 2025 17:21
…s-1770453055841

Add Claude Code GitHub Workflow
Publish a new workflow for duplicating mirror image at brainstormforce/bsf-admin-ui
Update release trigger in .github/workflows/publish.yml and .github/workflows/publish-public-build.yml from types: [created] to types: [published] so the publish jobs run only when a release is published (not when a draft or created event occurs). This avoids premature or duplicate publish runs.
Replace the release: published trigger with push: branches: [master] in both publish workflows so publishing runs on pushes to the master branch instead of on GitHub release events. Files updated: .github/workflows/publish-public-build.yml and .github/workflows/publish.yml. No other job changes.
@jaieds jaieds requested a review from earth9890 February 10, 2026 06:12
@@ -1,12 +1,16 @@
{

Choose a reason for hiding this comment

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

What: The package name has been changed from '@bsf/force-ui' to '@brainstormforce/force-ui'. Ensure that this change is reflected in other dependent modules and components.

Why: Changing the package name can affect existing installations and usages of the library. It is crucial to ensure that all references across the codebase and any documentation are updated to prevent breakages.

How: Verify all instances where '@bsf/force-ui' is being used in your projects and update them to '@brainstormforce/force-ui'. Additionally, check for any dependencies that may require updates.

"registry": "https://npm.pkg.github.com",
"access": "restricted"
},
"exports": {

Choose a reason for hiding this comment

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

What: A new publishConfig section has been added with a registry and access level specified. Ensure that this configuration is necessary and correct.

Why: The publishConfig specifies how the package should be published to the GitHub Package Registry. Incorrect configurations may lead to publishing issues or security concerns with package access levels.

How: Confirm that the specified registry URL is correct and corresponds to your GitHub Packages setup. If access should be public rather than restricted, adjust the configuration accordingly.

@@ -41,7 +45,7 @@
},

Choose a reason for hiding this comment

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

What: The repository URL has been updated from a different repository to the correct one for this package.

Why: This ensures that anyone accessing the package will find the correct source code and can contribute or raise issues against the right repository. Keeping repository links accurate is important for maintainability.

How: Double-check that the new URL 'git+https://github.com/brainstormforce/force-ui.git' is accessible and reflects the intended destination for users who might wish to contribute.

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

Great job! ✅ The PR looks solid with no security or performance issues.

Please make sure to resolve any remaining comments if any. Approved 👍

@claude
Copy link

claude bot commented Feb 10, 2026

Code review

No issues found. Checked for bugs and CLAUDE.md compliance.

@jaieds jaieds merged commit f8dc7f9 into staging Feb 10, 2026
6 checks passed
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.

5 participants