Problems with custom components in Aurora

Hi!
I have two questions about new custom components in Aurora communities.
In documentation:
Create a pull request to pull these changes into the main branch of your plugin (<phase>-main, not main). The pull request must be merged
We merged our changes to stage-main branch, but this changes are not appearing in the community ( stage-main is the active branch in the community)The added ExampleComponent does not appear in the list of Custom Components, but when I change the branch to feat/cleanup-package-lock (merged branch), the changes become available.

When i switch active branch to the feat/cleanup-package-lock and try to add custom component i get error:
Loading script failed. (missing: https://aurora-customization-usw2.lithium.com/auroradynatrace/feat%2Fcleanup-package-lock/mf/_next/static/chunks/remoteEntry.js?t=1737618055467)What can be the reason of this issue? Component is really simple and almost identical to the CatFactToast from the example, but without any fetchings :)

Code:

import type { CustomComponentProps } from 'aurora/externalContext';
import React from 'react';
const ExampleComponent: React.FC<CustomComponentProps> = ({ auroraContext }) => {
  const { components, utils } = auroraContext;
  const { i18n } = utils;
  const { Panel, PanelBody } = components;
  return (
    <div>
      <Panel>
        <PanelBody>
          <p>{i18n.formatMessage('panel.title')}</p>
        </PanelBody>
      </Panel>
    </div>
  );
};
export default ExampleComponent;
Would be grateful for any help, thanks!

Would be grateful for any help, thanks!

Something is wrong with posting anything on community 

I believe the process you're following is correct - once you're created the pull request, it's approved and merged into Stage-Main, it should appear for you within the site if stage-main is the active branch.

engwei it doesn't work for us :(

In GitHub, check the Actions tab on your <phase>-main branch, and see if there are any errors.

Other things to try:

• Check package.json and ensure the SDK version matches your community version (likely 24.12 or 25.1)
• Run npm i in your repo
• Run npm run build in your repo. This will do the same thing the actions in GitHub does. This will uncover any errors that may prevent your component from deploying properly